ERA20CA144 · Lake LA4 200
Lake LA4 200 · Accident: abnormal runway contact during takeoff
From Hickory, NC to Hickory, NC
Event
- NTSB case
- ERA20CA144
- 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
Lake LA4 200
- Aircraft type
- Lake LA4
- 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
- N84PF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hickory, NCTo Hickory, NC
- Aircraft age
- About 36 years (built 1984)
- 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
- Takeoff · rejected takeoff
- 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
- Abnormal runway contact
- 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
The pilot of the amphibious airplane was conducting a takeoff from a lake when he rejected the takeoff because there were power lines and a bridge in the direction of takeoff and he was unsure whether the airplane would be able to clear them. During the rejected takeoff, he reduced engine power; however, the airplane became airborne. He initiated a slight right turn toward more open water. After touching down, the airplane "water looped." The aft portion of the fuselage was substantially damaged during the accident sequence. The pilot reported that there were no preaccident mechanical malfunctions or failures of the airplane that would have precluded normal operation.
Probable cause
The pilot's inadequate preflight planning and attempted takeoff with obstacles in the direction of departure, and his failure to maintain control of the airplane during the rejected takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20CA144
- Event ID
- 20200406X44929
- Case number
- ERA20CA144
- 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: 090b52598c97a098e131c28022dfea7f193173149607ad4c2022d3e67febcb6b; retrieved 2026-09-16T11:25:04.321Z.