Champlain Enterprises Bombardier Inc DHC-8-202 accident
Bombardier Inc DHC-8-202 · Accident: abnormal runway contact
From Unalakleet Airport (UNK) to Unalakleet Airport (UNK)
Event
- NTSB case
- ERA09LA529
- 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
- Event fatalities
- Unknown
- 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
- Not recorded
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
- N367PH
- Operator
- Champlain Enterprises
- Onboard fatalities
- Unknown
- Route
- From Unalakleet Airport (UNK), UnknownTo Unalakleet Airport (UNK), Unknown
- 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
- Unknown
- 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
- Abnormal runway contact
- 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
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On an unknown date and at an unknown time, the airplane sustained substantial damage to the bottom of the fuselage tail section. The damage was found during a maintenance C-check inspection on August 29, 2009. The damage was found when maintenance personnel were inspecting the inside of the tail section and noticed bowing and bending in the support structure and damage to nearby rivets. The damage was consistent with tail strike damage and had resulted in a puncture of the pressure vessel of the airplane. According to the maintenance task cards for different inspections of the airplane, an exterior inspection was to be completed prior to any other work. At least three exterior inspections were completed within the weeks preceding the discovery of the damage, including the inspection in which the damage was discovered. Each inspection required examination of the damaged area. Because maintenance personnel likely missed the damage during these inspections, pilots performing preflight checks of the airplane would be just as likely to miss the damage. Due to the height of the damage personnel would likely need to bend down in order to see it.
Probable cause
Undetermined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09LA529
- Event ID
- 20090921X05830
- Case number
- ERA09LA529
- 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. Values present in the bulk record are kept.
- The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: addf3bcc9370278d496ad18766ad94f0b6047433514529faa34357df13133037; retrieved 2026-09-15T13:19:47.382Z.