Piper PA-28RT-201T accident near Boca Raton, Florida, December 23, 2012
On December 23, 2012 at about 6:15 pm local time, a 1984 Piper PA-28RT-201T, registered N4340G, was substantially damaged in an accident during initial climb near Boca Raton, Florida (Boca Raton Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's improper landing flare after a loss of engine power shortly after takeoff, which resulted in a hard landing. The reason for the loss of engine power could not be determined based on the available information.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- December 23, 2012 · about 6:15 pm local time · cases in 2012
- Place
- Boca Raton, Florida · Boca Raton Airport · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-28RT-201T, built 1984 · all PA-28RT-201Ts on the register
- Registration
- N4340G · registry record · serial 28R-8431015
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot stated that a pretakeoff engine run-up revealed no anomalies and that he then initiated a takeoff. Shortly after rotation, the pilot selected the landing gear handle to the "up" position. When the airplane reached an altitude of about 100 ft above ground level, the engine suddenly "stopped without sputtering," and the airplane entered an aerodynamic stall. The pilot pitched the airplane's nose down and subsequently attempted to flare the airplane for landing; the airplane subsequently touched down on all three landing gear, which were in transition. The left main and nose landing gears collapsed, and the airplane slid off the left side of the runway, which resulted in substantial damage to both wings. Neither the engine nor the fuel system were examined following the accident, and the reason for the loss of engine power could not be determined.
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 engine power (total) during initial climb defining event
- Off-field or emergency landing during emergency descent
- Hard landing during landing
- Runway excursion during landing
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 4,100 hours in all; 3,900 in this make and model; 50 in the last 90 days; 15 in the last 30 days; 4,100 as pilot in command
- Last flight review: October 9, 2011
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 4,100 hours
- Last inspection: annual inspection, January 15, 2012; 100 hours since
- Maximum gross weight: 2,900 lb
- Seats: 4
- Landing gear: retractable
- Engine: Cont Motor TSIO-360 SER (piston); 100 hours total
The flight
- Departed from: BCT Boca Raton FL at 6:15 pm
- Destination: 2IS Clewiston FL
- Flight plan: none
- Runway 05, 6,276 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: from 110° at 9 knots
- Visibility: 10 statute miles
- Sky: scat at 3,800 ft
- Temperature: 72°F (22°C), dew point 52°F (11°C)
- Altimeter: 30.18 inHg
- Observation at 5:53 pm from PMP, 8 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on June 25, 2015. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Photo 1 - Left Wing Damage (Courtesy FAA) | PDF, 1 page | View Download |
| 3 | Photo 2 - Right Wing Damage (Courtesy FAA) | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N4340G on the register today · the tail number may have moved to another aircraft since
- Piper PA-28 Cherokee, Warrior, Archer and Arrow 18,620 registered today · the model family and its accident history
- Piper 44,839 aircraft on the register
- Engine: Cont Motor TSIO-360 SER 1,907 aircraft carry this series today · as the NTSB recorded it
- Boca Raton Airport · nearest airport
- Airglades Airport · bound for
- Accidents and incidents in Florida 6,111 since 1982 · 984 in the last ten years
- Florida 21,704 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA13LA099.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.