Unstable approach — CRN300T

CYXS · 33

2026-06-01 18:49 UTC· CYXS → CYXS· Carson Air Ltd· B350

CRN300T (Carson Air) was operating from CYXS to CYXS on 2026-06-01. SkyMeter detected a low approach-stability score at Prince George Airport (CYXS) on runway 33 at 18:49 UTC. Trace data at the event: 3317 ft AGL, 162 kt GS. Approach stability score: 34/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 7 kt wind, 6 kt crosswind component, 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.

Pilot review data

  • Runway 33
  • 3317 ft AGL at event
  • 162 kt ground speed
  • 0 fpm vertical
  • Approach stability 34/100
  • 7 kt wind
  • 6 kt crosswind component
  • 14,484 m visibility
  • CYXS 162200Z AUTO 19014G23KT 9SM BKN091 OVC110 19/03 A2983 RMK SLP110 DENSITY ALT 3400FT

Flight context

  • CRN300T
  • Carson Air
  • B350
  • CYXS → CYXS
  • 2026-06-01 18:49 UTC
  • CYXS runway 33

All events on this flight

Unstable approach 18:49:00 UTC · CYXS runway 33 · 3,317 ft AGL · 162 kt GS
Unstable approach 18:49:00 UTC · CYXS runway 33 · 3,317 ft AGL · 162 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· CYXS