CHI82DA064 · Fairchild Hiller 227C
Britt Airways Fairchild Hiller 227C · Accident: hard landing
From Bloomington, IL to Bloomington, IN
Event
- NTSB case
- CHI82DA064
- 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
- 0
- 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
- General aviation
- 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
Fairchild Hiller 227C
- Aircraft type
- Fairchild Hiller 227
- 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
- N378NE
- Operator
- Britt Airways
- Onboard fatalities
- Unknown
- Route
- From Bloomington, ILTo Bloomington, IN
- 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 91: General Aviation
- 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 · flare/touchdown
- 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
- Hard landing
- 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
- Pilot in command › Airspeed, inadequate
Approximate · Estimated position: the centre of Bloomington, IN, the place the record names. Not the accident site.
NTSB narrative
THE AIRCRAFT WAS BEING PRE-POSITIONED FOR A SCHEDULED FLIGHT. DURING A VISUAL APPROACH TO LAND, THE CAPTAIN (PIC) CALLED FOR THE FLAPS TO BE LOWERED IN INCREMENTAL SETTINGS (16.5, 27 & 40 DEG). THE FLAP HANDLE WAS MOVED TO THE APPROPRIATE POSITIONS, BUT REPORTEDLY, NEITHER OF THE PILOTS LOOKED AT THE FLAP INDICATOR. THE PIC STATED THAT DURING THE FLARE, THE AIRCRAFT SETTLED AND CONTACTED THE RUNWAY QUITE HARD. HE IMMEDIATELY LOOKED DOWN AND SAW THE FLAP INDICATOR AT 16.5 DEG, THEN NOTICED THE FLAPS HAD EXTENDED TO 40 DEG. THE COPILOT SAW THE FLAPS AT 30 DEG AND MOVING TO FULL DOWN. DURING TOUCHDOWN, THE FUSELAGE WAS DAMAGED AROUND THE TAIL BUMPER/SKID TO THE LOWER PORTION OF THE PRESSURE BULKHEAD. ON A SUBSEQUENT FLIGHT FOR REPAIR, THE FLAPS OVER-RAN THE UP-LIMIT MICROSWITCH AND THEN WOULD NOT EXTEND. THE AIRCRAFT WAS EQUIPPED WITH A MODEL FPC-75 GROUND PROXIMITY WARNING SYSTEM IN ACCORDANCE WITH STC SA1176CE AND WAS WIRED INTO THE FLAP SELECTOR SWITCH. IT WOULD HAVE PROVIDED A WARNING IF IT HAD DETECTED FLAP PSN.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI82DA064
- Event ID
- 20020917X01813
- Case number
- CHI82DA064
- 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: investigation status. 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: 8b108094a349700c26bb565fdefc6df392fd39e33a892423dbbea0d03bfd8575; retrieved 2026-09-24T03:39:06.064Z.