Unstable approach — N813MS
KCEU · 252026-07-19 20:21 UTC· KSTL → KCEU· CYPRESS COVE AIR LLC· CL60
N813MS (Cypress Cove AIR) was operating from KSTL to KCEU on 2026-07-19. SkyMeter detected a low approach-stability score at Oconee County Regional Airport (KCEU) on runway 25 at 20:21 UTC. Trace data at the event: 1998 ft AGL, 150 kt GS. Approach stability score: 29/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 5 kt wind, 14,484 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)- SECURITY6/3980 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3990 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4114 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4116 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4119 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
NASHVILLE, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4121 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Nashville, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4135 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
CLAYTON, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4161 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
St, Louis, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7972 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Nashville, TN
View FAA NOTAM → - SECURITY6/7967 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Nashville, TN
View FAA NOTAM → - SECURITY6/7600 2026-07-07 13:07Z – 2026-07-21 03:59Z SFC–400 ft
Chattanooga, TN
View FAA NOTAM → - SECURITY6/7197 2026-07-09 11:07Z – 2026-07-21 03:59Z SFC–400 ft
Louisville, KY
View FAA NOTAM → - SECURITY6/7817 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft
St Louis, MO
View FAA NOTAM → - SECURITY6/7645 2026-07-19 19:07Z – 2026-07-21 04:59Z SFC–400 ft
Clayton, MO
View FAA NOTAM → - SECURITY6/7649 2026-07-19 19:07Z – 2026-07-21 03:59Z SFC–400 ft
Clayton, MO
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 25
- 1998 ft AGL at event
- 150 kt ground speed
- 0 fpm vertical
- Approach stability 29/100
- 5 kt wind
- 0 kt crosswind component
- 14,484 m visibility
- METAR KCEU 312354Z AUTO 03006KT 9SM CLR 28/21 A3010 RMK AO2 SLP181 T02780206 10328 20278 58001
Flight context
- N813MS
- Cypress Cove AIR
- CL60
- KSTL → KCEU
- 2026-07-19 20:21 UTC
- KCEU runway 25
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