FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13LA263 · Wilson William M CRICKET MC12

1 Jun 2013 · Doylestown, PA, United States

Wilson William M CRICKET MC12 · Accident: loss of engine power (partial) during takeoff

From Doylestown Airport (DYL) to Doylestown Airport (DYL)

Report a problem

Event

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

Wilson William M CRICKET MC12

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
N2SZ
Operator
Szabo John M
Onboard fatalities
Unknown
Route
From Doylestown Airport (DYL), Doylestown, PATo Doylestown Airport (DYL), Doylestown, PA
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
Loss of engine power (partial)
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 › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Although the gross weight at takeoff could not be determined, the airplane was a minimum of 30 pounds above the design gross weight (375 pounds), but 15 pounds under the builder-designated gross weight. Because the airplane was an experimental amateur built airplane, the builder can waiver from the design criteria, including gross weight; however, decreased performance will likely occur.

After rotation, the airplane flew several feet above the runway until about 2,100 feet down the 3,004-foot-long runway. The airplane then began a shallow climb and proceeded about ½ nautical mile west-northwest from the departure end of the runway flying at a low altitude. Two witnesses reported hearing sounds consistent with an engine(s) malfunction, while another witness located less than 200 feet from the accident site did not hear sputtering sounds. As the airplane approached a road for a forced landing with traffic ahead, it pitched up, rolled to the left, and collided with power lines then the ground. While two explosions were noted, the first likely occurred when the airplane collided with the power lines and would not have likely caused any burn injury to the pilot, while the second occurred at ground contact and was likely the result of rupture of the fuel tank, which resulted in the pilot's burn injuries. The drugs detected in the toxicology testing were consistent with those administered by medical personnel.

No evidence of preimpact failure or malfunction was noted to the flight controls, and examination of the heat-damaged engines revealed good compression in each cylinder. Both propeller blades of the right propeller were fractured, consistent with the engine developing power at impact, while both propeller blades of the left propeller were not fractured, which was consistent with the engine not developing power at impact. The reason for the lack of power from the left engine could not be determined during the postaccident examination of the engine.

Though it could not be determined whether the pilot intentionally remained close to the runway for more than 2/3's of its length, this would have been different from his past practices. Further, a prudent pilot would have initiated a normal climb after rotation for safety purposes. Therefore, the lack of climb performance should have been a clear indicator to the pilot to abort the takeoff, which he could have safely performed within the remaining runway distance.

Accounting for environmental conditions but excluding any issue related to inefficiency of the accident airplane's engines, propellers, or airframe, the single-engine and both-engine rate-of-climb at design gross weight would have been about 160- and 960 feet per minute, respectively. No determination could be made as to the actual values for the accident airplane. The operation of the airplane above the design gross weight would have further decreased the single-engine climb performance, although the exact decrease in performance could not be determined.

Probable cause

The pilot's failure to abort the takeoff after detecting the airplane’s degraded performance. Contributing to the accident were the likely loss of power from the left engine for reasons that could not be determined during the postaccident examination of the engine, and the operation of the airplane above the design gross weight, which resulted in decreased single-engine performance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13LA263
Event ID
20130601X50034
Case number
ERA13LA263
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: 8d382428edf68e52c8647efd4054ba43de85389fdb70e6d75f6861b60d35f610; retrieved 2026-09-14T15:57:44.415Z.