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

Piper PA-34-220T accident near Battle Mountain, Nevada, July 22, 2007

On July 22, 2007 at about 11:45 pm local time, a Piper PA-34-220T, registered N275JM, was substantially damaged in an accident near Battle Mountain, Nevada (Battle Mountain airport). It was a business 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

The pilot's failure to maintain directional control.

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

What the record shows

Date
July 22, 2007 · about 11:45 pm local time
Place
Battle Mountain, Nevada · Battle Mountain
Type
Accident
Injuries
2 people had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Piper PA-34-220T · all PA-34-220Ts on the register
Registration
N275JM · registry record · serial 34-8133221
Damage
Substantial damage
Flight
Business flight · general aviation rules (Part 91)

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

After landing just beyond the runway threshold, the airplane yawed left and departed the runway, colliding with a berm. The airplane continued over the berm and came to rest just beyond, on the rising wall of a ditch. Post accident investigation revealed no discrepancies in the nose wheel steering system or braking system. The airplane came to rest approximately 3,200 feet from the pilot's reported touchdown point. A typical ground roll under the reported conditions was calculated to be approximately 2,350 feet. The main landing gear and nose gear tires exhibited flat spots and striations. Investigators inspected the nose gear of an exemplar Piper PA-34 airplane as it cycled in a retraction and extension sequence. The nose gear stayed centered throughout its travel and did not cant during the sequence until it was in the vicinity of the wheel well.

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

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 324 hours in all; 144 in this make and model; 91 in the last 90 days; 22 in the last 30 days; 172 as pilot in command
  • Last flight review: June 1, 2007
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Airframe total time: 4,725 hours
  • Last inspection: annual inspection, March 1, 2007; 123 hours since
  • Maximum gross weight: 4,750 lb
  • Landing gear: retractable
  • Engine 1: Continental TSIO-360 (piston); 0 hours total
  • Engine 2: Continental LTSIO-360 (piston); 0 hours total

The flight

  • Departed from: F70 French Valley CA at 8:15 pm
  • Destination: BAM Battle Mountain NV
  • Flight plan: IFR
  • Runway 30, 7,300 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 260° at 8 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 99°F (37°C), dew point 28°F (-2°C)
  • Altimeter: 30.03 inHg
  • Observation at 11:56 pm from WMC, 46 miles away

Injuries

FatalSeriousMinorNone
Crew1
Passengers1

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.