SLI430 was operating from MMMX to KRDU on 2026-05-31. SkyMeter detected a low approach-stability score at Raleigh Durham International Airport (KRDU) on runway 14 at 18:12 UTC. Trace data at the event: 1538 ft AGL, 143 kt GS. Approach stability score: 42/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 4 kt wind, 4 kt crosswind component, 16,093 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/6914 2025-05-06 23:30Z – 2027-10-18 11:03Z SFC–6,000 ft
South Padre Island, TX, Tuesday, May 6, 2025 Local
View FAA NOTAM → - 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/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft
OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 2026 Local
View FAA NOTAM → - SECURITY5/3678 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–2,000 ft
Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local
View FAA NOTAM → - SECURITY5/3679 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–5,000 ft
Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local
View FAA NOTAM → - SECURITY6/2644 2026-05-27 11:00Z – 2026-06-12 22:00Z SFC–400 ft
Brunswick, GA, Wednesday, May 27, 2026 through Friday, June 12, 2026 Local
View FAA NOTAM → - HAZARDS6/3292 2026-05-27 17:20Z – 2026-06-10 00:15Z SFC–2,000 ft
22NM SW TALLAHASSEE, FL, Wednesday, May 27, 2026 through Wednesday, June 10, 2026 UTC
View FAA NOTAM → - SECURITY6/3583 2026-05-28 07:00Z – 2026-06-01 23:00Z
NEW ORLEANS, LA, Thursday, May 28, 2026 through Monday, June 1, 2026 UTC
View FAA NOTAM → - SECURITY6/2647 2026-05-28 12:00Z – 2026-06-02 04:00Z SFC–2,000 ft
New Orleans, LA, Thursday, May 28, 2026 through Monday, June 1, 2026 Local
View FAA NOTAM → - SECURITY6/3335 2026-05-28 12:00Z – 2026-06-02 04:00Z SFC–2,000 ft
New Orleans, LA, Thursday, May 28, 2026 through Monday, June 1, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/2997 2026-05-31 10:58Z – 2026-05-31 15:08Z SFC–180 ft
Cape Canaveral, FL, Sunday, May 31, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/2909 2026-05-31 17:30Z – 2026-06-01 05:30Z SFC–400 ft
Panama City Beach, FL, Sunday, May 31, 2026 through Monday, June 1, 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
- Runway 14
- 1538 ft AGL at event
- 143 kt ground speed
- 0 fpm vertical
- Approach stability 42/100
- 4 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KRDU 170630Z AUTO 34009KT 10SM BKN043 OVC045 20/12 A2990 RMK T02000120 MADISHF
Flight context
- SLI430
- E190
- MMMX → KRDU
- 2026-05-31 18:12 UTC
- KRDU runway 14
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