Return to field — N624PW
KTYR · 222026-07-17 13:21 UTC· KTYR → KTYR· K3M LEASING LLC· C560
N624PW (K3M Leasing) had departed KTYR on 2026-07-17. SkyMeter detected a return to field at Tyler Pounds Regional Airport (KTYR) on runway 22 at 13:21 UTC. Peak cruise altitude FL311, turnaround area near Brenham, US. METAR at the time reported 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4059 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
HOUSTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4068 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
HOUSTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/6447 2026-06-09 05:01Z – 2026-07-20 04:59Z SFC–1,000 ft
Houston, TX, Tuesday, June 9, 2026 through Sunday, July 19, 2026 Local
View FAA NOTAM → - SECURITY6/6787 2026-07-03 15:07Z – 2026-07-21 04:59Z SFC–400 ft
Houston, TX
View FAA NOTAM → - SECURITY6/6783 2026-07-03 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Houston, TX
View FAA NOTAM → - SECURITY6/6838 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft
Houston, TX
View FAA NOTAM →
SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.
Pilot review data
- Runway 22
- 31169 ft AGL at event
- 452 kt ground speed
- 0 fpm vertical
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KTYR 162153Z 21006KT 10SM CLR 35/21 A3014 RMK AO2 SLP198 T03500211
Flight context
- N624PW
- K3M Leasing
- C560
- KTYR → KTYR
- 2026-07-17 13:21 UTC
- KTYR runway 22
All events on this flight
Automated analysis. Events shown on this page (such as go-around, unstable approach, or runway events) are heuristic classifications produced by algorithms from publicly broadcast ADS-B data. They are intended to surface flights of interest for further review — they are not findings of fact, and they do not determine pilot fault, regulatory compliance, or the cause of any occurrence. Coverage gaps and sensor noise can affect accuracy. Only the relevant civil aviation authority or accident investigation body can make official determinations. How we detect events · Dispute or correct this data