Amateur-built VANS RV 7A accident near Dayton, Nevada, March 8, 2015
On March 8, 2015 at about 10:20 pm local time, a 2006 amateur-built VANS RV 7A, registered N51MJ, was substantially damaged in an accident during approach near Dayton, Nevada (Dayton Valley Airpark airport). It was a personal flight under general aviation rules (Part 91). 2 people had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A loss of engine power during descent for reasons that could not be determined because postaccident examination of the engine revealed no anomalies that would have precluded normal operation.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 8, 2015 · about 10:20 pm local time · cases in 2015
- Place
- Dayton, Nevada · Dayton Valley Airpark · cases near this airport · map
- Type
- Accident
- Injuries
- 2 people had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Amateur-built VANS RV 7A, built 2006
- Registration
- N51MJ · registry record · serial 70661
- 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 he departed the airport and flew at cruise altitude at 11,500 ft. About 10 miles from his destination airport, he started the descent to the traffic pattern altitude of about 6,000 ft. About 3 miles from the airport, he realized that the engine had quit without any indications or warning. The propeller was still windmilling, and he checked the engine gauges and noted that the oil pressure and temperature indications were good. He switched fuel tanks and tried to restart the engine without success. The airplane landed in a field short of the runway and then came to rest inverted. The pilot reported that he usually keeps the mixture control lever about half to three-quarters of the way out almost the entire time he flies. He added that the only time he ever needs to change the fuel mixture is while flying above 14,500 ft. Postaccident examination of the engine revealed no anomalies that would have precluded normal operation. The reason for the loss of engine power could not be determined.
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
- Loss of engine power (total) during approach defining event
- Off-field or emergency landing during approach
- Nose over/nose down during landing (flare/touchdown)
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
Pilot
- Certificate: commercial pilot
- Ratings: single-engine land
- Flight time: 1,030 hours in all; 303.2 in this make and model; 26 in the last 90 days
- Last flight review: September 11, 2014
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 303.3 hours
- Last inspection: continuous airworthiness programme, February 4, 2015; 15 hours since
- Maximum gross weight: 1,800 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming IO-360 Series (piston); 551 hours total
The flight
- Departed from: AUN Auburn CA at 9:00 pm
- Destination: A34 Dayton NV
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 050° at 4 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 66°F (19°C), dew point 50°F (10°C)
- Altimeter: 30.12 inHg
- Observation at 10:15 pm from CXP, 10 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
5 documents, released by the NTSB on December 7, 2015. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 18 pages | View Download |
| 2 | Record of Conversations - Pilot | PDF, 2 pages | View Download |
| 3 | Record of Email - FAA | PDF, 1 page | View Download |
| 4 | Excerpts from Lycoming Operator's Manual | PDF, 2 pages | View Download |
| 5 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N51MJ the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N51MJ on the register today · the tail number may have moved to another aircraft since
- Engine: Lycoming IO-360 Series 8,560 aircraft carry this series today · as the NTSB recorded it
- Dayton Valley Airpark · nearest airport
- Auburn Municipal · departed from
- Accidents and incidents in Nevada 1,294 since 1982 · 223 in the last ten years
- Nevada 4,584 aircraft registered
- Other NTSB records under N51MJ 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/WPR15LA127.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
