OpenAirDocs.org

20060402011139I

Incident · Minor damage
Open the Markdown

FAA incident report · Semco Challenger · Richmond, VA · April 2, 2006

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
April 2, 2006 · 17:17 local
Place
Richmond, VA
Airport
Chesterfield County Airport
Phase of flight
Fcd/Prec Ldg From Cruise
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
NONE
Reported as
Semco Challenger
People aboard
1
Fatal injuries
0
Pilot’s flight hours
2,000 total200 in this make and model10 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

(-23) The aircraft was at low altitude when it hit some turbulence. This caused the pilot's hat to blow off and strike the propeller behind the pilot. One of the propeller blades broke off in flight as a result of striking the hat. The aircraft then began to lose altitude. In an attempt to make an emergency landing in a field the aircraft lost too much altitude and landed upright in bushes. This aircraft was not registered at the time of this incident. This aircraft does not meet the requirements of FAR part 103.

As the FAA filed it

(-23) THE AIRCRAFT WAS AT LOW ALTITUDE WHEN IT HIT SOME TURBULENCE. THIS CAUSED THE PILOT'S HAT TO BLOW OFF AND STRIKE THE PROPELLER BEHIND THE PILOT. ONE OF THE PROPELLER BLADES BROKE OFF IN FLIGHT AS A RESULT OF STRIKING THE HAT. THE AIRCRAFT THEN BEGAN TO LOSE ALTITUDE. IN AN ATTEMPT TO MAKE AN EMERGENCY LANDING IN A FIELD THE AIRCRAFT LOST TOO MUCH ALTITUDE AND LANDED UPRIGHT IN BUSHES. THIS AIRCRAFT WAS NOT REGISTERED AT THE TIME OF THIS INCIDENT. THIS AIRCRAFT DOES NOT MEET THE REQUIREMENTS OF FAR PART 103.