ERA20FA043 · Bushby BUSHBY MUSTANG M II
Bushby BUSHBY MUSTANG M II · Accident: abrupt maneuver during takeoff
From Peter Prince Field (2R4) to an unrecorded destination
Event
- NTSB case
- ERA20FA043
- 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
- 1 · 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
Bushby BUSHBY MUSTANG M II
- Aircraft type
- Bushby MUSTANG
- 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
- N24GL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Peter Prince Field (2R4), Milton, FLTo not recorded
- Aircraft age
- About 17 years (built 2002)
- 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
- Abrupt maneuver
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Witnesses observed the pilot of the experimental, amateur-built airplane perform a touch-and-go-landing on the 3,701-foot-long runway before it pitched up “fairly aggressively" and entered a near vertical climb to about 50 ft. The airplane then stalled and entered a spin toward the ground. None of these witnesses heard the airplane’s engine prior to impact. The pilot told a friend that he had to reject a takeoff about 3 weeks prior due to a loss of engine power, but the pilot never said what caused the engine to lose power. The pilot did state that he was having issues with the electronic magnetos. A mechanic had replaced all eight automotive spark plugs 2 days before the accident due to an excessive rpm drop on each electronic magneto. A post-maintenance test run of the engine revealed that replacing the spark plugs rectified the problem. The pilot told the mechanic that he would do an extensive engine run-up before he flew the airplane, which he did (per a witness) on the morning of the accident. A postaccident examination of the engine, including both magnetos and the spark plugs, revealed no mechanical deficiencies that would have contributed to a loss of engine power. Examination of the fuel system revealed a small amount of water and corrosion in the carburetor bowl, the accelerator pump chamber, and the fuel inlet screen port. Maintenance records revealed that a mechanic had drained the main fuel tank at the last inspection due to water in the tank. The mechanic said he dried the tank and added fresh fuel but did not check the carburetor for water. A witness said it was not unusual to see pilots flying their sport airplanes low and level over the runway before making a steep climb near the end of the runway, and this is what he thought the pilot was doing. The airplane stalled and spun to the ground from a height of about 50 ft, which was too low for the pilot to recover. It is possible that the engine experienced a loss of power due to fuel contamination, but the pilot’s actions were not consistent with a power loss prior to him pulling the airplane into a climb. Since no mechanical anomalies were observed with the airplane’s flight control system that would have precluded normal operation, the pilot failed to maintain a proper angle of attack and airspeed on takeoff, which resulted in an aerodynamic stall at an altitude that was too low for him to recover. Diphenhydramine was detected in the pilot’s blood and urine; however, the levels were not sufficient to contribute to the accident.
Probable cause
The pilot’s failure to maintain control of the airplane on takeoff, which resulted in an aerodynamic stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20FA043
- Event ID
- 20191124X11831
- Case number
- ERA20FA043
- 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: 27a72dd2dca5edc6afd5e08a0a00c4554cb92adbefb76cd201df7fdf94ff8428; retrieved 2026-09-15T07:08:38.168Z.