FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA03LA080 · Ditommasso-Keminski Great Lakes 2T-1A

22 Mar 2003 · Daytona Beach, FL, United States

Ditommasso-Keminski Great Lakes 2T-1A · Accident: total loss of engine power (mechanical failure) during initial climb

From Lakewood Ranch Medical Center Helistop (7FL9) to an unrecorded destination

Report a problem

Event

NTSB case
MIA03LA080
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

Ditommasso-Keminski Great Lakes 2T-1A

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
N1980A
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lakewood Ranch Medical Center Helistop (7FL9), Daytona Beach, FLTo not recorded
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
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
Total loss of engine power (mechanical failure)
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/mush
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

  • Pilot in command › Airspeed(vs), not maintained
  • Pilot in command › Operation with known deficiencies in equipment, performed
  • Pilot in command › Preflight planning/preparation, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot stated that he did a thorough preflight, run up, the takeoff checklist and took off from runway 05 at Spruce Creek Airport. Approximately 300 to 400 feet off the end of the runway he said the engine started to surge, and after a few surges it ceased operating completely. The pilot said that in order to avoid houses and trees, he attempted a turn to runway 23. He said he performed pre-landing tasks, and during his attempt to land on runway 23, it became apparent that he was not going to make it, so he landed in the only available open area for runway 5, in a wings level attitude. The airplane flipped over on its back and stopped. The passenger stated that they were flying the airplane on a flight immediately preceding the accident flight, and when they first took off on that flight he knew something was wrong. He stated that he smelled "smoke from the engine, or some kind of burning smell", and that they then landed because something was wrong. He said the pilot then did nothing other than "reved the engine before taking off again." During the takeoff, the passenger said that they got to an altitude of about 100 feet over the treetops and the engine started to stop and start. He said they lost altitude slowly at first, and as the pilot tried to turn around and come back toward the runway, he only made it to a position perpendicular to the end of the runway, before they started loosing altitude drastically. He said they went down at an angle into the water ditch at the and of the runway. An FAA inspector who responded to the accident, conducted examinations of the airframe and engine. According to the inspector, no preaccident anomalies were evident, and cold compressions were low on cylinders, but consistent with those obtained from a Franklin engine. The inspector further stated that when the engine was first installed on the airframe, the accessories had been swapped from another engine on to the accident engine. The Bendix model PS-5C pressure carburetor was examined, under NTSB supervision, at an FAA certified repair facility. The manual mixture control had incurred damage, and dark deposits had been baked on to the throttle body, consistent with that of an engine having been operating very rich. A large amount of engine oil in the venturi area, and during teardown, an air passage on the air side of the outer valve was found to have oil present, consistent with there being anomalies internal to the engine.The filter was clean and residue/contamination was found under the screen.

Probable cause

The pilot's improper preflight planning/decision to perform a second flight with known deficiencies in equipment, and his failure to maintain airspeed above the airplane's stall speed while maneuvering to reverse direction to land, after the engine subsequently ceased to operate, which resulted in a stall/mush, an inflight lost of control, an uncontrolled descent, and an impact with a ditch.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA03LA080
Event ID
20030326X00391
Case number
MIA03LA080
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: 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: ed6ab13f2f4ce930b3ca51fdec9f9e52d7d5732f2d85b4765474316c573fe742; retrieved 2026-09-21T09:30:46.501Z.