Stall warning — N347DB

2026-06-30 13:02 UTC· 53NJ KACY· SF50

N347DB was operating from 53NJ to KACY on 2026-06-30. SkyMeter detected a stall warning at 13:02 UTC. Trace data at the event: 13007 ft AGL, 75 kt GS. Approach stability score: 48/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, 3 kt crosswind component. A stall flag is raised when the inferred angle of attack and observed airspeed are consistent with a stalled wing. Stall events on general-aviation trainer aircraft are predominantly stall-recognition practice during primary flight training, not safety-of-flight incidents. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

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

    Atlantic City, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Atlantic City, NJ

    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

  • 13007 ft AGL at event
  • 75 kt ground speed
  • 0 fpm vertical
  • Approach stability 48/100
  • 4 kt wind
  • 3 kt crosswind component

Flight context

  • N347DB
  • SF50
  • 53NJ → KACY
  • 2026-06-30 13:02 UTC

All events on this flight

Stall warning 13:02:36 UTC · · 13,007 ft AGL · 75 kt GS
Stall warning 13:02:36 UTC · · 13,007 ft AGL · 75 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