ATL03FA009 · Beechcraft A60
Beechcraft A60 · Accident: partial loss of engine power (mechanical failure) en route
From Delaware County Johnson Field (MIE) to Melbourne Orlando International Airport (MLB)
Event
- NTSB case
- ATL03FA009
- 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
- 2 · 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
Beechcraft A60
- Aircraft type
- Beechcraft 60
- 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
- N73CR
- Operator
- J. P. R. Comeault · private individual
- Onboard fatalities
- Unknown
- Route
- From Delaware County Johnson Field (MIE), Muncie, INTo Melbourne Orlando International Airport (MLB), Melbourne, 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
- En route · cruise
- First occurrenceThe 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
- Partial loss of engine power (mechanical failure)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was equipped with two experimental Engine AIR Power Systems TSIVD-427, 500-horsepower, liquid-cooled, turbocharged, V8 engines. During previous flights, the right engine lost boost then overboosted intermittently, and attempted repairs were unsuccessful. The pilot elected to fly the airplane to its home base for further troubleshooting. During cruise flight, the pilot reported an engine was surging, declared an emergency, and received vectors toward the airport. The airplane collided into a field beside the airport runway and caught fire. The airplane had a total of 8 to 10 hours of flight time at the time of the accident. Records revealed that two days after the airplane's first test flight, the pilot flew the airplane from Melbourne, Florida, to an airport 336 nm miles away, then flew it to Canada to display it at a fly-in.The FAA operating limitations for the airplane restricted its operation to flight test only, which was proposed to consist of 100 flight hours, since the installation of the modified engines. No single-engine performance data was available for this airplane. Examination of the engines and accessories revealed extensive fire and impact damage. Continuity of the crankshaft, valves, rods, and pistons was established for the right engine by manually rotating the propeller reduction control unit.
Probable cause
The loss of power in one engine and the loss of control for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL03FA009
- Event ID
- 20021029X05401
- Case number
- ATL03FA009
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2002-10-24.
- API snapshot SHA-256: 983edd0682490d263bf7be3affc364c39ab7def9ade024fe3d42b1ab989493fa; retrieved 2026-09-20T19:43:32.324Z.