NYC03CA152 · Maule MX-7-235
Maule MX-7-235 · Accident: loss of control in flight during landing
From Pittsburgh/Butler Regional Airport (BTP) to East Brady, PA (no airport)
Event
- NTSB case
- NYC03CA152
- 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
- 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
Maule MX-7-235
- Aircraft type
- Maule MX-7
- 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
- N70LB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Pittsburgh/Butler Regional Airport (BTP), Butler, PATo East Brady, PA (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
- Landing · flare/touchdown
- 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
- Loss of control in flight
- 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 › Aircraft control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot set up for a river landing by first circling the touchdown zone twice to check for obstacles, and waiting for boat traffic to clear. The pilot maintained an airspeed of about 75 knots during the approach, and slowed to an estimated 60 knots just above the water. During the touchdown, the airplane bounced, and the pilot added power to cushion the landing. The airplane touched down on the water on its left float, bounced onto its right float, then again on its left float. During the last bounce, the left strut impacted the fuselage, and the airplane came to rest on the shore of the river. Examination of the airplane by a Federal Aviation Administration inspector revealed substantial damage to both pontoons, both wings, the engine cowling, and the propeller. No mechanical anomalies were noted with the airplane.
Probable cause
The pilot's failure to maintain control of the airplane during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC03CA152
- Event ID
- 20031107X01872
- Case number
- NYC03CA152
- 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, coordinates. 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: 5e553d2859b6767240f2471ebb711634c8c2312c90f3f0cd257dd1a1004c38c0; retrieved 2026-09-21T19:25:43.610Z.