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

Bombardier INC CL600 2D24 incident near Detroit, Michigan, January 27, 2016

On January 27, 2016 at about 1:04 pm local time, a 2014 Bombardier INC CL600 2D24, registered N316PQ, was involved in an incident during takeoff near Detroit, Michigan (Detroit Metropolitan Wayne Cou airport). It was flown under scheduled airline rules (Part 121). The NTSB record does not give the injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The local controller's failure to visually scan and ensure that the runway surface was not occupied by a vehicle or other aircraft before issuing a takeoff clearance to the pilot. Contributing to this incident was the relieved controller's failure to monitor and review the position, after completing the relief briefing, to ensure that nothing had been overlooked.

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

What the record shows

Date
January 27, 2016 · about 1:04 pm local time · cases in 2016
Place
Detroit, Michigan · Detroit Metropolitan Wayne Cou · cases near this airport · map
Type
Incident
Injuries
The NTSB record does not give the injuries.
Weather
visual conditions (good weather)
Aircraft
Bombardier INC CL600 2D24 900, built 2014
Registration
N316PQ · registry record · serial 15316
Damage
Not recorded
Flight
Flight · scheduled airline rules (Part 121)

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

The Local Northwest (LNW) controller cleared Ops 373 (O373), an airport ops vehicle, to drive on runway 22L to conduct a routine inspection. About 90 seconds prior to the incident, and while O373 was operating on the runway, the LNW and Local Northeast (LNE) positions were combined and the LNE controller assumed all LNE and LNW duties. The LNW and LNE controllers conducted a required position relief briefing but did not conduct the briefing at the relieved position in accordance with standard operating procedures. During the position relief briefing, the LNW controller informed the LNE controller that O373 was driving on runway 22L and at about the same time, Endeavor Air (FLG3860), a CRJ 900, transmitted on the frequency they were ready for departure on runway 22L. About four seconds after completion of the position relief briefing, at 0802:44, the LNE controller instructed FLG3860 to line up and wait on runway 22L and at 0803:46 cleared FLG3860 for takeoff. About 20 seconds later the Airport Surface Detection System – Model X (ASDE-X) alerted indicating the runway was occupied by both FLG3860 and O373. The LNE controller instructed FLG3860 to "…abort takeoff" and instructed O373 to exit the runway. Both complied with the instruction. ASDE-X data indicated the closest proximity between FLG3860 and O373 was about 211 feet. The relieved LNW controller did not conduct a required two-minute overlap upon completion of the position relief briefing in order to monitor and review the position to ensure that nothing had been overlooked or incorrectly displayed. At the time of the incident, the tower was staffed with four personnel; one combined LNE/LNW controller, one combined ground northeast/ground northwest controller, one flight data/clearance delivery controller, and one controller in charge.

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 incursion veh/AC/person during takeoff defining event

The NTSB's findings

  • factor Personnel issues › Task performance › Communication (personnel) › Crew/duty change › over › ATC personnel
  • cause Personnel issues › Task performance › Use of equip/info › Use of policy/procedure › ATC personnel

The aircraft

  • Landing gear: retractable
  • Operator: Endeavor Air

The flight

  • Departed from: DTW Detroit MI
  • Destination: ORF Norfolk VA
  • Flight plan: IFR
  • Runway 22L, 12,003 ft by 200 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 250° at 9 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 4,000 ft; scat at 2,500 ft
  • Temperature: 28°F (-2°C), dew point 25°F (-4°C)
  • Altimeter: 30.20 inHg
  • Observation at 12:53 pm from KDTW, 1 miles away

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

7 documents, released by the NTSB on April 14, 2020. 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.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/OPS16IA002.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.