Unstable approach — N9LV
92CA · 322026-08-09 03:07 UTC· KSLC → 92CA· MIKE LIMA LLC· PRM1
N9LV (Mike Lima) was operating from KSLC to 92CA on 2026-08-09. SkyMeter detected a low approach-stability score at Westlake Farms Airport (92CA) on runway 32 at 03:07 UTC. Trace data at the event: 1295 ft AGL, 145 kt GS. METAR at the time reported 5 kt wind, 3 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)- HAZARDS6/7246 2026-07-21 05:00Z – 2026-08-21 03:00Z SFC–10,500 ft
20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Friday, August 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/7372 2026-07-21 13:38Z – 2026-08-22 03:00Z SFC–10,500 ft
20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/9393 2026-07-28 14:00Z – 2026-08-11 05:00Z SFC–13,000 ft
60NM NE FALLON, NV, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/9881 2026-07-29 02:10Z – 2026-08-12 04:00Z SFC–13,500 ft
25NM S BISHOP, CA, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/9879 2026-07-29 14:00Z – 2026-08-11 04:00Z SFC–13,000 ft
60NM NE FALLON, NV, Wednesday, July 29, 2026 through Tuesday, August 11, 2026 UTC
View FAA NOTAM → - HAZARDS6/0406 2026-07-30 14:00Z – 2026-08-12 05:00Z SFC–13,000 ft
60NM NE FALLON, NV, Thursday, July 30, 2026 through Wednesday, August 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/0407 2026-07-30 14:00Z – 2026-08-12 05:00Z SFC–13,000 ft
60NM NE FALLON, NV, Thursday, July 30, 2026 through Wednesday, August 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/0722 2026-08-01 13:00Z – 2026-08-14 04:00Z SFC–14,000 ft
9NM S ELY, NV, Saturday, August 1, 2026 through Friday, August 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/1038 2026-08-03 13:00Z – 2026-08-16 04:00Z SFC–14,000 ft
9NM S ELY, NV, Monday, August 3, 2026 through Sunday, August 16, 2026 UTC
View FAA NOTAM → - HAZARDS6/1461 2026-08-04 12:00Z – 2026-08-18 04:00Z SFC–13,000 ft
4NM W RICHFIELD, UT, Tuesday, August 4, 2026 through Tuesday, August 18, 2026 UTC
View FAA NOTAM → - HAZARDS6/1464 2026-08-04 12:00Z – 2026-08-18 04:00Z SFC–13,000 ft
4NM W RICHFIELD, UT, Tuesday, August 4, 2026 through Tuesday, August 18, 2026 UTC
View FAA NOTAM → - HAZARDS6/1961 2026-08-05 13:00Z – 2026-08-19 04:00Z SFC–14,000 ft
9NM S ELY, NV, Wednesday, August 5, 2026 through Wednesday, August 19, 2026 UTC
View FAA NOTAM → - HAZARDS6/2274 2026-08-05 19:25Z – 2026-08-15 04:00Z SFC–13,500 ft
25NM S BISHOP, CA, Wednesday, August 5, 2026 through Saturday, August 15, 2026 UTC
View FAA NOTAM → - HAZARDS6/2889 2026-08-07 19:58Z – 2026-08-21 04:00Z SFC–13,000 ft
4NM W RICHFIELD, UT, Friday, August 7, 2026 through Friday, August 21, 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 32
- 1295 ft AGL at event
- 145 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 3 kt crosswind component
Flight context
- N9LV
- Mike Lima
- PRM1
- KSLC → 92CA
- 2026-08-09 03:07 UTC
- 92CA runway 32
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