Unstable approach — N173CN
0CA3 · 282026-06-12 01:05 UTC· KPAE → 0CA3· PNC BANK NA· FA7X
N173CN (PNC Bank NA) was operating from KPAE to 0CA3 on 2026-06-12. SkyMeter detected a low approach-stability score at Crawford Airport (0CA3) on runway 28 at 01:05 UTC. Trace data at the event: 1691 ft AGL, 154 kt GS. METAR at the time reported 5 kt wind, 4 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft
BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM → - SECURITY6/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft
SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local
View FAA NOTAM → - SECURITY6/4011 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
BELLEVUE, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4013 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Seattle, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4033 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
RENTON, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4034 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Renton, WA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4052 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4054 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4060 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Oakland, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4061 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
BERKLEY, CA, Monday, June 1, 2026 through Tuesday, July 21, 2026 Local
View FAA NOTAM → - SECURITY6/4192 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Santa Barbara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4204 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Santa Clara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/6143 2026-06-08 15:00Z – 2026-06-13 04:00Z SFC–8,000 ft
3NM S CHELAN, WA, Monday, June 8, 2026 through Saturday, June 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/7765 2026-06-11 22:46Z – 2026-06-13 23:59Z SFC–400 ft
3.8NM NW TRACY, CA, Thursday, June 11, 2026 through Saturday, June 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/7800 2026-06-12 00:56Z – 2026-06-13 23:59Z SFC–400 ft
3.8NM NW TRACY, CA, Friday, June 12, 2026 through Saturday, June 13, 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 28
- 1691 ft AGL at event
- 154 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 4 kt crosswind component
Flight context
- N173CN
- PNC Bank NA
- FA7X
- KPAE → 0CA3
- 2026-06-12 01:05 UTC
- 0CA3 runway 28
All events on this flight
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