Atlantic Coast Airlines Canadair CRJ-600 incident
Canadair CRJ-600 · Incident: on ground/water collision with object during landing
From Chicago O'Hare International Airport (ORD) to Central Illinois Regional Airport at Bloomington-Normal (BMI)
Event
- NTSB case
- CHI03IA070
- 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
- Incident
- 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
- Airline
- 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
Canadair CRJ-600
- Aircraft type
- Canadair CRJ-600
- 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
- N653BR
- Operator
- Atlantic Coast Airlines
- Onboard fatalities
- Unknown
- Route
- From Chicago O'Hare International Airport (ORD), Chicago, ILTo Central Illinois Regional Airport at Bloomington-Normal (BMI), Bloomington, IL
- Aircraft age
- Not recorded
- 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 121: Air Carrier
- 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
- First occurrenceThe 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
- On ground/water collision with object
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Airport personnel › Airport operations, inadequate
- Airport personnel › Airport snow removal, inadequate
- Landing gear, nose gear › Failure
- Landing gear, nose gear › Overload
- Pilot in command › Compensation for wind conditions, not performed
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Procedures/directives, not complied with
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The regional jet, operating as a 14 CFR Part 121 domestic passenger flight, sustained minor damage when the nose landing gear collapsed during landing rollout on runway 20. While en route to their destination, the flight crew obtained the airport Automated Terminal Information Service (ATIS) information. The ATIS information indicated the current winds were 060 degrees at 14 knots. Neither the captain nor the first officer checked the reported winds against the Wind Component Conversion Chart to determine whether the headwind/tailwind and crosswind components were within limits. The Wind Component Conversion Chart indicated that the tailwind component was 10.5 knots and the crosswind component was 9 knots. The airplane's tailwind limitation is 10 knots. The Flight Data Recorder (FDR) data indicated that the airplane landed with a 13 knot tailwind. Prior to the ILS instrument approach, the captain conducted an Approach Brief, but did not brief the missed approach procedures. The tower air traffic controller informed the pilot that snowplows had removed snow from the centerline of the runway and that the braking action was "fair to poor." The captain did not brief the first officer concerning procedures for landing on a contaminated runway. The FDR data indicated that the airplane touched down near the runway intersection, approximately 2,900 +/- 250 feet (2,650 feet to 3,150 feet) from the approach end of Runway 20. Runway 20 is 7,000 feet long. The desired touchdown point is 1,000 feet from the approach end of the runway, or the first 1/3 of the runway. Runway 20's touchdown zone limit is 2,333 feet from the approach end of the runway. The FDR data indicated that the aircraft touched down on a heading of 190 degrees at 124 knots computed airspeed with 0.4 degrees of nose up pitch. The data indicated the nose was pitching nose down at the time of touchdown. All three landing gear Weight-on-Wheels (WOW) switches changed from Air to Ground within 0.25 seconds of each other. Approximately 1.75 seconds later the nose landing gear WOW switched to Air again, indicating that the nose landing gear had collapsed. The vertical acceleration parameter did not show a significant load at touchdown. The airplane skidded to a stop on the runway. The captain reported that he inspected the runway and observed ridges of snow and ice near the runway intersection. The on-site inspection of the airplane revealed that the nose landing gear drag brace had broken and the nose landing gear collapsed rearward. The nose wheel and tire remained intact and were jammed under the airplane as it skidded to a stop. Metallurgical examination revealed that the drag brace failed due to the application of an overload and that there were no material defects. The Messier-Dowty analysis of the nose landing gear fracture indicated that the load required to fracture the drag brace was generated by hitting an obstacle. An investigation of airport operations revealed that the personnel inside the snow removal vehicles were making runway condition assessments by looking out their side view mirrors. The airport did not conduct or provide friction measurement reports and NOTAMS between the hours of 1900 and 2200 when airport conditions were rapidly changing with significant snowfall accumulations and snow removal equipment was actively operating on runway 20.
Probable cause
The pilot's improper in-flight decision to land on a runway with a tailwind component that exceeded the airplane's tailwind limitation and his failure to perform a go-around which resulted in the proper touchdown point not being attained and the airplane landing long. Also causal was the inadequate snow removal procedures used by the airport personnel and the airport personnel failed to issue NOTAMS in accordance with existing regulations, resulting in the landing gear to fail in overload as a result of hitting a ridge of snow and/or ice on the runway during landing roll. Additional factors included the contaminated runway; the tailwind; the snow; and the dark night.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI03IA070
- Event ID
- 20030220X00241
- Case number
- CHI03IA070
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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 2003-02-15.
- API snapshot SHA-256: 17452aab52cbd77812f9d94712ec1c0424148562b847e6e80db167230f66c47e; retrieved 2026-09-18T15:54:54.697Z.