Unstable approach — N526CF

KSUN · 31

2026-09-04 02:04 UTC· KLAX KSUN· WOLFF 45 LLC, PGP EQUIPMENT LLC, RTF EQUIPMENT LLC, RTH EQUIPMEN· LJ45

N526CF (Wolff 45) was operating from KLAX to KSUN on 2026-09-04. SkyMeter detected a low approach-stability score at Friedman Memorial Airport (KSUN) on runway 31 at 02:04 UTC. Trace data at the event: 6360 ft AGL, 170 kt GS. Approach stability score: 36/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 2 kt wind, 2 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)
  • HAZARDS6/7121 2026-08-23 03:30Z – 2026-09-05 04:00Z SFC–10,000 ft

    60NM SW MOUNTAIN HOME, ID, Sunday, August 23, 2026 through Saturday, September 5, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8111 2026-08-26 02:30Z – 2026-09-09 04:00Z SFC–10,000 ft

    60NM SW MOUNTAIN HOME, ID, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8332 2026-08-26 17:45Z – 2026-09-05 04:00Z SFC–11,000 ft

    51NM NE FALLON, NV, Wednesday, August 26, 2026 through Saturday, September 5, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8474 2026-08-27 00:30Z – 2026-09-04 03:00Z SFC–13,000 ft

    37NM N WINNEMUCCA, NV, Thursday, August 27, 2026 through Friday, September 4, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8492 2026-08-27 01:45Z – 2026-09-04 03:00Z SFC–8,000 ft

    16NM SW BOISE, ID, Thursday, August 27, 2026 through Friday, September 4, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8507 2026-08-27 03:15Z – 2026-09-05 03:00Z SFC–11,000 ft

    51NM NE FALLON, NV, Thursday, August 27, 2026 through Saturday, September 5, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8501 2026-08-27 14:00Z – 2026-09-04 06:00Z SFC–11,000 ft

    104NM SE BURNS, OR, Thursday, August 27, 2026 through Friday, September 4, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8588 2026-08-27 18:00Z – 2026-09-09 03:00Z SFC–10,500 ft

    62NM NE WINNEMUCCA, NV, Thursday, August 27, 2026 through Wednesday, September 9, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8676 2026-08-27 23:15Z – 2026-09-10 03:00Z SFC–13,000 ft

    37NM N WINNEMUCCA, NV, Thursday, August 27, 2026 through Thursday, September 10, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/0682 2026-09-03 13:00Z – 2026-09-17 03:00Z SFC–10,000 ft

    60NM SW MOUNTAIN HOME, ID, Thursday, September 3, 2026 through Thursday, September 17, 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 31
  • 6360 ft AGL at event
  • 170 kt ground speed
  • 0 fpm vertical
  • Approach stability 36/100
  • 2 kt wind
  • 2 kt crosswind component
  • 16,093 m visibility
  • KSUN 162147Z 14009KT 10SM CLR 26/02 A3012

Flight context

  • N526CF
  • Wolff 45
  • LJ45
  • KLAX → KSUN
  • 2026-09-04 02:04 UTC
  • KSUN runway 31

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