LOST56 was operating from KSTS to KSLI on 2026-06-14. SkyMeter detected a low approach-stability score at Los Alamitos Army Air Field (KSLI) on runway 22L at 21:36 UTC. Trace data at the event: 1157 ft AGL, 131 kt GS. Approach stability score: 41/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 10 kt wind, 3 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/2969 2026-05-26 17:44Z – 2026-06-26 16:00Z SFC–4,000 ft
GARDEN GROVE, CA, Tuesday, May 26, 2026 through Friday, June 26, 2026 UTC
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/4189 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Los Angeles, CA, Monday, June 1, 2026 through Monday, July 20, 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/4197 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
GOLETA, 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 → - SECURITY6/6445 2026-06-10 07:01Z – 2026-06-15 06:59Z SFC–1,000 ft
Los Angeles, CA, Wednesday, June 10, 2026 through Sunday, June 14, 2026 Local
View FAA NOTAM → - SECURITY6/7265 2026-06-12 21:07Z – 2026-07-16 06:29Z SFC–400 ft
Manhattan Beach, CA
View FAA NOTAM → - SECURITY6/7814 2026-06-14 17:00Z – 2026-06-14 22:00Z SFC–400 ft
HOLLYWOOD, CA, Sunday, June 14, 2026 Local
View FAA NOTAM → - HAZARDS6/8214 2026-06-14 17:34Z – 2026-06-17 07:00Z SFC–400 ft
3.8NM NW TRACY, CA, Sunday, June 14, 2026 through Wednesday, June 17, 2026 UTC
View FAA NOTAM → - SECURITY6/6669 2026-06-14 18:00Z – 2026-06-14 23:00Z SFC–400 ft
Las Vegas, NV, Sunday, June 14, 2026 Local
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 22L
- 1157 ft AGL at event
- 131 kt ground speed
- 0 fpm vertical
- Approach stability 41/100
- 10 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KSLI 152155Z 22012KT 10SM FEW030 BKN150 BKN250 28/17 A3000 RMK AO2A SLP162 T02830165
Flight context
- LOST56
- C560
- KSTS → KSLI
- 2026-06-14 21:36 UTC
- KSLI runway 22L
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