Crash of a Cessna T303 Crusader in Louisa: 1 killed

Date & Time: Mar 4, 2010 at 1245 LT
Type of aircraft:
Registration:
N9305T
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Manassas - Louisa - Danville
MSN:
303-00001
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2255
Aircraft flight hours:
1374
Circumstances:
During takeoff, one witness noted that at least one engine seemed to be running rough and not making power. Several other witnesses, located about 1/2 mile northwest of the airport, observed the accident airplane pass overhead in a right turn. They reported that the engine noise did not sound normal. Two of the witnesses noted grayish black smoke emanating from the airplane. The airplane then rolled left and descended nose down into the front yard of a residence. Review of maintenance records revealed the airplane underwent an annual inspection and extensive maintenance about 3 months prior to the accident. One of the maintenance issues was to troubleshoot the right engine that was reportedly running rough at cruise. During the maintenance, the right engine fuel pump, metering valve, and fuel manifold were removed and replaced with overhauled units. Additionally, the right engine fuel flow was reset contrary to procedures contained in an engine manufacturer service information directive; however, the fuel pump could not be tested due to thermal damage and the investigation could not determine if the fuel flow setting procedure contributed to the loss of power on the right engine. On-scene examination of the wreckage and teardown examination of both engines did not reveal any preimpact mechanical malfunctions. Teardown examination of the right propeller revealed that the blades were not at or near the feather position, which was contrary to the emergency procedure published by the manufacturer, to secure the engine and feather the propeller in the event of an engine power loss. The right propeller exhibited signatures consistent with low or no power at impact, while the left propeller exhibited signatures consistent of being operated with power at impact.
Probable cause:
The pilot's failure to maintain aircraft control and secure the right engine during a loss of engine power after takeoff. Contributing to the accident was the loss of engine power on the right engine for undetermined reasons.
Final Report:

Crash of a Pilatus PC-12/45 in Raphine: 4 killed

Date & Time: Jul 5, 2009 at 1002 LT
Type of aircraft:
Registration:
N578DC
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Teterboro - Tampa
MSN:
570
YOM:
2004
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
1873
Captain / Total hours on type:
715.00
Aircraft flight hours:
723
Circumstances:
While in instrument meteorological conditions flying 800 feet above the airplane’s service ceiling (30,000 feet), with no icing conditions reported, the pilot reported to the air traffic controller that he, “...lost [his] panel.” With the autopilot most likely engaged, the airplane began a right roll about 36 seconds later. The airplane continued in a right roll that increased to 105 degrees, then rolled back to about 70 degrees, before the airplane entered a right descending turn. The airplane continued its descending turn until being lost from radar in the vicinity of the accident site. The airplane impacted in a nose-down attitude in an open field and was significantly fragmented. Postaccident inspection of the flight control system, engine, and propeller revealed no evidence of preimpact failure or malfunction. The flaps and landing gear were retracted and all trim settings were within the normal operating range. Additionally, the airplane was within weight and balance limitations for the flight. The cause of the pilot-reported panel failure could not be determined; however, the possibility of a total electrical failure was eliminated since the pilot maintained radio contact with the air traffic controller. Although the source of the instrumentation failure could not be determined, proper pilot corrective actions, identified in the pilot operating handbook, following the failure most likely would have restored flight information to the pilot’s electronic flight display. Additionally, a standby attitude gyro, compass, and the co-pilot’s electronic flight display units would be available for attitude reference information assuming they were operational.
Probable cause:
The pilot's failure to maintain control of the airplane while in instrument meteorological conditions following a reported instrumentation failure for undetermined reasons.
Final Report:

Crash of a Grumman E-2C Hawkeye at Chambers Field NAS

Date & Time: Mar 19, 2009
Type of aircraft:
Operator:
Registration:
165818
Flight Type:
Survivors:
Yes
MSN:
A189
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After touchdown at Norfolk-Chambers Field NAS, a tyre burst. The crew lost control of the airplane that veered off runway and collided with an arrestor gear engine. There were no casualties.
Probable cause:
Loss of control upon landing after a tyre burst.

Crash of a Dornier DO328Jet in Manassas

Date & Time: Jun 3, 2006 at 0719 LT
Type of aircraft:
Operator:
Registration:
N328PD
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Manassas - Myrtle Beach
MSN:
3105
YOM:
2000
Crew on board:
3
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
15615
Captain / Total hours on type:
2523.00
Copilot / Total flying hours:
819
Copilot / Total hours on type:
141
Aircraft flight hours:
2830
Circumstances:
Prior to departure on the maintenance repositioning flight, the captain discussed with the first officer an uneven fuel balance that they could "fix" once airborne, and a 25,000 feet msl restriction because of an inoperative air conditioning/pressurization pack. The captain also commented about the right pack "misbehaving", and a bleed valve failure warning. The captain also commented about aborting below 80 knots for everything, except for the bleed shutoff valve. During the takeoff roll, a single chime was heard, and the first officer reported a bleed valve fail message. The captain responded, "ignore it." Another chime was heard, and the first officer reported "lateral mode fail, pusher fail." The captain asked about airspeed and was advised of an "indicated airspeed miscompare." The captain initiated the aborted takeoff approximately 13 seconds after the second chime was heard. The crew was unable to stop the airplane, and it went off the end of the runway, and impacted obstructions and terrain. According to the flight data recorder, peak groundspeed was 152 knots and the time the aborted takeoff was initiated, and indicated airspeed was 78.5 knots. The captain and the airplane owner's director of maintenance were aware of several mechanical discrepancies prior to the flight, and the captain had advised the first officer that the flight was for "routine maintenance," but that the airplane was airworthy. Prior to the flight the first officer found "reddish clay" in one of the pitot tubes and removed it. A mechanic and the captain examined the pitot tube, and determined the tube was not obstructed. The captain's pitot tube was later found to be partially blocked with an insect nest. A postaccident examination of the airplane and aircraft maintenance log revealed that no discrepancies were entered in the log, and no placards or "inoperative" decals were affixed in the cockpit.
Probable cause:
The partially blocked pitot system, which resulted in an inaccurate airspeed indicator display, and an overrun during an aborted takeoff. A factor associated with the accident was the pilot-in-command's delayed decision to abort the takeoff.
Final Report:

Crash of a Saab 340A in Washington DC

Date & Time: Jun 8, 2005 at 2137 LT
Type of aircraft:
Operator:
Registration:
N40SZ
Survivors:
Yes
Schedule:
White Plains – Washington DC
MSN:
40
YOM:
1985
Flight number:
UA7564
Crew on board:
3
Crew fatalities:
Pax on board:
27
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4673
Captain / Total hours on type:
3476.00
Copilot / Total flying hours:
2050
Copilot / Total hours on type:
620
Aircraft flight hours:
41441
Circumstances:
During the approach, the flightcrew was unable to get the right main landing gear extended and locked. After several attempts, while conferring with the checklist and company personnel, the flightcrew performed an emergency landing with the unsafe landing gear indication. During the landing, the right main landing gear slowly collapsed, and the airplane came to rest off the right side of the runway. Examination of the right main landing gear revealed that the retract actuator fitting was secured with two fasteners, a smaller bolt, and a larger bolt. The nut and cotter key were not recovered with the smaller bolt, and 8 of the 12 threads on the smaller bolt were stripped consistent with an overstress pulling of the nut away from the bolt. The larger bolt was bent and separated near the head, consistent with a tension and overstress separation as a result of the smaller bolt failure. The overstress failures were consistent with the right main landing gear not being locked in the extended position when aircraft weight was applied; however, examination of the right main landing gear down lock system could not determine any pre-impact mechanical malfunctions. Further, the right main landing gear retract actuator was tomography scanned, and no anomalies were noted. The unit was then functionally tested at the manufacturer's facility, under the supervision of an FAA inspector. The unit tested successfully, with no anomalies noted.
Probable cause:
Failure of the right main landing gear to extend and lock for undetermined reasons, which resulted in the right main landing gear collapsing during touchdown.
Final Report:

Crash of a Cessna 414 Chancellor in Petersburg

Date & Time: Dec 2, 2004 at 1310 LT
Type of aircraft:
Registration:
N2EQ
Flight Type:
Survivors:
Yes
Schedule:
Petersburg - Petersburg
MSN:
414-0373
YOM:
1972
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3000
Captain / Total hours on type:
130.00
Copilot / Total flying hours:
5600
Circumstances:
The purpose of the flight was to "check out" the airplane before delivering it to its new owner, and to provide the copilot with an indoctrination ride in the Cessna 414. During the approach, the pilot provided guidance and corrections to the copilot. The copilot flew the airplane to within 200 feet of the ground when the nose of the airplane yawed abruptly to the right. The pilot took control of the airplane, and pushed the engine and propeller controls to the full forward position. He placed the fuel pump switches to the "high" position, retracted the flaps, and attempted to retract the landing gear. With full left rudder and full left aileron applied, he could neither maintain directional control nor stop a roll to the right. The airplane struck the ground and continued into the parking area where it struck an airplane and a waste-oil tank. Examination of the airplane following the accident revealed that the landing gear was down and locked, and the propeller on the right engine was not feathered. The emergency procedure for an engine inoperative go-around required landing gear retraction and a feathered propeller on the inoperative engine. The pilot's handbook further stated, "Climb or continued level flight is improbable with the landing gear extended and the propeller windmilling." After the accident, both pilots stated that they didn't notice a power loss on the right engine until the copilot surrendered the flight controls. The right engine was removed and placed in a test cell. The engine started immediately on the first attempt and ran continuously without interruption.
Probable cause:
The partial loss of engine power for undetermined reasons, and the pilot's failure to maintain adequate airspeed (Vmc).
Final Report:

Crash of a Beechcraft 200 Super King Air on Mt Bull: 10 killed

Date & Time: Oct 24, 2004 at 1235 LT
Operator:
Registration:
N501RH
Survivors:
No
Site:
Schedule:
Concord – Martinsville
MSN:
BB-805
YOM:
1981
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
10
Captain / Total flying hours:
10733
Captain / Total hours on type:
210.00
Copilot / Total flying hours:
2090
Copilot / Total hours on type:
121
Aircraft flight hours:
8078
Circumstances:
On October 24, 2004, about 1235 eastern daylight time (all times in this brief are eastern daylight time based on a 24-hour clock), a Beech King Air 200, N501RH, operated by Hendrick Motorsports, Inc., crashed into mountainous terrain in Stuart, Virginia, during a missed approach to Martinsville/Blue Ridge Airport (MTV), Martinsville, Virginia. The flight was transporting Hendrick Motorsports employees and others to an automobile race in Martinsville, Virginia. The two flight crewmembers and eight passengers were killed, and the airplane was destroyed by impact forces and post crash fire. The flight was operating under the provisions of 14 Code of Federal Regulations (CFR) Part 91 on an instrument flight rules (IFR) flight plan. Instrument meteorological conditions (IMC) prevailed at the time of the accident.
Probable cause:
The flight crew's failure to properly execute the published instrument approach procedure, including the published missed approach procedure, which resulted in controlled flight into terrain. Contributing to the cause of the accident was the flight crew's failure to use all available navigational aids to confirm and monitor the airplane's position during the approach.
Final Report:

Crash of a Socata TBM-700 in Leesburg: 3 killed

Date & Time: Mar 1, 2003 at 1445 LT
Type of aircraft:
Registration:
N700PP
Survivors:
No
Schedule:
Greenville - Leesburg
MSN:
059
YOM:
1992
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
730
Copilot / Total flying hours:
8375
Aircraft flight hours:
1049
Circumstances:
The private pilot, who sat in the left seat, was executing the LOC RWY 17 instrument approach in actual instrument meteorological conditions, when the airplane decelerated, lost altitude, and began a left turn about 2 miles from the airport. Subsequently, the airplane collided with terrain and came to rest on residential property. The radar data also indicated that the airplane was never stabilized on the approach. A witness, a private pilot, said the airplane "appeared" out of the fog about 300-400 feet above the ground. It was in a left bank, with the nose pointed down, and was traveling fast. The airplane then "simultaneously and suddenly level[ed] out," pitched up, and the engine power increased. The witness thought that the pilot realized he was low and was trying to "get out of there." The airplane descended in a nose-high attitude, about 65 degrees, toward the trees. Radar data indicates that the airplane slowed to 80 knots about 3 miles from the airplane, and then to 68 knots 18 seconds later as the airplane began to turn to the left. Examination of the airplane and engine revealed no mechanical deficiencies. Weather reported at the airport 25 minutes before the accident included wind from 140 degrees at 5 knots, visibility 1 statute mile, and ceiling 500 foot overcast. Weather 5 minutes before the accident included wind from 140 degrees at 5 knots, visibility 1 statute miles, and ceiling 300 foot overcast.
Probable cause:
The pilot's failure to fly a stabilized, published instrument approach procedure, and his failure to maintain adequate airspeed which led to an aerodynamic stall.
Final Report:

Crash of a BAe 4101 Jetstream 41 in Charlottesville

Date & Time: Dec 29, 2000 at 2234 LT
Type of aircraft:
Operator:
Registration:
N323UE
Survivors:
Yes
Schedule:
Washington DC – Charlottesville
MSN:
41059
YOM:
1995
Flight number:
UA331
Crew on board:
3
Crew fatalities:
Pax on board:
15
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4050
Captain / Total hours on type:
1425.00
Copilot / Total flying hours:
4818
Copilot / Total hours on type:
68
Aircraft flight hours:
14456
Circumstances:
The twin-engine turboprop airplane touched down about 1,900 feet beyond the approach end of the 6,000-foot runway. During the rollout, the pilot reduced power by pulling the power levers aft, to the flight idle stop. He then depressed the latch levers, and pulled the power levers further aft, beyond the flight idle stop, through the beta range, into the reverse range. During the power reduction, the pilot noticed, and responded to a red beta light indication. Guidance from both the manufacturer and the operator prohibited the use of reverse thrust on the ground with a red beta light illuminated. The pilot pushed the power levers forward of the reverse range, and inadvertently continued through the beta range, where aerodynamic braking was optimum. The power levers continued beyond the flight idle gate into flight idle, a positive thrust setting. The airplane continued to the departure end of the runway in a skid, and departed the runway and taxiway in a skidding turn. The airplane dropped over a 60-foot embankment, and came to rest at the bottom. The computed landing distance for the airplane over a 50-foot obstacle was 3,900 feet, with braking and ground idle (beta) only; no reverse thrust applied. Ground-taxi testing after the accident revealed that the airplane could reach ground speeds upwards of 85 knots with the power levers at idle, and the condition levers in the flight position. Simulator testing, based on FDR data, consistently resulted in runway overruns. Examination of the airplane and component testing revealed no mechanical anomalies. Review of the beta light indicating system revealed that illumination of the red beta light on the ground was not an emergency situation, but only indicated a switch malfunction. In addition, a loss of the reverse capability would have had little effect on computed stopping distance, and none at all in the United States, where performance credit for reverse thrust was not permitted.
Probable cause:
The captain's improper application of power after responding to a beta warning light during landing rollout, which resulted in an excessive rollout speed and an inability to stop the airplane before it reached the end of the runway.
Final Report:

Crash of a Beechcraft F90 King Air in Lynchburg

Date & Time: Nov 24, 2000 at 1151 LT
Type of aircraft:
Registration:
N94U
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Lynchburg - Lynchburg
MSN:
LA-124
YOM:
1981
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12000
Captain / Total hours on type:
250.00
Aircraft flight hours:
6788
Circumstances:
The pilot was conducting a post-maintenance test flight. An overhauled engine had been installed on the right side of the airplane, and both propeller assemblies had been subsequently re-rigged. Ground checks were satisfactory, although the right engine propeller idled 90-100 rpm higher than the left engine propeller. Test flight engine start and run-up were conducted per the checklist, with no anomalies noted. Takeoff ground roll and initial climb were normal; however, when the airplane reached about 100 feet, it stopped climbing and lost airspeed. The pilot could not identify the malfunction, and performed a forced landing to rough, hilly terrain. Upon landing, the landing gear collapsed and the engine nacelles were compromised. The airplane subsequently burned. Post-accident examination of the airplane revealed that the propeller beta valves of both engines were improperly rigged, and that activation of the landing gear squat switch at takeoff resulted in both propellers going into feather. The maintenance personnel did not have rigging experience in airplane make and model. As a result of the investigation, the manufacturer clarified maintenance manual and pilot handbook procedures.
Probable cause:
Improper rigging of both propeller assemblies by maintenance personnel, which resulted in the inadvertent feathering of both propellers after takeoff. Factors included a lack of rigging experience in airplane make and model by maintenance personnel, unclear maintenance manual information, and unsuitable terrain for the forced landing.
Final Report: