Accident Raytheon Beechjet 400A N570TM,
ASN logo
 

Date:Sunday 4 February 2018
Time:19:24
Type:Silhouette image of generic BE40 model; specific model in this crash may look slightly different    
Raytheon Beechjet 400A
Owner/operator:Travel Management, Inc
Registration: N570TM
MSN: RK-292
Year of manufacture:2000
Total airframe hrs:9332 hours
Engine model:Williams International FJ44
Fatalities:Fatalities: 0 / Occupants: 4
Aircraft damage: Substantial, written off
Category:Accident
Location:Cleveland-Burke Lakefront Airport, OH (BKL) -   United States of America
Phase: Landing
Nature:Passenger
Departure airport:Teterboro Airport, NJ (TEB/KTEB)
Destination airport:Cleveland-Burke Lakefront Airport, OH (BKL/KBKL)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The two airline-transport pilots and two passengers departed on a cross-country flight in the chartered airplane. Preflight planning had noted the destination airport's runway conditions as "good." As the flight neared the destination airport and the crew conducted the approach checklist, the captain stated, "light snow ... maybe slippery." When the crew checked the airport’s automated terminal information service, the broadcast included "light freezing rain." The flight was transferred to the tower controller, who told the crew that the airport operations crew was on the runway about 20 minutes earlier and advised that it was starting to pick up traces of ice. The captain acknowledged the transmission and, after conducting a missed approach to runway 6L, requested to land on runway 24R. During the approach to runway 24R, the tower controller reported wind at 020° at 25 knots and also at 010° at 25 knots. The crewmembers reported that, after touchdown, they applied maximum braking; however, the airplane did not slow and skidded off the end of the runway into the engineered material arresting system (EMAS), which resulted in substantial damage to the fuselage and a collapsed nose gear. 
The crew stated that the runway grooves had been "smoothed out" by ice accumulations. A first responder reported that the ramp and taxiways were very icy, adding that the end of the runway and EMAS had a sheet of ice. A review of the airport's snow and ice control plan noted that the airport did not have pavement surface sensors and that operations personnel would monitor the airfield as conditions dictated. An airport operations log entry for a runway and field inspection, recorded about 24 minutes before the accident, noted a temperature of 31°F and a braking coefficient of 40 , with runways and taxiways wet. A log entry for a runway and field inspection recorded about 6 minutes after the accident noted a braking coefficient of 30-35, with runways and taxiways wet.
The Runway Condition Assessment Matrix contained in Advisory Circular 150/5200-30D states that a braking coefficient of 40 or higher is the equivalent of a pilot-reported braking action of "good," while a braking coefficient of 30-35 would be medium to poor. The field conditions noted during the pilots’ preflight planning indicated "good" braking conditions; however, the captain's statement of "light snow ... maybe slippery," along with the tower controller's report that the runway was starting to pick up traces of ice, indicated that the crew was aware of the potential for braking conditions that were less than good, which would decrease braking action and increase the stopping distance.
Further, the crew’s selection of runway 24R, which led to the presence of a tailwind, also would decrease braking action.

Probable Cause: The airplane's reduced braking performance due to an ice-covered runway, which resulted in a runway excursion. Contributing to the accident was the crew's selection of a runway with a tailwind.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: final report
Status: Investigation completed
Duration: 1 year and 9 months
Download report: Final report

Sources:


Location

Revision history:

Date/timeContributorUpdates

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org