Crash of a Beechcraft Beechjet 400A in Macon

Date & Time: Sep 18, 2012 at 1003 LT
Type of aircraft:
Operator:
Registration:
N428JD
Survivors:
Yes
Schedule:
Charleston - Macon
MSN:
RJ-13
YOM:
1986
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7000
Captain / Total hours on type:
4000.00
Copilot / Total flying hours:
2500
Copilot / Total hours on type:
450
Aircraft flight hours:
5416
Circumstances:
The aircraft was substantially damaged when it overran runway 28 during landing at Macon Downtown Airport (MAC), Macon, Georgia. The airplane departed from Charleston Air Force Base/International Airport (CHS), Charleston, South Carolina, about 0930. Visual meteorological conditions prevailed and an instrument flight rules (IFR) flight plan was filed. Both Airline Transport Pilots (ATP) and one passenger sustained minor injuries. The airplane was owned by Dewberry, LLC and operated by The Aviation Department. The corporate flight was conducted under the provisions of Title 14 Code of Federal Regulations (CFR) Part 91. According to an interview with the pilots, they arrived at DeKalb-Peachtree Airport (PDK), Atlanta, Georgia, which was their home base airport, about 0400, and then drove about 4 1/2 hours to CHS for the 0930 flight. The flight departed on time, the airspeed index bug was set on the co-pilot's airspeed for a decision takeoff speed (V1) of about 102 knots and a single engine climb speed (V2) on the pilot's side of 115 knots. The flight climbed to 16,000 feet prior to beginning the descent into MAC. When the flight was about 11 miles from the airport the flight crew visually acquired the airport and cancelled their IFR clearance with the Macon Radar Approach controller and proceeded to the airport visually. The second-in-command activated the runway lights utilizing the common traffic advisory frequency for the airport. Both crew members reported that about 3 seconds following activation of the lights and the precision approach path indicator (PAPI) lights, the PAPI lights turned off and would not reactivate. During the approach, the calculated reference speed (Vref) was 108 knots and was set on both pilots' airspeed indicator utilizing the index bug that moved around the outside face of the airspeed instrument. The landing was within the first 1,000 feet of the runway and during the landing roll out the airplane began to "hydroplane" since there was visible standing water on the runway and the water was "funneling into the middle." Maximum reverse thrust, braking, and ground spoilers were deployed; however, both pilots reported a "pulsation" in the brake system. The airplane departed the end of the runway into the grass, went down an embankment, across a road, and into trees. They further added that the airplane "hit hard" at the bottom of the embankment. They also reported that there were no mechanical malfunctions with the airplane prior to the landing. According to an eyewitness statement, a few minutes prior to the airplane landing, the airport experienced a rain shower with a "heavy downpour." The witness reported observing the airplane on approach, heard the engine thrust reverse, and then observed the airplane "engulfed in a large ball of water vapor." However, he did not observe the airplane as it departed the end of the runway. Another witness was located in a hangar on the west side of the airport and heard the airplane, looked outside and then saw the airplane with the reverse thrusters deployed. He watched it depart the end of the runway and travel into the nearby woods.
Probable cause:
The pilot’s failure to maintain proper airspeed, which resulted in the airplane touching down too fast on the wet runway with inadequate runway remaining to stop and a subsequent runway overrun. Contributing to the landing overrun were the flight crew members’ failure to correctly use the appropriate performance chart to calculate the runway required to stop on a contaminated runway and their general lack of proper crew resource management.
Final Report:

Crash of a Beechcraft Beechjet 400A in Atlanta

Date & Time: Jun 18, 2012 at 1006 LT
Type of aircraft:
Operator:
Registration:
N826JH
Survivors:
Yes
Schedule:
Gadsden - Atlanta
MSN:
RK-70
YOM:
1993
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
10800
Captain / Total hours on type:
1500.00
Copilot / Total flying hours:
3500
Copilot / Total hours on type:
150
Aircraft flight hours:
4674
Circumstances:
The second-in-command (SIC) was the pilot flying for most of the flight (takeoff, climb, cruise, and descent) and was in the left seat, while the pilot-in-command (PIC) was the pilot monitoring for most of the flight and was in the right seat. Before takeoff, the PIC calculated reference speed (Vref) for the estimated landing weight and flaps 30-degree extension was 120 knots, with a calculated landing distance of 3,440 ft. Further, before takeoff, there were no known mechanical difficulties with the brakes, flaps, antiskid, or traffic alert and collision avoidance (TCAS) systems. After takeoff and for most of the flight, the PIC coached/instructed the SIC, including instructions on how to set the airspeed command cursor, a request to perform the after-takeoff checklist, and a comment to reduce thrust to silence an overspeed warning aural annunciation. When the flight was northwest of Dekalb Peachtree Airport (PDK), Atlanta, Georgia, on a right base leg for a visual approach to runway 20L with negligible wind, air traffic controllers repeatedly announced the location and distance of a Cessna airplane (which was ahead of the Beech 400A on a straight-in visual approach to runway 20R). Because the Beech 400A flight crew did not see the other airplane, the controllers appropriately instructed them to maintain their altitude (which was 2,300 ft mean sea level [msl]) for separation until they had the traffic in sight; radar data indicated the Beech 400A briefly descended to 2,200 ft msl then climbed back to 2,300 ft msl. According to the cockpit voice recorder (CVR) transcript, at 1004:42, which was about 12 seconds after the controller instructed the Beech 400A flight crew to maintain altitude, the on board TCAS alerted "traffic traffic." While the Beech 400A did climb back to 2,300 ft msl, this was likely a response to the air traffic control (ATC) instruction to maintain altitude and not a response to the TCAS "traffic traffic" warning. At 1004:47, the CVR recorded the SIC state, "first degree of," likely referring to flap extension, but the comment was not completed. The CVR recorded an immediate increase in background noise, which was likely due to the landing gear extension. The PIC then advised the local controller that the flight was turning onto final approach. The CVR did not record any approach briefing or discussion of runway length or Vref speed. After landing on runway 20L at Atlanta-DeKalb Peachtree Airport, aircraft did not stop as expected. It overrun the runway, went through a fence and came to rest near a road, broken in two. All four occupants were injured, both pilots seriously.
Probable cause:
The flight crew's failure to obtain the proper airspeed for landing, which resulted in the airplane touching down too fast with inadequate runway remaining to stop and a subsequent
runway overrun. Contributing to the accident were the failure of either pilot to call for a go-around and the flight crew's poor crew resource management and lack of professionalism.
Final Report:

Crash of a Beechcraft BeechJet 400A in São José dos Campos

Date & Time: Jul 15, 2008 at 1130 LT
Type of aircraft:
Operator:
Registration:
PT-WHF
Flight Type:
Survivors:
Yes
Schedule:
São Paulo - São José dos Campos
MSN:
RK-82
YOM:
1994
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4300
Captain / Total hours on type:
2811.00
Copilot / Total flying hours:
540
Copilot / Total hours on type:
35
Circumstances:
The crew departed São Paulo-Congonhas Airport on a positioning flight to São José dos Campos. While descending to São José dos Campos, the captain led the controls to the copilot who was still under instruction. On final, the aircraft was too high on the glide. The captain took over controls but his reaction was excessive. The aircraft suddenly rolled to the right, causing the right wing to struck the ground few dozen metres short of runway 15 threshold. The aircraft landed and came to rest on the main runway. Both pilots evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
The captain did not conduct a preflight briefing and then improvised during the descent by deciding to leave the controls to the copilot while he was still under instruction.
The following contributing factors were identified:
- The copilot who was pilot-in-command on final was in his initial training process,
- The captain authorized the copilot to be the PIC while he was still under initial training,
- The captain was not qualified to operate as an instructor,
- The captain did not make any simulator training for more than two years,
- The copilot had never completed any simulator training since the beginning of his training,
- Lack of crew coordination,
- Poor judgment on part of the captain.
Final Report: