ERA10FA364 · S.C. Aerostar S.A. Yak52
S.C. Aerostar S.A. Yak52 · Accident: loss of engine power (total) during initial climb
From Portland International Jetport (PWM) to Portland International Jetport (PWM)
Event
- NTSB case
- ERA10FA364
- 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
S.C. Aerostar S.A. Yak52
- Aircraft type
- S C Aerostar YAK52
- 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
- N52MY
- Operator
- Mark H Haskell · private individual
- Onboard fatalities
- Unknown
- Route
- From Portland International Jetport (PWM), South Portland, METo Portland International Jetport (PWM), South Portland, ME
- 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
- 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 (total)
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot had not flown any airplane in almost 2 years. The purpose of the flight was for the pilot to obtain a biennial flight review from an instructor. Additionally, the accident flight was the first flight after the airplane's most recent annual condition inspection, which was completed about 2 weeks before the accident. The airplane made two touch-and-go landings uneventfully. The third landing was full-stop, followed by the pilot back-taxiing to the run-up area and testing the engine.
Following the engine run-up, the pilot intended to take off again; he told the air traffic controller that he wanted to fly over the airport at 3,000 feet to do a system check. A witness stated that, during the takeoff, the wings started to rock back and forth. The pilot indicated to the air traffic controller that he wanted to return to the airport, and he began a slow left turn. About one-fourth of the way through the turn, the airplane stalled and descended nose-low into the ground.
Examination of the wreckage revealed that one wooden propeller blade had separated at the hub and the other blade had separated about mid-span. The propeller blade and engine damage were consistent with little or no rotation at impact. Adequate fuel was found in the fuel system, and no evidence of contamination was noted. On-scene and metallurgical examination of the wreckage and fuel components did not reveal any preimpact mechanical malfunctions.
Although this airplane had a history of fuel flow obstruction due to debris in the fuel system caused by torn hoses as a result of the installation of English-size fuel hoses rather than metric, no evidence of tear debris was found in the fuel system of the accident airplane.
Probable cause
The pilot did not maintain adequate airspeed during an emergency return to the airport following a total loss of engine power, which resulted in an inadvertent stall. Contributing to the accident was a total loss of engine power for undetermined reasons and the pilot's lack of recent flying experience.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10FA364
- Event ID
- 20100717X74629
- Case number
- ERA10FA364
- 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: 95e40a1c632fdc8c428ac89f6c4fdd6994417c764fd4f8524065d3f81901e8c3; retrieved 2026-09-13T20:57:13.910Z.