ASN Wikibase Occurrence # 279967
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can
submit corrected information.
Date: | Sunday 3 July 2022 |
Time: | 08:49 |
Type: | Extra EA 300/L |
Owner/operator: | Private |
Registration: | N343BH |
MSN: | 037 |
Year of manufacture: | 1996 |
Fatalities: | Fatalities: 1 / Occupants: 1 |
Aircraft damage: | Destroyed |
Category: | Accident |
Location: | near Boulder City Municipal Airport (BLD/KBVU), Boulder City, NV -
United States of America
|
Phase: | Manoeuvring (airshow, firefighting, ag.ops.) |
Nature: | Private |
Departure airport: | Las Vegas-Henderson Sky Harbor Airport, NV (HSH/KHND) |
Destination airport: | Las Vegas-Henderson Sky Harbor Airport, NV (HSH/KHND) |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:On July 3, 2022, about 0849 Pacific daylight time, an Extra Flugzeugbau GMBH EA 300/L Airplane, N343BH, was destroyed when it was involved in an accident near Boulder City, Nevada. The pilot was fatally injured. The airplane was operated as a Title 14 CFR Part 91 personal flight.
The pilot departed on a local flight to perform low-altitude maneuvers in a nearby desert valley. The pilot flew into a gap between ridgelines and performed maneuvers that consisted of flying low through the valley and then performing a turn and climb maneuver to fly in the opposite direction. The maneuvers were similar to aerobatic maneuvers called a wingover, in which the airplane makes a steep climb followed by a turn at the top of the climb using the rudder and a descent flying back in the opposite direction from which the maneuver began. If the rudder turn is executed right at the initiation of a stall, the maneuver is known as a stall turn or a hammerhead.
Three turn reversals were accomplished. On the first turn maneuver, the climb rate was nearly 15,000 fpm and the descent rate more than 10,000 fpm. Additionally, the load factor peaked about 3 g. The second turn maneuver was similar to the first but slightly less aggressive. On the third and final turn maneuver, when the accident occurred, the climb rate was about 6,500 fpm and the descent rate was about 6,800 fpm. The roll angles exceeded 90° at the peaks of the maneuvers. The airplane’s airspeed was close to the stall speed at the peak altitude of the first and last turn maneuvers.
According to a witness, the pilot planned to perform the flight maneuvers that morning while a ground photo shoot was taking place. On the final flyby, two witnesses observed the airplane fly overhead and pull up in a climb and subsequently enter a spin towards the ground. The airplane’s engine sounded normal during the flyby maneuvers.
A video taken by a witness showed the airplane performing the low altitude flybys near or below the ridgelines and then enter the vertical turn reversals maneuvers. On the final turn maneuver, the airplane went temporarily out of view, and when back in view, it was in a steep nose-down descent with rotation, consistent with a spin.
Impact marks at the accident site, witness observations, review of the flight data, and the video, were all consistent with the pilot losing control by exceeding the critical angle of attack of the airplane during a turn climb maneuver and entering a spin. In addition, examination of the airplane wreckage revealed no evidence of preimpact failures or malfunctions that would have precluded normal operation.
On the last turn maneuver, the pilot experienced a load factor of about 2 g that was the least amount of g sustained during the turn maneuvers performed by the pilot. Referencing the Federal Aviation Administration (FAA) Advisory Circular (AC) 91.61 on g effects; 2 g was substantially below the threshold and minimum range of grey out, which was the first effect of the g-forces that would affect the pilot. Therefore, it was likely that the pilot did not experience any adverse effects (greyout, blackout, or incapacitation) from the g load during the final turn maneuver.
The FAA Code of Federal Regulations (CFR) Title 14. 91.303 Aerobatic flight, states “No person may operate an aircraft in aerobatic flight - below an altitude of 1,500 ft above the surface.” The pilot was not in compliance with this requirement, which reduced his recovery margin.
Toxicology testing revealed that the pilot had used methamphetamine at some time before the accident. Methamphetamine and its metabolite amphetamine were detected at high concentration in the urine sample, and it was likely that the pilot was still under the influence and experiencing some effects of methamphetamine while flying. Pseudoephedrine and phenylpropanolamine, which are precursors for illicit production of methamphetamine, were detected in the urine. This further supports the evidence of recreational and illicit use of methamphetamine by the pilot. Methamphetamine effects include impaired judgment, impulsivity, and increased risk taking. Therefore, the effects from the pilot’s use of methamphetamine likely contributed to the accident.
Probable Cause: The failure of the pilot to maintain control of the airplane by exceeding the airplane’s critical angle of attack while maneuvering in a turning climb at a low altitude, which resulted in an aerodynamic stall and spin from which the pilot was unable to recover. Contributing to the accident was the pilot’s use of methamphetamine and decision to perform aerobatics below the required minimum altitude.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | WPR22FA240 |
Status: | Investigation completed |
Duration: | 1 year and 9 months |
Download report: | Final report |
|
Sources:
https://www.fox5vegas.com/2022/07/03/1-dead-after-plane-crash-near-boulder-city/ https://www.usnews.com/news/best-states/colorado/articles/2022-07-03/small-plane-crashes-near-boulder-city-airport-pilot-injured https://data.ntsb.gov/Docket?ProjectID=105412 https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=343BH https://flightaware.com/live/flight/N343BH https://globe.adsbexchange.com/?icao=a3c894&lat=35.938&lon=-115.058&zoom=12.0&showTrace=2022-07-03&leg=2 http://www.aircraft.com/aircraft/1433433/n343bh-1997-extra-aircraft-ea-300-slash-l (photos)
Location
Revision history:
Date/time | Contributor | Updates |
03-Jul-2022 19:11 |
Captain Adam |
Added |
03-Jul-2022 19:30 |
RobertMB |
Updated [Time, Total fatalities, Location, Destination airport, Source, Damage, Narrative] |
04-Jul-2022 00:48 |
johnwg |
Updated [Time, Destination airport, Source, Narrative, Category] |
04-Jul-2022 03:32 |
RobertMB |
Updated [Time, Destination airport, Source, Narrative] |
04-Jul-2022 14:15 |
johnwg |
Updated [Time, Destination airport, Narrative] |
04-Jul-2022 19:42 |
RobertMB |
Updated [Destination airport, Narrative] |
05-Jul-2022 01:18 |
johnwg |
Updated [Destination airport, Narrative] |
05-Jul-2022 06:07 |
RobertMB |
Updated [Destination airport, Narrative] |
05-Jul-2022 21:06 |
RobertMB |
Updated [Time, Narrative] |
20-Jul-2022 00:52 |
Captain Adam |
Updated [Time, Location, Phase, Source, Narrative] |
20-Apr-2024 21:37 |
Captain Adam |
Updated [Location, Source, Narrative, Accident report] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation