Champlain Enterprises Bombardier Inc DHC 8 202 accident
Bombardier Inc DHC 8 202 · Accident: system/component malfunction/failure (non-power) on approach
From Albany International Airport (ALB) to Washington Dulles International Airport (IAD)
Event
- NTSB case
- DCA16CA226
- 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
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Bombardier Inc DHC 8 202
- Aircraft type
- Bombardier DHC-8
- 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
- N366PH
- Operator
- Champlain Enterprises
- Onboard fatalities
- Unknown
- Route
- From Albany International Airport (ALB), Albany, NYTo Washington Dulles International Airport (IAD), Dulles, VA
- Aircraft age
- About 18 years (built 1998)
- 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
- Approach
- 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
- System/component malfunction/failure (non-power)
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On September 24 2016, at about 1015 PM EDT, Commutair flight 4919, a De Havilland Dash 8-200, N366PH, performed a nose gear up landing on runway 1R after the nose gear would not fully extend during approach to Washington Dulles International Airport (KIAD), Dulles, Virginia. The passengers were evacuated via exit doors on the runway. There were no injuries to the 21 passengers and 3 crew members and the airplane sustained substantial damage. The flight was operating under the provisions of 14 Code of Federal Regulations Part 121 as a regularly scheduled passenger flight from Albany International Airport (KALB), Albany, New York to KIAD.
According to the operator, the airplane was scheduled for maintenance during an overnight period on the evening before the accident flight at the Albany Maintenance Hangar Facility at KALB. As part of the scheduled maintenance, a frangible towing fuse in the nose landing gear mechanism was removed and replaced. The aircraft was released from maintenance and signed off for revenue service on the morning of the accident flight.
According to the flight crew, the flight was uneventful until the final approach phase when they were configuring the airplane for landing at KIAD. After selecting the gear down, both main landing gear indicated down and locked but the nose gear indicated that the gear doors remained open and that the gear was unsafe. The flight crew then retracted the main landing gear and climbed to 3000 feet.
While at altitude, the flight crew attempted to lower the gear a second time but the same result was indicated. The flight crew then performed the manual gear extension, but the nose gear still failed to extend. The flight conducted a low pass of the airport and ground personnel confirmed that the main landing gear were down, but the nose gear was retracted with the doors open. The flight crew climbed back to 3,000 feet, declared an emergency and requested airport emergency vehicles standby.
During the landing roll, the nose of the airplane contacted the runway surface and the captain shut down the engines after the airplane came to a stop and called for an evacuation. None of the passengers or crew were injured.
Examination of the airplane found substantial damage to the airplane skin and forward pressure vessel as a result of the contact with the runway. Inspection of the nose gear system found that the frangible towing fuse, which was replaced before the flight, was incorrectly installed.
Probable cause
incorrect installation of the frangible towing fuse that prevented the nose landing gear from extending.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA16CA226
- Event ID
- 20160927X51937
- Case number
- DCA16CA226
- 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: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 1ce109666a1cd0ebd65b0be847f1d3493851a19115f6c90b96012bb591a33dde; retrieved 2026-09-16T04:19:11.994Z.