Speed exceedance — N317DT
2026-06-27 22:33 UTC· KSNA → KOKC· C'EST LA VIE LLC· F2TH
N317DT (C'Est la VIE) was operating from KSNA to KOKC on 2026-06-27. SkyMeter detected a speed exceedance at 22:33 UTC. Trace data at the event: 23435 ft AGL, 519 kt GS. Approach stability score: 26/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 16 kt wind. An overspeed flag is raised when observed indicated airspeed exceeds the aircraft type's published Vmo (maximum operating speed) or Mmo (maximum operating Mach). Compressibility-correction bugs were a major false-positive source on the E75L and CRJ9 fleets prior to April 2026; current flags use the corrected IAS calculation. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4182 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Irvine, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4198 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
IRVINE, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4201 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Dana Point, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - HAZARDS6/8547 2026-06-16 02:03Z – 2026-06-30 03:00Z SFC–6,000 ft
3.1NM S CALIMESA, CA, Tuesday, June 16, 2026 through Tuesday, June 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/8709 2026-06-16 17:25Z – 2026-06-29 00:15Z SFC–6,000 ft
3.1NM S CALIMESA, CA, Tuesday, June 16, 2026 through Monday, June 29, 2026 UTC
View FAA NOTAM → - HAZARDS6/9123 2026-06-18 12:00Z – 2026-06-30 05:00Z SFC–14,000 ft
80NM N SILVER CITY, NM, Thursday, June 18, 2026 through Tuesday, June 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/9125 2026-06-18 14:00Z – 2026-07-02 04:00Z SFC–10,000 ft
45NM E MESA, AZ, Thursday, June 18, 2026 through Thursday, July 2, 2026 UTC
View FAA NOTAM → - HAZARDS6/9420 2026-06-20 21:25Z – 2026-07-04 04:00Z SFC–12,000 ft
40NM SE ALBUQUERQUE, NM, Saturday, June 20, 2026 through Saturday, July 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/9456 2026-06-21 13:00Z – 2026-07-05 04:00Z SFC–12,000 ft
40NM SE ALBUQUERQUE, NM, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/9455 2026-06-21 14:00Z – 2026-07-05 04:00Z SFC–9,000 ft
14NM E PAYSON, AZ, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/9496 2026-06-21 14:00Z – 2026-07-05 03:00Z SFC–13,000 ft
33NM W SHOW LOW, AZ, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/9548 2026-06-22 14:00Z – 2026-07-05 04:00Z SFC–10,000 ft
16NM NE SAN CARLOS, AZ, Monday, June 22, 2026 through Sunday, July 5, 2026 UTC
View FAA NOTAM → - HAZARDS6/9854 2026-06-23 14:00Z – 2026-07-06 04:00Z SFC–10,000 ft
45NM E MESA, AZ, Tuesday, June 23, 2026 through Monday, July 6, 2026 UTC
View FAA NOTAM → - HAZARDS6/0466 2026-06-24 16:30Z – 2026-06-30 03:00Z SFC–13,000 ft
50NM E ALBUQUERQUE, NM, Wednesday, June 24, 2026 through Tuesday, June 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/0842 2026-06-26 14:00Z – 2026-07-09 03:00Z SFC–10,500 ft
13NM SW FLAGSTAFF, AZ, Friday, June 26, 2026 through Thursday, July 9, 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
- 23435 ft AGL at event
- 519 kt ground speed
- 0 fpm vertical
- Approach stability 26/100
- 16 kt wind
- 0 kt crosswind component
Flight context
- N317DT
- C'Est la VIE
- F2TH
- KSNA → KOKC
- 2026-06-27 22:33 UTC
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