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

Amateur-built Fisher Celebrity accident near Greensboro, North Carolina, October 6, 2022

On October 6, 2022 at about 8:21 pm local time, a 2006 amateur-built Fisher Celebrity, registered N655WP, was substantially damaged in an accident during approach (VFR pattern downwind) near Greensboro, North Carolina (Piedmont Triad International A 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/mechanic’s failure to remove excess sealant from the header fuel tank after recent maintenance, which resulted in fuel starvation to the engine and a loss of engine power. Contributing to the accident was the pilot’s inflight decision making following the initial loss of engine power.

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

What the record shows

Date
October 6, 2022 · about 8:21 pm local time
Place
Greensboro, North Carolina · Piedmont Triad International A · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Amateur-built Fisher Celebrity NO SERIES, built 2006
Registration
N655WP · no longer on the register · serial CE-130
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot departed with an adequate supply of fuel in the airplane’s header fuel tank and remained in the airport traffic pattern. He reported that while on the downwind leg the engine “stumbled slightly.” The pilot turned the auxiliary fuel pump on and the airplane sustained a loss of engine power like it was, “starving for fuel.” He verified the fuel shutoff valve was fully open, retarded the throttle, and engaged the electric primer two to three times. The engine restarted, and the pilot continued in the traffic pattern downwind leg. Video recorded onboard the airplane during the flight, ADS-B flight track data, and air traffic control communication information indicated that following the loss/resumption of engine power, the pilot did not alter his previously established course, nor did he alert air traffic control to any difficulty. While on the downwind leg of the traffic pattern, air traffic control asked the pilot to extend his downwind leg in consideration of two other airplanes that were landing. The pilot was then cleared to land, when the airplane was about 1.5 nautical miles from the runway threshold, turning from the downwind toward a base traffic pattern leg. About that time the engine lost power again while the airplane was above a heavily forested residential area. Almost directly ahead of the airplane was a golf course fairway that was relatively free of obstacles. The pilot continued the right turn away from the fairway and toward the runway threshold, over an area densely covered by trees and houses. Although the pilot stated the airplane contacted a tree, which resulted in a right yaw and descent, based on recorded video the pilot likely exceeded the airplane’s critical angle of attack and the airplane stalled before impacting the tree. The airplane then descended to impact with the terrain and a residence. Postaccident examination of the wreckage revealed minimal fuel in the engine fuel system components. The header fuel tank contained 3 to 4 gallons of 100 low lead fuel with no water present. A foreign object recovered from the header fuel tank matched the color of material used by the pilot/mechanic to seal the flange of the recently replaced fuel sending unit. Based on this information, it is likely that when the fuel sending unit was replaced, excess sealant applied to the flange compressed out into the tank during installation. Although the header fuel tank outlet was not observed to be blocked by the foreign material inside the tank, the symptom reported by the pilot, like the engine was “starving for fuel,” and the lack of any appreciable amount of fuel in the engine fuel system components were consistent with fuel starvation and subsequent near total loss of engine power. Based on the inflight video, ADS-B track data, and air traffic control communications information, the initial loss of engine power occurred while the airplane was still early in its progression around the airport traffic pattern. While the pilot was able to restart the engine, he did not otherwise deviate from the established traffic pattern path to return to, or at least deviate closer toward, the runway. The pilot also did not advise air traffic control of any need to deviate due to the engine anomaly. Had he taken these actions, it is possible that the accident could have been avoided. Additionally, after the airplane’s engine lost power a second time, had the pilot committed to performing a forced landing to the golf course fairway ahead, instead of attempting to continue the flight over houses and trees toward the runway, it is likely that the severity of the accident could have been mitigated.

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. Off-field or emergency landing during enroute
  2. Loss of control in flight during maneuvering
  3. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
  4. Fuel starvation during approach (VFR pattern downwind) defining event

The NTSB's findings

  • Aircraft › Aircraft systems › Fuel system › Fuel distribution › Damaged/degraded
  • Personnel issues › Task performance › Maintenance › Replacement › Maintenance personnel
  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 1,529 hours in all; 59.6 in this make and model; 1 in the last 90 days; 1 in the last 30 days; 1,529 as pilot in command
  • Last flight review: November 19, 2020
  • Medical certificate: Sport Pilot
  • Seat: rear
  • Injury: minor injuries

The aircraft

  • Airframe total time: 155 hours
  • Last inspection: condition inspection, July 9, 2022; 1 hours since
  • Maximum gross weight: 1,250 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotec R-2800 (piston); 155 hours total

The flight

  • Flight plan: none
  • Runway 23R, 9,000 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 280° at 9 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 5,500 ft
  • Temperature: 75°F (24°C), dew point 52°F (11°C)
  • Altimeter: 30.02 inHg
  • Observation at 3:54 pm from KGSO, 2 miles away

Weather report (METAR): METAR KGSO 061954Z 28009KT 10SM FEW055 FEW250 24/11 A3002 RMK SLP158 T02440111 $=

Injuries

FatalSeriousMinorNone
Flight crew1

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

12 documents, released by the NTSB on October 30, 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.

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.