The U.S. aircraft register, updated daily
Accidents · NTSB BFO86FID05 · Preliminary: the investigation is not finished

Maule M-4-210C accident near Saluda, Virginia, May 31, 1986

On May 31, 1986 at about 2:30 pm local time, a Maule M-4-210C, registered N9861M, was substantially damaged in an accident near Saluda, Virginia (Hummel Field). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

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

What the record shows

Date
May 31, 1986 · about 2:30 pm local time · cases in 1986
Place
Saluda, Virginia · Hummel Field · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Maule M-4-210C · all M-4-210Cs on the register
Registration
N9861M · registry record · serial 1058C
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

WHILE ON FINAL APCH, THE ACFT STRUCK THE TOP SIDE OF A VAN WHICH WAS ON A ROAD OFF THE APCH END OF THE RWY. BOTH MAIN LANDING GEAR WERE SHEARED OFF AND THE PLT LANDED THE ACFT IN A GRASS AREA ALONG THE SIDE OF THE RWY. THE PLT REPORTED THAT A HIGH SINK RATE DEVELOPED DURING FINAL APCH.

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,800 hours in all; 350 in this make and model
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 1,525 hours
  • Last inspection: annual inspection, June 3, 1985; 54 hours since
  • Maximum gross weight: 2,100 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental IO-360-A (piston); 0 hours total

The flight

  • Departed from: King George VA at 2:00 pm
  • Destination: W75 Saluda VA
  • Flight plan: none
  • Runway 36, 2,500 ft by 45 ft

Weather at the time

  • Light: daylight
  • Wind: from 010° at 6 knots
  • Visibility: 6 statute miles
  • Sky: broken clouds at 25,000 ft; not recorded at 25,000 ft
  • Temperature: 82°F (28°C), dew point 66°F (19°C)
  • Altimeter: 29.00 inHg
  • Observation at 2:30 pm from PHF, 34 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.

Other NTSB records under N9861M the same tail number, which may have belonged to a different aircraft at the time

1992-10-31ATL93LA020 · accident near Pickens, SC · substantial damage · no injuries

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/BFO86FID05.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.