Unstable approach — N783AL

KAPA · 17L

2026-07-04 04:08 UTC· KAPA KAPA· AIR METHODS LLC· BE20

N783AL (AIR Methods) was operating from KAPA to KAPA on 2026-07-04. SkyMeter detected a low approach-stability score at Centennial Airport (KAPA) on runway 17L at 04:08 UTC. Trace data at the event: 6948 ft AGL, 184 kt GS. METAR at the time reported 8 kt wind, 7 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/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/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 17L
  • 6948 ft AGL at event
  • 184 kt ground speed
  • 0 fpm vertical
  • 8 kt wind
  • 7 kt crosswind component
  • 16,093 m visibility
  • KAPA 161153Z 18003KT 10SM BKN220 13/07 A3022 RMK AO2 SLP183 T01330067 10161 20122 58001

Flight context

  • N783AL
  • AIR Methods
  • BE20
  • KAPA → KAPA
  • 2026-07-04 04:08 UTC
  • KAPA runway 17L

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

SkyMeter · trace data observed via ADS-B· KAPA