CHI84IA314 · Boeing 727-2M7
Boeing 727-2M7 · Incident: airframe, component or system failure en route
From Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (MSP) to San Francisco International Airport (SFO)
Event
- NTSB case
- CHI84IA314
- 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
- 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
- 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
Boeing 727-2M7
- Aircraft type
- Boeing 727
- 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
- N721RW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (MSP), Minneapolis, MNTo San Francisco International Airport (SFO), San Francisco, CA
- 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
- En route · climb to cruise
- 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Flt control syst, wing flap control › Failure, partial
- Flt control syst, wing flap control › Previous damage
Approximate · Estimated position: the centre of Minneapolis, MN, the place the record names. Not the accident site.
NTSB narrative
THE CREW REPORTED THAT THEY NOTICED A DECREASE IN CLIMB RATE WHILE OVER RAPID CITY, SD, EN ROUTE FROM MSP TO SFO AT FLT LEVEL 310. THE PLT NOTED FUEL BURN WAS APRX 1400 LBS AHEAD OF SCHEDULE. IN-FLT INSPECTION REVEALED THAT THE INBOARD TRAILING EDGE FLAPS HAD FAILED TO RETRACT PROPERLY AFTER TAKEOFF AND REMAINED IN A 7 DEG DOWN POSITION. THE FLT RETURNEDTO MINNEAPOLIS AND LANDED AT 1540 CDT (APRX 50 MINS AFTER THE INCIDENT). A POST FLT INSPECTION DISCLOSED THAT THE INBOARD FLAP CONTROL VALVE HAD FAILED. THE FLT CREW SAID THAT THIS MALFUNCTION HAD OCCURRED ON A PREVIOUS FLT AND HAD BEEN REPORTED. THE FLAPS HAD GROUND CHECKED OK BOTH ON THIS & THE PREVIOUS OCCASION. THIS REPORTED FAILURE WAS CORRECTEDBY REPUBLIC AIRLINES MAINTENANCE BY REPLACEMENT OF A FLAP CONTROL VALVE AND INSPECTION OF THE RIGGING IN ACCORDANCE WITHBOEING MAINTENANCE MANUAL 27-51-51, AFTER THIS INCIDENT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI84IA314
- Event ID
- 20001214X40227
- Case number
- CHI84IA314
- 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, damage. 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: 0dbbf31503c665414f23888ba60a0d1a5cbbde5167c0d89ba4da3772e9bc7a55; retrieved 2026-09-18T20:38:26.183Z.