ERA09CA112 · Michael Muratore Vans RV-7
Michael Muratore Vans RV-7 · Accident: runway excursion during landing
From Bayport Aerodrome (23N) to Bayport Aerodrome (23N)
Event
- NTSB case
- ERA09CA112
- 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
Michael Muratore Vans RV-7
- Aircraft type
- Michael Muratore VANS
- 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
- N307MM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bayport Aerodrome (23N), Bayport, NYTo Bayport Aerodrome (23N), Bayport, NY
- 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
- 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
- Runway excursion
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While landing on an unimproved-turf airstrip, the pilot of the amateur-built airplane attempted to lower the flaps using the electric flap switch. He noted no extension of the flaps and re-cycled the switch. The flaps did not extend and the pilot decided to conduct a no-flap landing. The pilot stated that he made a "low approach to limit glide slope and maintained about 90 kias [knots indicated airspeed]." The airplane touched down in the first 1/3 of the runway, with the main landing gear contacting the ground first. The pilot pulled the control stick aft, allowing the tailwheel to contact the ground, and applied full brakes to slow the airplane. The airplane began sliding on the damp grass and impacted trees at the end of the runway, substantially damaging the left wing. Examination of the airplane by a Federal Aviation Administration inspector did not reveal evidence of any preimpact failures or malfunctions with the airplane.
Probable cause
The pilot's failure to stop the airplane within the available runway after touchdown. Contributing to the accident were the failure of the flap system as reported by the pilot and the damp grass.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09CA112
- Event ID
- 20081229X02028
- Case number
- ERA09CA112
- 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, 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: 9f8ee09cc4fb6924b46f577e0b9a85f62fd2ede6318ee56ec435e83951263f36; retrieved 2026-09-15T10:38:29.604Z.