Unstable approach — UAL263

UAL263 (United Airlines) was operating from EGLL to KFTG on 2026-08-04. SkyMeter detected a low approach-stability score at Colorado Air and Space Port (KFTG) on runway 36 at 23:19 UTC. Trace data at the event: 6582 ft AGL, 178 kt GS. Approach stability score: 43/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 10 kt wind, 10 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.

• 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/4348 2026-03-08 07:00Z – 2026-11-01 06:59Z SFC–2,400 ft

  GRAND FORKS AFB, ND, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/2790 2026-07-02 22:30Z – 2026-09-15 03:59Z SFC–400 ft

  St. George, ME, Thursday, July 2, 2026 through Monday, September 14, 2026 Local

  View FAA NOTAM →
• HAZARDS6/6777 2026-07-19 19:05Z – 2026-08-20 07:00Z SFC–7,000 ft

  10NM N ELY, MN, Sunday, July 19, 2026 through Thursday, August 20, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6779 2026-07-19 19:09Z – 2026-08-20 07:00Z SFC–7,000 ft

  20NM N ELY, MN, Sunday, July 19, 2026 through Thursday, August 20, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8871 2026-07-27 14:00Z – 2026-08-09 04:00Z SFC–8,000 ft

  83NM N SPEARFISH, SD, Monday, July 27, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9566 2026-07-28 17:15Z – 2026-08-11 04:00Z SFC–10,000 ft

  33NM SW PHILIP, SD, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1033 2026-08-03 10:00Z – 2026-08-10 02:00Z SFC–7,000 ft

  25NM NW ELY, MN, Monday, August 3, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1034 2026-08-03 10:00Z – 2026-08-10 02:00Z SFC–7,000 ft

  13NM N ELY, MN, Monday, August 3, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/9616 2026-08-04 16:30Z – 2026-08-04 18:30Z SFC–16,000 ft

  Rochester, NY, Tuesday, August 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1483 2026-08-04 20:00Z – 2026-08-04 20:15Z SFC–7,500 ft

  DEER RIVER, MN, Tuesday, August 4, 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.

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