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

Beech A36 accident near Provo, Utah, March 16, 2000

On March 16, 2000 at about 2:45 am local time, a Beech A36, registered N367T, was substantially damaged in an accident near Provo, Utah (Provo Municipal airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot misjudging the flare. Factors were dark night conditions, and the pilot's lack of recent experience in the type of operation (night landings).

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

What the record shows

Date
March 16, 2000 · about 2:45 am local time
Place
Provo, Utah · Provo Municipal · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Beech A36 · all A36s on the register
Registration
N367T · registry record · serial E-1043
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The purpose of the flight was for the pilot to regain night currency. He said the landing approach was 'completely in order. . .and everything was set up well. I was coming in directly to the mid portion of the runway.' When the pilot decreased power and flared, the airplane landed 'hard' and 'ballooned.' When the airplane touched down again, the nose gear collapsed and the airplane slid down the middle of the runway. Postaccident inspection by an FAA inspector disclosed the nose tire had blown out in three different spots in the tread area. Additionally, the FAA inspector reported that the nose landing gear was sheared off 'in the thickest part of the casting.' The assembly was located 300 feet back along the runway.

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: 142 hours in all; 80 in this make and model; 38 in the last 90 days; 12 in the last 30 days; 88 as pilot in command
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 850 hours
  • Last inspection: annual inspection, November 19, 1999; 58 hours since
  • Maximum gross weight: 3,600 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Continental IO-520-BA (piston); 0 hours total

The flight

  • Departed from: PVU at 2:30 am
  • Flight plan: none
  • Runway 31, 8,600 ft by 150 ft

Weather at the time

  • Light: night, dark
  • Wind: from 330° at 14 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 39°F (4°C), dew point 21°F (-6°C)
  • Altimeter: 30.00 inHg
  • Observation at 2:55 am from PVU

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.

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

2002-11-25FTW03FA048 · accident near Salem, UT · destroyed · fatal

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.