Beech A23 accident near Hammonton, New Jersey, May 1, 2011
On May 1, 2011 at about 6:30 pm local time, a Beech A23, registered N3594R, was substantially damaged in an accident during takeoff (rejected takeoff) near Hammonton, New Jersey (Hammonton Municipal Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain directional control during the aborted takeoff.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 1, 2011 · about 6:30 pm local time
- Place
- Hammonton, New Jersey · Hammonton Municipal Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Beech A23 · all A23s on the register
- Registration
- N3594R · no longer on the register · serial M-783
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
According to the pilot, his original intent was to start, run-up, and then taxi his airplane on the day of the accident. At the completion of the run-up, the pilot taxied the airplane onto the active runway for a "fast taxi" and applied full engine power. The airplane achieved takeoff speed, the pilot pulled back on the control yoke, and the airplane lifted from the runway. The pilot then aborted the takeoff and lost directional control as the airplane touched down on the runway. The airplane impacted a fence, resulting in substantial damage to the wings. The pilot reported that there were no mechanical deficiencies with the airplane.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of control on ground during takeoff (rejected takeoff) defining event
- Runway excursion during takeoff (rejected takeoff)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 370 hours in all; 140 in this make and model; 0 in the last 90 days
- Last flight review: September 30, 2006
- Medical certificate: Class 3
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 2,343 hours
- Last inspection: annual inspection, July 1, 2010
- Seats: 4
- Landing gear: fixed
- Engine: Cont Motor IO-346 SERIES (piston); 0 hours total
The flight
- Departed from: N81 Hammonton NJ
- Destination: N81 Hammonton NJ
- Flight plan: none
- Runway 03, 3,601 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 110° at 10 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 63°F (17°C), dew point 50°F (10°C)
- Altimeter: 30.29 inHg
- Observation at 6:54 pm from ACY, 15 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.