EmergencyDescent — LAN602

2026-03-30 12:39 UTC· B788

▶ Replay 📊 Analyse

LAN602 was inbound to KLAX on 2026-03-30. SkyMeter detected a emergencydescent at 12:39 UTC. Trace data at the event: 38511 ft AGL, 386 kt GS. Approach stability score: 93/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 4 kt wind, 3 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/0091 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft

    Coyote Wells, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local

    View FAA NOTAM →
  • SECURITY6/0092 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft

    CALEXICO, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4165 2026-02-14 07:00Z – 2026-08-15 06:59Z SFC–400 ft

    Nogales, AZ, Saturday, February 14, 2026 through Friday, August 14, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4160 2026-02-14 08:00Z – 2026-08-15 06:59Z SFC–400 ft

    Chula Vista, CA, Saturday, February 14, 2026 through Friday, August 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

  • 38511 ft AGL at event
  • 386 kt ground speed
  • 0 fpm vertical
  • Approach stability 93/100
  • 4 kt wind
  • 3 kt crosswind component

Flight context

  • LAN602
  • B788
  • 2026-03-30 12:39 UTC

All events on this flight

EmergencyDescent 12:39:54 UTC · · 38,511 ft AGL · 386 kt GS
EmergencyDescent 12:39:54 UTC · · 38,511 ft AGL · 386 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