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

Piper PA-28-180 accident near Grass Valley, California, August 14, 2000

On August 14, 2000 at about 3:57 am local time, a Piper PA-28-180, registered N16411, was substantially damaged in an accident near Grass Valley, California (Nevada County Air Park airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to attain proper alignment with the runway during approach for landing. Contributing factors were the pilot's inadequate and improper preflight planning and in-flight decision.

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

What the record shows

Date
August 14, 2000 · about 3:57 am local time
Place
Grass Valley, California · Nevada County Air Park · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Piper PA-28-180 · all PA-28-180s on the register
Registration
N16411 · no longer on the register · serial 28-7305246
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

On a bright night, the pilot attempted to land on runway 07. At the time, the runway lights were not operating. On final approach, the pilot failed to attain alignment with the desired runway and lined up with a parallel taxiway. About 20 feet above the ground the pilot increased engine power attempting to correct the misalignment. However, the airplane touched down in rough terrain next to the runway. Thereafter, the airplane veered into a ditch and came to rest against a berm. The pilot indicated that he was familiar with the airport, having been based there during the previous 10 years. He indicated a lack of awareness that a NOTAM had been recently issued indicating the airport was closed for night operations. The pilot's airplane contained adequate fuel to proceed to nearby alternate airports.

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: single-engine land
  • Flight time: 1,648 hours in all; 1,513 in this make and model; 21 in the last 90 days; 7 in the last 30 days; 1,535 as pilot in command
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 2,677 hours
  • Last inspection: annual inspection, June 16, 2000; 17 hours since
  • Maximum gross weight: 2,450 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-360-A4A (piston); 0 hours total

The flight

  • Departed from: RNO Reno NV at 2:45 am
  • Destination: O17
  • Flight plan: none
  • Runway 7, 4,350 ft by 75 ft

Weather at the time

  • Light: night, bright
  • Wind: from 040° at 3 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 151°F (66°C), dew point 90°F (32°C)
  • Altimeter: 30.00 inHg
  • Observation at 5:01 am from BLU, 14 miles away

Injuries

FatalSeriousMinorNone
Crew1

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.