| ARRIVED 40 HOUR 53 MINUTES AGO |
 |  |
Departure (G42959 Flight Schedule)
Tulsa, United StatesCST 00:00:00 DAY
Arrival (G42959 Flight Schedule)
EST 00:00:00 DAY
Flight Radar Checker G4 2959
Live Flight Tracker Map
Flight G42959 from Tulsa to Sanford is operated by Allegiant Air. Scheduled time of departure from Tulsa Intl is 09:18 CST and scheduled time of arrival in Orlando Sanford Intl is 12:43 EST. The duration of the flight is 2 hours 25 minutes.
Not Rated
History Flight Information for G42959 from Flight Scanner System
| Date | Flight | Departure Airport | Arrival Airport | Scheduled | Plane | Estimated | ||
|---|---|---|---|---|---|---|---|---|
| Departure | Arrival | Departure | Arrival | |||||
| Thu, 29 Jan | G42959 | Tulsa Intl (TUL) | Orlando Sanford Intl (SFB) | 09:18 CST | 12:43 EST | 09:55 CST | 12:42 EST | |
| Sun, 25 Jan | G42959 | Louisville International Airport (SDF) | Orlando Sanford Intl (SFB) | 16:39 EST | 18:41 EST | |||
| Thu, 22 Jan | G42959 | Tulsa Intl (TUL) | Orlando Sanford Intl (SFB) | 09:18 CST | 12:43 EST | 09:39 CST | 12:30 EST | |
| Sun, 18 Jan | G42959 | Louisville International Airport (SDF) | Orlando Sanford Intl (SFB) | 16:39 EST | 18:41 EST | 16:52 EST | 18:19 EST | |
| Thu, 15 Jan | G42959 | Tulsa Intl (TUL) | Orlando Sanford Intl (SFB) | 09:18 CST | 12:43 EST | 09:43 CST | 12:44 EST | |
| Sun, 11 Jan | G42959 | Louisville International Airport (SDF) | Orlando Sanford Intl (SFB) | 16:39 EST | 18:41 EST | N229NV (Airbus A320) | 17:07 EST | 18:35 EST |
| Thu, 08 Jan | G42959 | Tulsa Intl (TUL) | Orlando Sanford Intl (SFB) | 09:18 CST | 12:43 EST | 09:53 CST | 13:02 EST | |
| Fri, 12 Dec | G42959 | Orlando Sanford Intl (SFB) | Stewart Intl (SWF) | 16:00 EST | 18:40 EST | 16:14 EST | 18:24 EST | |
| Fri, 05 Dec | G42959 | Orlando Sanford Intl (SFB) | Stewart Intl (SWF) | 16:00 EST | 18:40 EST | 16:10 EST | 18:20 EST | |
Disclaimer for G42959 Flight Radar Data
Flight G42959 from Tulsa Intl to Orlando Sanford Intl data is collected from different sources. The data is for informational purposes only and PlaneMapper is not responsible for the accuracy and reliability of flight G42959 data.
