Return to field — N823PM
KFTW · 162026-07-18 15:26 UTC· KFTW → KFTW· HERNCO GP LLC· C550
N823PM (Hernco GP) had departed KFTW on 2026-07-18. SkyMeter detected a return to field at Fort Worth Meacham International Airport (KFTW) on runway 16 at 15:26 UTC. Peak cruise altitude FL383, turnaround area near Guadalupe, 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/4002 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
FORT WORTH, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4030 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
AUSTIN, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4031 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
AUSTIN, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/6842 2026-06-29 15:07Z – 2026-07-21 04:59Z SFC–400 ft
Fort Worth, TX
View FAA NOTAM → - SECURITY6/6820 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft
San Antonio, TX
View FAA NOTAM → - SECURITY6/6841 2026-07-15 13:07Z – 2026-07-21 04:59Z SFC–400 ft
Fort Worth, 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 16
- 38329 ft AGL at event
- 438 kt ground speed
- 0 fpm vertical
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KFTW 152153Z 13012G18KT 10SM CLR 38/18 A2996 RMK AO2 SLP132 T03830178
Flight context
- N823PM
- Hernco GP
- C550
- KFTW → KFTW
- 2026-07-18 15:26 UTC
- KFTW runway 16
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