Unstable approach — RAX801
KBTV · 152026-08-14 08:30 UTC· KLRD → KBTV· ROYAL AIR FREIGHT INC· FA20
RAX801 (Royal AIR Freight) was operating from KLRD to KBTV on 2026-08-14. SkyMeter detected a low approach-stability score at Burlington International Airport (KBTV) on runway 15 at 08:30 UTC. Trace data at the event: 1421 ft AGL, 156 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 1 kt wind, 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/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/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft
Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC
View FAA NOTAM → - SECURITY6/0879 2026-08-06 12:00Z – 2026-08-14 20:00Z SFC–2,000 ft
Laurel, MD, Thursday, August 6, 2026 through Friday, August 14, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/0460 2026-08-06 13:00Z – 2026-08-17 05:00Z SFC–400 ft
Milwaukee, WI, Thursday, August 6, 2026 through Monday, August 17, 2026 UTC
View FAA NOTAM → - VIP6/2748 2026-08-08 14:00Z – 2026-08-16 22:00Z SFC–4,999 ft
THURMONT, MD, Saturday, August 8, 2026 through Sunday, August 16, 2026 Local
View FAA NOTAM → - SECURITY6/3199 2026-08-12 05:00Z – 2026-08-15 09:30Z SFC–17,999 ft
Macon, GA, Wednesday, August 12, 2026 through Saturday, August 15, 2026 Local
View FAA NOTAM → - SECURITY6/3974 2026-08-13 05:00Z – 2026-08-15 09:30Z SFC–17,999 ft
Macon, GA, Thursday, August 13, 2026 through Saturday, August 15, 2026 Local
View FAA NOTAM → - UAS PUBLIC GATHERING6/2574 2026-08-13 12:00Z – 2026-08-24 05:00Z SFC–400 ft
des moines, IA, Thursday, August 13, 2026 through Monday, August 24, 2026 UTC
View FAA NOTAM → - AIR SHOWS/SPORTS6/2569 2026-08-13 14:00Z – 2026-08-16 22:00Z SFC–16,000 ft
chicago, IL, Thursday, August 13, 2026 through Sunday, August 16, 2026 UTC
View FAA NOTAM → - HAZARDS6/4962 2026-08-13 18:15Z – 2026-08-20 18:00Z SFC–2,000 ft
YOUNGSPORT, TX, Thursday, August 13, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/3173 2026-08-13 21:00Z – 2026-08-23 07:00Z SFC–400 ft
Lebanon, TN, Thursday, August 13, 2026 through Sunday, August 23, 2026 UTC
View FAA NOTAM → - SECURITY6/4961 2026-08-14 04:07Z – 2026-08-14 04:59Z SFC–400 ft
Dyersville, IA
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 15
- 1421 ft AGL at event
- 156 kt ground speed
- 0 fpm vertical
- Approach stability 41/100
- 1 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KBTV 160554Z 20009KT 10SM OVC090 18/11 A3025 RMK AO2 SLP244 T01830106 10183 20172 51005
Flight context
- RAX801
- Royal AIR Freight
- FA20
- KLRD → KBTV
- 2026-08-14 08:30 UTC
- KBTV runway 15
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