NYC98LA110 · Cessna 337B
Cessna 337B · Accident: in flight collision with object during initial climb
From Orange County Airport (MGJ) to Waterbury Oxford Airport (OXC)
Event
- NTSB case
- NYC98LA110
- 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
- 0
- 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
Cessna 337B
- Aircraft type
- Cessna 337
- 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
- N5471S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Orange County Airport (MGJ)To Waterbury Oxford Airport (OXC), Oxford, CT
- 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
- In flight collision with object
- 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
- Tree(s)
- 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 › Procedures/directives, not followed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was unable to start the rear engine of the Cessna 337. He then told some people he was going to make a single engine takeoff. The pilot initiated a takeoff with the rear engine not operating and the rear propeller not feathered. The airplane was observed to use all of the 5,000 foot runway to become airborne. After lift-off, the airplane did not climb, and it impacted trees off the departure end of the runway. An FAA inspector reported that there was a placard in the cockpit which stated, 'DO NOT INITITATE SINGLE ENGINE TAKEOFF.' Examination of the airplane revealed the rear propeller was not feathered, and the front propeller had separated from the engine at the crankshaft.
Probable cause
the pilot's improper decision to initiate a takeoff with the rear engine inoperative, which resulted in an airplane that could not climb sufficiently to clear obstacles (trees).
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC98LA110
- Event ID
- 20001211X10178
- Case number
- NYC98LA110
- 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. 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: 014b69040875dc13cbe80fa93bc021b7c92bed1c11cbf5187468c21af2266a89; retrieved 2026-09-20T22:35:17.639Z.