EIX04N was operating from LSZC to EIWT on 2026-05-19. SkyMeter detected a stall warning at 18:44 UTC. Trace data at the event: 703 ft AGL, 95 kt GS. Approach stability score: 41/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 10 kt wind, 7 kt crosswind component. A stall flag is raised when the inferred angle of attack and observed airspeed are consistent with a stalled wing. Stall events on general-aviation trainer aircraft are predominantly stall-recognition practice during primary flight training, not safety-of-flight incidents. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- 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/0907 2026-05-18 13:00Z – 2026-05-19 20:00Z SFC–1,000 ft
Morristown, NJ, Monday, May 18, 2026 through Tuesday, May 19, 2026 Local
View FAA NOTAM → - SECURITY6/0903 2026-05-19 12:00Z – 2026-05-21 20:00Z SFC–400 ft
East Marion, NY, Tuesday, May 19, 2026 through Thursday, May 21, 2026 Local
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
- 703 ft AGL at event
- 95 kt ground speed
- 0 fpm vertical
- Approach stability 41/100
- 10 kt wind
- 7 kt crosswind component
Flight context
- EIX04N
- A339
- LSZC → EIWT
- 2026-05-19 18:44 UTC
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