Return to field — N400MZ

KPDK · 3R

2026-06-02 13:43 UTC· KPDK → KPDK· TEXTRON AVIATION INC· C25M

▶ Replay 📊 Analyse

N400MZ (Textron Aviation) had departed KPDK on 2026-06-02. SkyMeter detected a return to field at DeKalb Peachtree Airport (KPDK) on runway 3R at 13:43 UTC. Peak cruise altitude FL357, turnaround area near Cedar Bluff, US. Approach stability score: 35/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 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/3991 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    MARIETTA, GA, Monday, June 1, 2026 through Monday, July 20, 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 3R
  • 35748 ft AGL at event
  • 404 kt ground speed
  • 0 fpm vertical
  • Approach stability 35/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KPDK 162253Z AUTO 27007KT 10SM SCT060 OVC090 26/16 A2994 RMK AO2 SLP124 T02560156

Flight context

  • N400MZ
  • Textron Aviation
  • C25M
  • KPDK → KPDK
  • 2026-06-02 13:43 UTC
  • KPDK runway 3R

All events on this flight

Return to field 13:43:30 UTC · KPDK runway 3R · 35,748 ft AGL · 404 kt GS
Unstable approach 14:48:13 UTC · KPDK runway 3R · 2,118 ft AGL · 160 kt GS
Unstable approach 14:48:13 UTC · KPDK runway 3R · 2,118 ft AGL · 160 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· KPDK