NOS431 was inbound to LIRF on 2026-07-24. SkyMeter detected a upset at 14:54 UTC. Trace data at the event: 39680 ft AGL, 494 kt GS. Approach stability score: 90/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 3 kt wind, 3 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft
Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft
NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY6/2790 2026-07-02 22:30Z – 2026-09-15 03:59Z SFC–400 ft
St. George, ME, Thursday, July 2, 2026 through Monday, September 14, 2026 Local
View FAA NOTAM → - HAZARDS6/6848 2026-07-20 00:32Z – 2026-08-03 23:45Z SFC–3,000 ft
2NM W SHULERVILLE, SC, Monday, July 20, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/6520 2026-07-23 13:00Z – 2026-07-26 04:00Z SFC–400 ft
sterling heights, MI, Thursday, July 23, 2026 through Sunday, July 26, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/6521 2026-07-23 21:30Z – 2026-07-26 04:00Z SFC–400 ft
cincinnati, OH, Thursday, July 23, 2026 through Sunday, July 26, 2026 UTC
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
- 39680 ft AGL at event
- 494 kt ground speed
- 0 fpm vertical
- Approach stability 90/100
- 3 kt wind
- 3 kt crosswind component
Flight context
- NOS431
- B789
- 2026-07-24 14:54 UTC
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