The U.S. aircraft register, updated daily
Accidents · NTSB SEA08LA087 · Final report

Maule M-4 accident near Bishop, California, March 7, 2008

On March 7, 2008 at about 11:00 pm local time, a Maule M-4, registered N51430, was substantially damaged in an accident during takeoff near Bishop, California (Eastern Sierra Regional Airpor airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A loss of engine power due to foreign object ingestion in the induction system, which resulted in a stuck/jammed exhaust valve during the takeoff.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
March 7, 2008 · about 11:00 pm local time
Place
Bishop, California · Eastern Sierra Regional Airpor · map
Type
Accident
Injuries
No one was hurt; 3 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Maule M-4 · all M-4s on the register
Registration
N51430 · registry record · serial 1097C
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot reported that just after takeoff the engine began running rough and he returned to the airport for a landing. The airplane touched down long and overran the runway. The pilot stated he intentionally ground looped the airplane in an effort to avoid a fence located beyond the overrun area of the runway. Post accident examination of the engine revealed that the alternate induction air valve (automatic air door) was separated from the induction bracket and a 2-inch-long AN3 bolt associated with door assembly was lodged between (holding open) the number six cylinder exhaust valve and corresponding exhaust port.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Powerplant sys/comp malf/fail during takeoff
  2. Loss of engine power (partial) during takeoff defining event
  3. Landing area overshoot during landing (landing roll)

The NTSB's findings

  • cause Aircraft › Aircraft power plant › Power plant › Air intake › Malfunction

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 1,500 hours in all; 180 in this make and model; 30 in the last 90 days; 10 in the last 30 days; 1,500 as pilot in command
  • Last flight review: November 20, 2008
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,194 hours
  • Last inspection: annual inspection, December 28, 2007
  • Maximum gross weight: 2,300 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental IO-360 (piston); 0 hours total

The flight

  • Departed from: BIH Bishop CA at 11:00 pm
  • Destination: BIH Bishop CA
  • Flight plan: none
  • Runway 12, 7,498 ft by 100 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 61°F (16°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.