ERA10LA431 · Maxair MU 582 DRIFTER
Maxair MU 582 DRIFTER · Accident: loss of control in flight during initial climb
From Old Forge, NY (no airport) to Old Forge, NY (no airport)
Event
- NTSB case
- ERA10LA431
- 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
Maxair MU 582 DRIFTER
- Aircraft type
- Maxair MU-582
- 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
- N582RH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Old Forge, NY (no airport)To Old Forge, NY (no airport)
- 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 control in flight
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the passenger, the pilot had planned to fly the airplane to the opposite end of the lake. He said that the pilot taxied about 3/4 of the way down the lake, turned around, and started the takeoff roll. The airplane began to climb within 300 feet, but the pilot noticed an approaching line of trees on the shore, so he banked the airplane steeply to avoid hitting the trees. The passenger said that, when the pilot banked the airplane, all forward momentum was lost and they seemed to freefall. The passenger estimated that the airplane fell to the ground from a height of about 100 feet and impacted a swamp in a nose- down attitude. He said that the engine continued to operate throughout the entire accident sequence. A postaccident examination of the engine revealed no evidence of any preimpact mechanical malfunctions or failures.
Probable cause
The pilot's failure to use the full length of the lake, which necessitated a steep turn to avoid obstacles during takeoff that resulted in an accelerated stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10LA431
- Event ID
- 20100818X35504
- Case number
- ERA10LA431
- 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: 36f080931810eafc5ae9f855e837e81b6347c7f2e93de4b89d5b7c8693571337; retrieved 2026-09-13T21:00:31.565Z.