Unstable approach — AAL1947

AAL1947 (U S Bank NA) was operating from KDCA to K8T8 on 2026-08-19. SkyMeter detected a low approach-stability score at San Geronimo Airpark (K8T8) on runway 17L at 01:35 UTC. Trace data at the event: 2127 ft AGL, 120 kt GS. METAR at the time reported 6 kt wind, 2 kt crosswind component. 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.

• 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 →
• 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/3628 2026-08-17 12:00Z – 2026-08-23 23:59Z SFC–400 ft

  SAINT LOUIS, MO, Monday, August 17, 2026 through Sunday, August 23, 2026 Local

  View FAA NOTAM →
• SECURITY6/5452 2026-08-17 12:30Z – 2026-08-22 06:00Z SFC–2,500 ft

  MAYPORT, FL, Monday, August 17, 2026 through Saturday, August 22, 2026 Local

  View FAA NOTAM →
• SECURITY6/5153 2026-08-18 05:00Z – 2026-08-20 09:30Z SFC–17,999 ft

  Macon, GA, Tuesday, August 18, 2026 through Thursday, August 20, 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.

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