Unstable approach — EVC3

K2W6 · 11

2026-04-03 20:22 UTC· SKY WHEEELS LLC· FA10

▶ Replay 📊 Analyse

EVC3 (SKY Wheeels) was inbound to K2W6 on 2026-04-03. SkyMeter detected a low approach-stability score at St. Mary's County Regional Airport (K2W6) on runway 11 at 20:22 UTC. Trace data at the event: 1308 ft AGL, 149 kt GS. Approach stability score: 24/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 11 kt wind, 11 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)
  • SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft

    Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

    View FAA NOTAM →
  • SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft

    OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/4875 2026-03-30 13:00Z – 2026-04-04 06:00Z SFC–2,500 ft

    20NM NW MEDFORD, OR, Friday, July 10, 2026 through Saturday, July 25, 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 11
  • 1308 ft AGL at event
  • 149 kt ground speed
  • 0 fpm vertical
  • Approach stability 24/100
  • 11 kt wind
  • 11 kt crosswind component
  • 16,093 m visibility
  • METAR K2W6 152215Z AUTO 00000KT 10SM CLR 29/20 A3012 RMK AO2 T02860203 $

Flight context

  • EVC3
  • SKY Wheeels
  • FA10
  • 2026-04-03 20:22 UTC
  • K2W6 runway 11

All events on this flight

Unstable approach 20:22:25 UTC · K2W6 runway 11 · 1,308 ft AGL · 149 kt GS
Unstable approach 20:22:25 UTC · K2W6 runway 11 · 1,308 ft AGL · 149 kt GS
Unstable approach 20:22:25 UTC · K2W6 runway 11 · 1,308 ft AGL · 149 kt GS
Unstable approach 20:22:25 UTC · K2W6 runway 11 · 1,308 ft AGL · 149 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· K2W6