Unstable approach — LXJ305
KABI · 042026-07-03 20:35 UTC· FLEXJET LLC, SHILLINGFORD NEIL, SHILLINGFORD LIZA, JENNINGS MARK· E55P
LXJ305 (Flexjet) was inbound to KABI on 2026-07-03. SkyMeter detected a low approach-stability score at Abilene Regional Airport (KABI) on runway 04 at 20:35 UTC. Trace data at the event: 2892 ft AGL, 154 kt GS. Approach stability score: 35/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, 3 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)- HAZARDS6/9420 2026-06-20 21:25Z – 2026-07-04 04:00Z SFC–12,000 ft
40NM SE ALBUQUERQUE, NM, Saturday, June 20, 2026 through Saturday, July 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/9456 2026-06-21 13:00Z – 2026-07-05 04:00Z SFC–12,000 ft
40NM SE ALBUQUERQUE, NM, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/0608 2026-06-25 13:00Z – 2026-07-09 03:00Z SFC–14,000 ft
15NM W LOS ALAMOS, NM, Thursday, June 25, 2026 through Thursday, July 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/1156 2026-06-28 14:00Z – 2026-07-12 03:00Z SFC–12,500 ft
32NM NW TAOS, NM, Sunday, June 28, 2026 through Sunday, July 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/1169 2026-06-28 14:00Z – 2026-07-12 03:00Z SFC–12,500 ft
32NM NW TAOS, NM, Sunday, June 28, 2026 through Sunday, July 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/1333 2026-06-29 03:06Z – 2026-07-13 04:00Z SFC–17,000 ft
8NM SW LEADVILLE, CO, Monday, June 29, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/1416 2026-06-29 14:37Z – 2026-07-14 04:00Z SFC–13,500 ft
15NM NW CAÑON CITY, CO, Monday, June 29, 2026 through Tuesday, July 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/1584 2026-06-29 18:38Z – 2026-07-13 04:00Z SFC–12,500 ft
32NM NW TAOS, NM, Monday, June 29, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/1594 2026-06-29 18:49Z – 2026-07-13 03:00Z SFC–12,500 ft
32NM NW TAOS, NM, Monday, June 29, 2026 through Monday, July 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/1775 2026-06-30 06:00Z – 2026-07-14 04:00Z SFC–15,000 ft
4NM SW PUEBLO, CO, Tuesday, June 30, 2026 through Tuesday, July 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/2312 2026-07-01 04:00Z – 2026-07-15 04:00Z SFC–14,000 ft
20NM W WALSENBURG, CO, Wednesday, July 1, 2026 through Wednesday, July 15, 2026 UTC
View FAA NOTAM → - HAZARDS6/2597 2026-07-02 04:41Z – 2026-07-16 04:00Z SFC–15,000 ft
4NM SW PUEBLO, CO, Thursday, July 2, 2026 through Thursday, July 16, 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 04
- 2892 ft AGL at event
- 154 kt ground speed
- 0 fpm vertical
- Approach stability 35/100
- 4 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KABI 170752Z 15007KT 10SM CLR 26/17 A3021 RMK AO2 SLP198 T02610167
Flight context
- LXJ305
- Flexjet
- E55P
- 2026-07-03 20:35 UTC
- KABI runway 04
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