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

Amateur-built ZENITH CH 801 accident near Brigham City, Utah, March 11, 2023

On March 11, 2023 at about 6:30 pm local time, a 2006 amateur-built ZENITH CH 801, registered N639BH, was substantially damaged in an accident during landing (flare/touchdown) near Brigham City, Utah (Brigham City Rgnl airport). 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 pilot’s improper flare, which resulted in a hard landing following a reported loss of engine thrust for undetermined reasons.

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

What the record shows

Date
March 11, 2023 · about 6:30 pm local time · cases in 2023
Place
Brigham City, Utah · Brigham City Rgnl · 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
Amateur-built ZENITH CH 801, built 2006
Registration
N639BH · registry record · serial 841534
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 the airplane sustained a loss of engine thrust during the initial takeoff climb, but the engine continued to run. The pilot elected to land on the remaining runway; however, during the landing flare, the airplane landed hard on its nose and the nose landing gear collapsed. Additionally, the pilot stated that he defueled about 40 gallons of fuel from the airplane after the accident. A visual inspection of the fuel system was conducted, and continuity was established from the main fuel tanks throughout the system; however, fuel was not observed within the fuel system. A postaccident engine ground run was accomplished, and the engine performed at various power settings. Due to a damaged propeller, the propeller governor was removed and functionally tested; it performed within manufacturer's specifications. Postaccident examination of the airplane’s engine revealed no evidence of any preaccident mechanical malfunctions or failures that would have precluded normal operation. Examination of the propeller governor indicated no visible signs of damage and the governor control lever moved freely from stop to stop. The propeller governor was functionally tested and performed within the manufacturer's specifications. While it’s likely that the loss of engine thrust may have been fuel related, it could not be substantiated due to the available evidence.

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

  1. Hard landing during landing (flare/touchdown) defining event
  2. Unknown or undetermined during takeoff

The NTSB's findings

  • Aircraft › Aircraft power plant › Engine (reciprocating) › (general) › Unknown/Not determined other cases naming the engine
  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Not attained/maintained

Pilot

  • Certificate: private
  • Ratings: single-engine land; rotorcraft: helicopter
  • Flight time: 505 hours in all; 14 in this make and model; 9 in the last 90 days; 6 in the last 30 days; 335 as pilot in command
  • Last flight review: October 22, 2021
  • Medical certificate: BasicMed (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Passenger

  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 21 hours
  • Last inspection: condition inspection, September 6, 2022
  • Maximum gross weight: 2,200 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Franklin PZLR-6A-350CI (piston); 21 hours total

The flight

  • Flight plan: none
  • Runway 35, 8,900 ft by 100 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 340° at 3 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 36°F (2°C), dew point 23°F (-5°C)
  • Altimeter: 30.01 inHg
  • Observation at 11:30 am from KBMC

Weather report (METAR): METAR KBMC 111830Z AUTO 34004KT 10SM CLR 02/M05 A3001 RMK AO1 T00151048=

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Photographs from the investigation 4 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

8 documents, released by the NTSB on June 5, 2024. 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.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
  • N639BH on the register today · the tail number may have moved to another aircraft since
  • Engine: Franklin PZLR-6A-350CI · as the NTSB recorded it
Place

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