ERA12LA077 · Ercoupe 415-C
Ercoupe 415-C · Accident during takeoff
From South Lakeland Airport (X49) to Albert Whitted Airport (SPG)
Event
- NTSB case
- ERA12LA077
- 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
Ercoupe 415-C
- Aircraft type
- Ercoupe 415
- 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
- N99168
- Operator
- Robert Van Wagnen
- Onboard fatalities
- Unknown
- Route
- From South Lakeland Airport (X49), Mulberry, FLTo Albert Whitted Airport (SPG), St. Petersburg, 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
- 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
- Miscellaneous/other
- 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 › Action/decision
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The medically unqualified pilot filled the airplane’s fuel tanks and flew about 45 minutes to another airport, where the airplane remained on the ground about 2 hours and no fuel or maintenance services were performed. The pilot agreed to fly a passenger, who was a student pilot, to another airport. The passenger reported that, after boarding the airplane, he was not briefed on how to use the lapbelt, which the pilot secured for him. The passenger also reported that the pilot did not ask him his weight for the purpose of weight and balance calculations. The pilot did not perform a preflight inspection per the passenger’s account. Based on all available data from the pilot, maintenance records, and airplane documents located in the wreckage, the airplane was near or at its maximum gross weight at the time of engine start. After taxiing to the departure runway, the pilot did not perform an engine runup. He then taxied onto the grass runway, applied the brakes, and applied full power. The pilot reported that the airplane accelerated but not as fast as he thought it should have. The pilot reported that it took a long time to accelerate to 60 mph, and, about the point when he was considering aborting the takeoff, the airplane became airborne.
After becoming airborne, the pilot stated that the airplane climbed to 400 feet, cleared power lines, then began descending. He maneuvered the airplane toward a clearing, and, while descending, the right wing collided with trees. The airplane then impacted the ground in a right-wing-low attitude and a fire ensued. The pilot and passenger exited the airplane. The passenger later reported having difficulty unlatching his restraint because he was not familiar with it. The delay in releasing his restraint most likely resulted in greater burn injury to the passenger than had it been immediately released.
Postaccident examination of the engine revealed no compression in three of the four cylinders, but this was most likely due to the postcrash fire. Further examination of the thermally damaged engine revealed that the left magneto produced spark when rotated by hand, but the right magneto did not produce spark. Postaccident inspection of the right magneto revealed extensive heat damage, which precluded operational testing; therefore, no determination could be made as to whether there was preimpact failure or malfunction of the right magneto. Based on available evidence, the airplane’s poor acceleration during takeoff was most likely due to being near or at its maximum gross weight and operating from a grass runway. The pilot should have aborted the takeoff once he recognized the airplane’s poor acceleration performance.
Probable cause
The pilot’s failure to abort the takeoff after recognizing the airplane’s poor performance during the takeoff roll. Contributing to the passenger’s injuries was the pilot’s failure to provide a briefing on the use of the lapbelt, which delayed the passenger’s exit from the wreckage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12LA077
- Event ID
- 20111121X82500
- Case number
- ERA12LA077
- 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, coordinates. 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: f96390bdd2e13c0ab66326ccd8b3c0ae5f95f6aa4781f6d25fd4c015e42dca41; retrieved 2026-09-15T16:57:03.409Z.