NYC00FA023 · Cessna T303
Cessna T303 · Accident: total loss of engine power (mechanical failure) en route
From Portland International Jetport (PWM) to Youngstown Warren Regional Airport (YNG)
Event
- NTSB case
- NYC00FA023
- 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
- 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
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Cessna T303
- Aircraft type
- Cessna 303
- 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
- N511AR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Portland International Jetport (PWM), Portland, METo Youngstown Warren Regional Airport (YNG), Youngstown, OH
- 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 135: Air Taxi & Commuter
- 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
- Total 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
- Substantial
Cause areas
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Missed approach, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While in cruise flight, at 6,000 feet, the left engine lost power. The pilot attempted a restart of the engine, but only about one-half rotation of the left engine propeller was observed, and the engine was secured. The pilot stated that he was unable to maintain altitude and initiated a decent. He requested and was cleared for an instrument approach at an airport where the weather conditions were, 1/4 statute mile of visibility, fog, and a vertical visibility of 100 feet. On the approach, at the minimum decent altitude, the pilot executed a missed approach. As the airplane climbed, the pilot reported to the controller that the 'best altitude [he] could get was 2,200 feet.' A second approach was initiated to the reciprocal runway. While on the second approach, the pilot 'was going to fly the aircraft right to the runway, and told the controller so.' He put the gear down, reduced power, and decided there was 'no hope for a go-around.' He then 'flew down past the decision height,' and about 70-80 feet above the ground, 'added a little power to smooth the landing.' The pilot also stated, 'The last thing I remember was the aircraft nose contacting the runway.' A passenger stated that once the pilot could not see the runway, [the pilot] 'applied power, pitched the nose up,' and attempted a 'go-around' similar to the one that was executed on the first approach. Disassembly of the left engine revealed that the crankshaft was fatigue fractured between connecting rod journal number 2 and main journal number 2. Review of the pilot's operating handbook revealed that the single engine service ceiling, at a weight of 4,800 pounds, was 11,700 feet. The average single engine rate of climb, at a pressure altitude of 6,000 feet, was 295 feet per minute. The average single engine rate of climb, at a pressure altitude of 1,625 feet, was 314 feet per minute. Review of the ILS approach plate for Runway 34 revealed that the decision height was 200 feet above the ground.
Probable cause
The pilot's improper in-flight decision to descend below the decision height without the runway environment in sight, and his failure to execute a missed approach. A factor in the accident was the failed crankshaft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC00FA023
- Event ID
- 20001212X20150
- Case number
- NYC00FA023
- 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: 422a7c4e0da62b526843370dd99ebcd0d0d72c9e4ce7a172eebe13fd6176b7a7; retrieved 2026-09-18T16:51:39.700Z.