Unstable approach — C102

KRME · 33

2026-08-18 16:16 UTC· KMTC KRME· GLF5

C102 was operating from KMTC to KRME on 2026-08-18. SkyMeter detected a low approach-stability score at Griffiss International Airport (KRME) on runway 33 at 16:16 UTC. Trace data at the event: 1617 ft AGL, 171 kt GS. Approach stability score: 59/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 9 kt wind, 5 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.

Pilot review data

  • Runway 33
  • 1617 ft AGL at event
  • 171 kt ground speed
  • 0 fpm vertical
  • Approach stability 59/100
  • 9 kt wind
  • 5 kt crosswind component
  • 16,093 m visibility
  • KRME 040653Z 00000KT 10SM FEW050 FEW065 16/15 A2989 RMK AO2 SLP118 T01560150

Flight context

  • C102
  • GLF5
  • KMTC → KRME
  • 2026-08-18 16:16 UTC
  • KRME runway 33

All events on this flight

Unstable approach 16:16:59 UTC · KRME runway 33 · 1,617 ft AGL · 171 kt GS
Unstable approach 16:16:59 UTC · KRME runway 33 · 1,617 ft AGL · 171 kt GS
Unstable approach 16:16:59 UTC · KRME runway 33 · 1,617 ft AGL · 171 kt GS

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· KRME