DCM6317 was operating from KSUS to KTTN on 2026-08-16. SkyMeter detected a emergencydescent at 22:46 UTC. Trace data at the event: 42131 ft AGL, 550 kt GS. METAR at the time reported 4 kt wind, 1 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- VIP6/2748 2026-08-08 14:00Z – 2026-08-16 22:00Z SFC–4,999 ft
THURMONT, MD, Saturday, August 8, 2026 through Sunday, August 16, 2026 Local
View FAA NOTAM → - VIP6/4493 2026-08-14 20:15Z – 2026-08-16 22:30Z SFC–17,999 ft
Bedminster, NJ, Friday, August 14, 2026 through Sunday, August 16, 2026 Local
View FAA NOTAM → - VIP6/4494 2026-08-14 20:15Z – 2026-08-16 22:30Z SFC–17,999 ft
Bedminster, NJ, Friday, August 14, 2026 through Sunday, August 16, 2026 Local
View FAA NOTAM → - VIP6/5403 2026-08-16 20:15Z – 2026-08-16 22:00Z SFC–17,999 ft
Morristown, NJ, Sunday, August 16, 2026 Local
View FAA NOTAM → - VIP6/5404 2026-08-16 20:15Z – 2026-08-16 22:00Z SFC–17,999 ft
Morristown, NJ, Sunday, August 16, 2026 Local
View FAA NOTAM → - VIP6/4582 2026-08-16 21:45Z – 2026-08-16 23:30Z SFC–17,999 ft
Morristown, NJ, Sunday, August 16, 2026 Local
View FAA NOTAM → - VIP6/4583 2026-08-16 21:45Z – 2026-08-16 23:30Z SFC–17,999 ft
Morristown, NJ, Sunday, August 16, 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
- 42131 ft AGL at event
- 550 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 1 kt crosswind component
Flight context
- DCM6317
- GA5C
- KSUS → KTTN
- 2026-08-16 22:46 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