Unstable approach — N4O5EH

KPDK · 3R

2026-07-17 10:53 UTC· KFXE KPDK· SOLOMON MARK TRUSTEE· LJ55

N4O5EH (Solomon Mark) was operating from KFXE to KPDK on 2026-07-17. SkyMeter detected a low approach-stability score at DeKalb Peachtree Airport (KPDK) on runway 3R at 10:53 UTC. Trace data at the event: 2093 ft AGL, 154 kt GS. 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 4 kt wind, 4 kt crosswind component, 14,484 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)
  • SECURITY6/4129 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    BOCA RATON, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4144 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    FORT LAUDERDALE, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4150 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    Palm Beach Gardens, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4153 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4156 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    TAMPA, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7906 2026-06-29 15:07Z – 2026-07-21 03:59Z SFC–400 ft

    Boca Raton, FL

    View FAA NOTAM →
  • SECURITY6/7880 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL

    View FAA NOTAM →
  • SECURITY6/7881 2026-07-05 14:07Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL

    View FAA NOTAM →
  • SECURITY6/7889 2026-07-07 13:07Z – 2026-07-21 03:59Z SFC–400 ft

    Palm Beach Gardens, FL

    View FAA NOTAM →
  • HAZARDS6/4885 2026-07-11 11:00Z – 2026-07-20 01:00Z SFC–5,000 ft

    14NM NE LAKE CITY, FL, Saturday, July 11, 2026 through Monday, July 20, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/4910 2026-07-11 11:33Z – 2026-07-20 01:00Z SFC–5,000 ft

    14NM NE LAKE CITY, FL, Saturday, July 11, 2026 through Monday, July 20, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/5640 2026-07-15 12:30Z – 2026-07-18 06:00Z SFC–2,500 ft

    MAYPORT, FL, Wednesday, July 15, 2026 through Saturday, July 18, 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
  • 2093 ft AGL at event
  • 154 kt ground speed
  • 0 fpm vertical
  • Approach stability 35/100
  • 4 kt wind
  • 4 kt crosswind component
  • 14,484 m visibility
  • KPDK 161453Z 00000KT 9SM FEW016 25/20 A3040 RMK AO2 SLP277 T02500200 51009

Flight context

  • N4O5EH
  • Solomon Mark
  • LJ55
  • KFXE → KPDK
  • 2026-07-17 10:53 UTC
  • KPDK runway 3R

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