Unstable approach — MXY134
KRDU · 142026-07-10 12:32 UTC· KTPA → KRDU· BREEZE AVIATION GROUP INC.· BCS3
MXY134 (Breeze Aviation Group) was operating from KTPA to KRDU on 2026-07-10. SkyMeter detected a low approach-stability score at Raleigh Durham International Airport (KRDU) on runway 14 at 12:32 UTC. Trace data at the event: 1549 ft AGL, 140 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)- SECURITY6/4001 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
GREENSBORO, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4004 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHARLOTTE, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4131 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MYRTLE BEACH, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4153 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4156 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
TAMPA, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7880 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft
Tampa, FL
View FAA NOTAM → - SECURITY6/7881 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft
Tampa, FL
View FAA NOTAM → - SECURITY6/2665 2026-07-07 12:30Z – 2026-07-11 06:00Z SFC–2,500 ft
MAYPORT, FL, Tuesday, July 7, 2026 through Saturday, July 11, 2026 Local
View FAA NOTAM → - SECURITY6/7564 2026-07-09 11:07Z – 2026-07-21 03:59Z SFC–400 ft
Conway, SC
View FAA NOTAM → - SPACE OPERATIONS6/3762 2026-07-10 08:32Z – 2026-07-10 13:24Z SFC–180 ft
Cape Canaveral, FL, Friday, July 10, 2026 Local
View FAA NOTAM → - SPACE OPERATIONS6/3768 2026-07-10 08:32Z – 2026-07-10 13:24Z SFC–180 ft
Cape Canaveral, FL, Friday, July 10, 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
- Runway 14
- 1549 ft AGL at event
- 140 kt ground speed
- 0 fpm vertical
- Approach stability 42/100
- 4 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- KRDU 300251Z 10003KT 10SM FEW065 FEW250 21/17 A3009 RMK AO2 SLP186 T02110167 51015 $
Flight context
- MXY134
- Breeze Aviation Group
- BCS3
- KTPA → KRDU
- 2026-07-10 12:32 UTC
- KRDU runway 14
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