The U.S. aircraft register, updated daily
Accidents · NTSB CEN18LA094 · Final report

Raytheon Aircraft Company 400A accident near Cleveland, Ohio, February 5, 2018

On February 5, 2018, a 2000 Raytheon Aircraft Company 400A, registered N570TM, was substantially damaged in an accident during landing (landing roll) near Cleveland, Ohio (Burke Lakefront airport). It was flown under charter and air-taxi rules (Part 135). No one was hurt; 4 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
February 5, 2018
Place
Cleveland, Ohio · Burke Lakefront · map
Type
Accident
Injuries
No one was hurt; 4 people were on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Raytheon Aircraft Company 400A NO SERIES, built 2000
Registration
N570TM · no longer on the register · serial RK-292
Damage
Substantial damage
Flight
Flight · charter and air-taxi rules (Part 135)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Runway excursion during landing (landing roll) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)

The NTSB's findings

  • cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Freezing rain/sleet › Effect on operation
  • cause Environmental issues › Operating environment › Airport facilities/design › Runway/landing area condition › Effect on operation
  • factor Personnel issues › Action/decision › Action › Incorrect action selection › Pilot
  • factor Environmental issues › Conditions/weather/phenomena › Wind › Tailwind › Not specified

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 12,487 hours in all; 1,762 in this make and model; 100 in the last 90 days; 4,342 as pilot in command
  • Last flight review: November 11, 2017
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 2,509 hours in all; 156 in this make and model; 156 in the last 90 days
  • Last flight review: November 14, 2017
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 9,332.1 hours
  • Last inspection: approved inspection programme, January 27, 2018
  • Landing gear: retractable
  • Engine 1: Williams FJ 44 SERIES (turbofan); 0 hours total
  • Engine 2: Williams FJ 44 Series (turbofan); 0 hours total
  • Operator: Travel Management, Inc

The flight

  • Departed from: KTEB Teterboro NJ at 11:04 pm
  • Destination: KBKL Cleveland OH
  • Flight plan: IFR
  • Runway 24R, 6,604 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: dusk
  • Wind: from 010° at 22 knots, gusting 30
  • Visibility: 4 statute miles
  • Sky: overcast at 700 ft
  • Temperature: 28°F (-2°C), dew point 25°F (-4°C)
  • Altimeter: 29.79 inHg

Injuries

FatalSeriousMinorNone
Flight crew2
Passengers2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

9 documents, released by the NTSB on June 24, 2019. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.