FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Travel Management Raytheon Aircraft Company 400A accident

4 Feb 2018 · Cleveland, OH, United States

Raytheon Aircraft Company 400A · Accident: runway excursion during landing

From Teterboro Airport (KTEB) to Burke Lakefront Airport (KBKL)

Report a problem

Event

NTSB case
CEN18LA094
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Charter & commuter
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Raytheon Aircraft Company 400A

Aircraft type
Raytheon 400
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N570TM
Onboard fatalities
Unknown
Route
From Teterboro Airport (KTEB), Teterboro, NJTo Burke Lakefront Airport (KBKL), Cleveland, OH
Aircraft age
About 18 years (built 2000)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 135: Air Taxi & Commuter
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · landing roll
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Runway excursion
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Environmental issues › Conditions/weather/phenomena
  • Environmental issues › Operating environment

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB 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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18LA094
Event ID
20180207X21243
Case number
CEN18LA094
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2018-02-05.
  • API snapshot SHA-256: 9356e23012fb4004aec7e2e680bbf45ed888ab2a9923c551a132c8b27bd1a588; retrieved 2026-09-16T06:26:17.866Z.