Zone

Crash of an Embraer EMB-505 Phenom 300 in Houston

Date & Time: Jul 26, 2016 at 1510 LT
Type of aircraft:
Operator:
Registration:
N362FX
Survivors:
Yes
Schedule:
Scottsdale - Houston
MSN:
500-00239
YOM:
2014
Flight number:
LXJ362
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9246
Captain / Total hours on type:
1358.00
Copilot / Total flying hours:
11362
Copilot / Total hours on type:
962
Aircraft flight hours:
1880
Circumstances:
The pilot executed an instrument approach and landing in heavy rain. The airplane touched down about 21 knots above the applicable landing reference speed, which was consistent with an unstabilized approach. The airplane touched down near the displaced runway threshold about 128 kts, and both wing ground spoilers automatically deployed. The pilot reported that the airplane touched down “solidly,” and he started braking promptly, but the airplane did not slow down. The main wheels initially spun up; however, both wheel speeds subsequently decayed consistent with hydroplaning in the heavy rain conditions. When the wheel speeds did not recover, the brake control unit advised the flight crew of an anti-skid failure; the pilot recalled an anti-skid CAS message displayed at some point during the landing. The pilot subsequently activated the emergency brake system and the wheel speeds decayed. The airplane ultimately overran the departure end of the runway about 60 kts, crossed an airport perimeter road, and encountered a small creek before coming to rest. The wings had separated from, and were located immediately adjacent to, the fuselage. The pilot reported light to moderate rain began on final approach. Weather data and surveillance images indicated that heavy rain and limited visibility prevailed at the airport during the landing. Thunderstorms were active in the vicinity and the rainfall rate at the time of the accident landing was between 4.2 and 6.0 inches per hour. About 4 minutes before the accident, a surface observation recorded the visibility as 3 miles. However, 3 minutes later, the observed visibility had decreased to 3/8 mile. A review of the available information indicated that the tower controller advised the pilot of changing wind conditions and of better weather west of the airport but did not update the pilot regarding visibility along the final approach course or precipitation at the airport. The pilot stated that the rain started 2 to 3 minutes before he landed and commented that it was not the heaviest rain that he had ever landed in. The pilot was using the multifunction display and a tablet for weather radar, which showed green and yellow returns indicating light to moderate rain during the approach. He chose not to turn on the airplane’s onboard weather radar because the other two sources were not indicating severe weather. The runway exhibited skid marks beginning about 1,500 ft from the departure end and each main tire had one patch of reverted rubber wear consistent with reverted rubber hydroplaning. The main landing gear remained extended and both tires remained pressurized. The tire pressures corresponded to a minimum dynamic hydroplaning speed of about 115 kts. The airplane flight manual noted that, in the case of an antiskid failure, the main brakes are to be applied progressively and brake pressure is to be modulated as required. The emergency brake is to be used in the event of a brake failure; however, the pilot activated the emergency brake when the main brakes still functioned; although, without anti-skid protection.
Probable cause:
The airplane’s hydroplaning during the landing roll, which resulted in a runway excursion. Contributing to the accident was the pilot’s continuation of an unstabilized approach, his decision to land in heavy rain conditions, and his improper use of the main and emergency brake systems. Also contributing was the air traffic controller’s failure to disseminate current airport weather conditions to the flight crew in a timely manner.
Final Report:

Crash of an Embraer EMB-500 Phenom 100 in Houston

Date & Time: Nov 21, 2014 at 1010 LT
Type of aircraft:
Operator:
Registration:
N584JS
Flight Type:
Survivors:
Yes
Schedule:
Houston - Houston
MSN:
500-00140
YOM:
2010
Flight number:
RSP526
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6311
Captain / Total hours on type:
410.00
Copilot / Total flying hours:
4232
Copilot / Total hours on type:
814
Aircraft flight hours:
3854
Circumstances:
The pilots of the very light jet were conducting a positioning flight in instrument meteorological conditions. The flight was cleared by air traffic control for the instrument landing system (ILS) approach; upon being cleared for landing, the tower controller reported to the crew that there was no standing water on the runway. Review of the airplane's flight data recorder (FDR) data revealed that the airplane reached 50 ft above touchdown zone elevation (TDZE) at an indicated airspeed of 118 knots (KIAS). The airplane crossed the runway displaced threshold about 112 KIAS, and it touched down on the runway at 104 KIAS with about a 7-knot tailwind. FDR data revealed that, about 1.6 seconds after touchdown of the main landing gear, the nose landing gear touched down and the pilot's brake pedal input increased, with intermediate oscillations, over a period of 7.5 seconds before reaching full pedal deflection. During this time, the airplane achieved its maximum wheel braking friction coefficient and deceleration. The cockpit voice recorder recorded both pilots express concern the that the airplane was not slowing. About 4 seconds after the airplane reached maximum deceleration, the pilot applied the emergency parking brake (EPB). Upon application of the EPB, the wheel speed dropped to zero and the airplane began to skid, which resulted in reverted-rubber hydroplaning, further decreasing the airplane's stopping performance. The airplane continued past the end of the runway, crossed a service road, and came to rest in a drainage ditch. Postaccident examination of the brake system and data downloaded from the brake control unit indicated that it functioned as commanded during the landing. The airplane was not equipped with thrust reversers or spoilers to aid in deceleration. The operator's standard operating procedures required pilots to conduct a go-around if the airspeed at 50 ft above TDZE exceeded 111 kts. Further, the landing distances published in the airplane flight manual (AFM) are based on the airplane slowing to its reference speed (Vref) of 101 KIAS at 50 ft over the runway threshold. The airplane's speed at that time exceeded Vref, which resulted in an increased runway distance required to stop; however, landing distance calculations performed in accordance with the AFM showed that the airplane should still have been able to stop on the available runway. An airplane performance study also showed that the airplane had adequate distance available on which to stop had the pilot continued to apply maximum braking rather than engage the EPB. The application of the EPB resulted in skidding, which increased the stopping distance. Although the runway was not contaminated with standing water at the time of the accident, the performance study revealed that the maximum wheel braking friction coefficient was significantly less than the values derived from the unfactored wet runway landing distances published in the AFM, and was more consistent with the AFM-provided landing distances for runways contaminated with standing water. Federal Aviation Administration Safety Alert for Operators (SAFO) 15009 warns operators that, "the advisory data for wet runway landings may not provide a safe stopping margin under all conditions" and advised them to assume "a braking action of medium or fair when computing time-of-arrival landing performance or [increase] the factor applied to the wet runway time-of-arrival landing performance data." It is likely that, based on the landing data in the AFM, the crew expected a faster rate of deceleration upon application of maximum braking; when that rate of deceleration was not achieved, the pilot chose to engage the EPB, which only further degraded the airplane's braking performance.
Probable cause:
The pilot's engagement of the emergency parking brake during the landing roll, which decreased the airplane's braking performance and prevented it from stopping on the available runway. Contributing to the pilot's decision to engage the emergency parking brake was the expectation of a faster rate of deceleration and considerably shorter wet runway landing distance provided by the airplane flight manual than that experienced by the crew upon touchdown and an actual wet runway friction level lower than the assumed runway fiction level used in the calculation of the stopping distances published in the airplane flight manual.
Final Report:

Crash of a Cessna 525 CitationJet CJ1 near Buda: 1 killed

Date & Time: Mar 26, 2000 at 0840 LT
Type of aircraft:
Registration:
N130MR
Flight Type:
Survivors:
No
Schedule:
Houston - Rutherford Ranch
MSN:
525-0097
YOM:
1995
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5887
Captain / Total hours on type:
154.00
Aircraft flight hours:
720
Circumstances:
The flight was approaching a private airport (elevation 983 feet msl), that did not have an instrument approach system, during instrument meteorological conditions. The pilot informed the air traffic controller that he had the airport in sight, and cancelled his instrument flight plan. The twin turbofan airplane impacted a tree approximately 4,000 feet northeast of the airport in an upright position. The airplane then impacted the ground in an inverted position approximately 200 yards from the initial impact with the tree. The weather observation facility located 16 miles northeast of the accident site was reporting an overcast ceiling at 400 feet agl, and visibility 4 statute miles in mist. The weather observation facility elevation was 541 feet msl. Local residents in the vicinity of the accident site stated that there was heavy fog and drizzle at the time of the accident. The pilot had filed an alternate airport (with a precision instrument approach); however, he elected not to divert to the alternate airport. Examination of the wreckage did not reveal any evidence of pre-impact anomalies that would have prevented operation of the airplane.
Probable cause:
The pilot's inadequate in-flight decision to continue a visual approach in instrument meteorological conditions which resulted in his failure to maintain terrain clearance. Contributing factors were the fog, drizzle, and low ceilings.
Final Report:

Crash of a Cessna T303 Crusader in San Diego

Date & Time: May 7, 1999 at 2230 LT
Type of aircraft:
Registration:
N3303S
Flight Type:
Survivors:
Yes
Schedule:
Houston – San Diego
MSN:
303-00018
YOM:
1981
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
25000
Captain / Total hours on type:
200.00
Aircraft flight hours:
1832
Circumstances:
The airplane departed Houston, Texas, for a VFR flight to San Diego, California. The pilot in the left seat said that they originally planned to purchase fuel at Gila Bend, Arizona, but were told that the fueling was closed. The left seat pilot said they elected to land at a private airstrip and made arrangements to have an individual drive to Casa Grande airport to purchase fuel for them. The left seat pilot said they were worried about adequate runway length, so they elected to only purchase 65 gallons of fuel for the remainder of the flight to San Diego. En route to San Diego, the right seat pilot obtained weather for the destination from FSS and was advised of 1,000-foot overcast ceiling. The right seat pilot then requested and received an instrument clearance. The TRACON controller advised the pilot of the accident airplane that he would have to keep speed up due to jet traffic or be given delay vectors for traffic spacing. The pilot told ATC that they were fuel critical and later said they had about 45 minutes to 1 hour of fuel. The right seat pilot was cleared for the localizer runway 27 approach. Approximately 18 minutes later, the pilot elected to do a missed approach because he was too high to land and moments later told San Diego radar that he was fuel critical and only had about 5 minutes of fuel left. San Diego radar began to give the pilot vectors to the closest airport and told the pilot not to descend any further. The right seat pilot replied that they were a glider and later told San Diego police that they had run out of fuel. There were no discrepancies noted with either the airframe or the engines during the postaccident aircraft examination.
Probable cause:
The pilot-in-command's inaccurate fuel consumption calculations that resulted in fuel exhaustion and the subsequent ditching.
Final Report:

Crash of a Mitsubishi MU-300-10 Diamond II in Houston

Date & Time: Mar 12, 1997
Type of aircraft:
Operator:
Registration:
N411BW
Flight Type:
Survivors:
Yes
MSN:
1008
YOM:
1985
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing on wet runway 35 at Houston-Sugar Land Airport, the crew encountered nil braking action. Unable to stop within the remaining distance, the aircraft overran and came to rest in a ditch. Both occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
No investigations were conducted by the NTSB. The pilot reported this incident was caused by tire hydroplaning and loss of brake effectiveness due to wet runway conditions.