LXJ267 (Flexjet) was operating from KBOS to KATL (Hartsfield Jackson Atlanta International Airport) on 2026-08-21. SkyMeter detected a diversion to Burlington Alamance Regional Airport (KBUY) on runway 06 at 23:14 UTC. Peak cruise altitude FL450, turnaround area near Cumberland County, US. Approach stability score: 88/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 5 kt wind, 1 kt crosswind component, 16,093 m visibility. 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/5076 2026-08-19 15:00Z – 2026-08-30 22:00Z SFC–1,000 ft
Williamsport, PA, Wednesday, August 19, 2026 through Sunday, August 30, 2026 Local
View FAA NOTAM → - SECURITY6/6927 2026-08-21 13:00Z – 2026-08-22 03:00Z SFC–1,000 ft
Williamsport, PA, Friday, August 21, 2026 through Friday, August 21, 2026 Local
View FAA NOTAM → - SECURITY6/5424 2026-08-21 22:00Z – 2026-08-27 03:59Z SFC–400 ft
East Rutherford, NJ, Friday, August 21, 2026 through Wednesday, August 26, 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 06
- 584 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 88/100
- 5 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- METAR KBUY 160554Z AUTO 00000KT 10SM CLR 17/16 A3032 RMK AO2 SLP263 T01670161 10222 20161 58004
Flight context
- LXJ267
- Flexjet
- E545
- KBOS → KBUY
- 2026-08-21 23:14 UTC
- KBUY runway 06
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