ERA13LA380 · Piper Aircraft Inc PA46R-350T
Pure Beauty Farms Piper Aircraft Inc PA46R-350T · Accident: loss of engine power (total) during initial climb
From Cat Cay Airport (MYCC) to Miami Executive Airport (TMB)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA13LA380
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper Aircraft Inc PA46R-350T
- Aircraft type
- Piper PA46
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N720JF
- Operator
- Pure Beauty Farms
- Onboard fatalities
- Unknown
- Route
- From Cat Cay Airport (MYCC), Cat CayTo Miami Executive Airport (TMB), Miami, FL
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Initial climb
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of engine power (total)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he applied full power, set the flaps at 10 degrees, released the brakes, and, after reaching 80 knots, he rotated the airplane. The pilot further reported that the engine subsequently lost total power when the airplane was about 150 ft above ground level. The airplane then impacted water in a nose-down, right-wing-low attitude about 300 ft from the end of the runway.
The pilot reported that he thought that the runway was 1,900 ft long; however, it was only 1,300 ft long. Review of the takeoff ground roll distance charts contained in the Pilot's Operating Handbook (POH) revealed that, with flap settings of 0 and 20 degrees, the ground roll would have been 1,700 and 1,150 ft, respectively. Takeoff ground roll distances were not provided for use of 10 degrees of flaps; however, the POH stated that 10 degrees of flaps could be used. Although the distance was not specified, it is likely that the airplane would have required more than 1,300 ft for takeoff with 10 degrees of flaps.
Examination of the engine revealed saltwater corrosion throughout it; however, this was likely due to the airplane's submersion in water after the accident. No other mechanical malfunctions or abnormalities were noted.
Examination of data extracted from the multifunction display (MFD) and primary flight display (PFD) revealed that the engine parameters were performing in the normal operating range until the end of the recordings. The data also indicated that, 7 seconds before the end of the recordings, the airplane pitched up from 0 to about 17 degrees and then rolled 17 degrees left wing down while continuing to pitch up to 20 degrees. The airplane then rolled 77 degrees right wing down and pitched down about 50 degrees. The highest airspeed recorded by the MFD and PFD was about 70 knots, which occurred about 1 second before the end of the recordings. The POH stated that, depending on the landing gear position, flap setting, and bank angle, the stall speed for the airplane would be between 65 and 71 knots.
Based on the evidence, it is likely that the engine did not lose power as reported by the pilot. As the airplane approached the end of the runway and the pilot realized that it was not long enough for his planned takeoff, he attempted to lift off at an insufficient airspeed and at too high of a pitch angle, which resulted in an aerodynamic stall at a low altitude. If the pilot had known the actual runway length, he might have used a flap setting of 20 degrees, which would have provided sufficient distance for the takeoff.
Probable cause
The pilot’s attempt to rotate the airplane before obtaining sufficient airspeed and his improper pitch control during takeoff, which resulted in the airplane exceeding its critical angle-of-attack and subsequently experiencing an aerodynamic stall at a low altitude. Contributing to the accident was the pilot’s lack of awareness of the length of the runway, which led to his attempting to take off with the airplane improperly configured.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13LA380
- Event ID
- 20130827X24543
- Case number
- ERA13LA380
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: a7fa873e9dac3098292b0017e73f480e32458b8823ab075d255046949b320695; retrieved 2026-09-15T22:38:09.459Z.