# Accident 20210724011679A: Cessna 172, Iron Mountain, MI, July 24, 2021 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: July 24, 2021, 11:30 local time - Place: Iron Mountain, MI - Damage: Substantial damage - Phase of flight: Taxi - Operating rules: General operating rules (Part 91) - Location: 45.8269° N, 88.0594° W: Placed by OpenAirDocs: center of Iron Mountain, MI, within about 6 miles (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=45.8269&lon=-88.0594&mi=10 - Aircraft: N6778A, registered now (https://openairdocs.org/aircraft/N6778A) (OpenAirDocs) - Registry model: Cessna 172 (registry code 2072402, https://openairdocs.org/model/cessna-172) (OpenAirDocs) - Registry engine: Continental 0-300 series (registry code 17022, https://openairdocs.org/engine/continental-0-300-series) (OpenAirDocs) - Reported make and model: CESSNA 172 - Reported engine: CONT MOTOR 0-300 SER - People aboard: 3 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Airline transport - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20210724011679A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ON JULY 24, 2021 AT 11:20 LOCAL TIME, A CESSNA CE-172 AIRCRAFT, N6778A, ^PRIVACY DATA OMITTED^ OPERATED BY AN AIRLINE TRANSPORT PILOT, RECEIVED SUBSTANTIAL DAMAGE DURING TAXI OPERATIONS AT THE AT THE FORD AIRPORT (IMT), KINGSFORD, MICHIGAN. DAYLIGHT VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME OF THE ACCIDENT. THE PILOT AND PASSENGER WERE NOT INJURED. ACCORDING TO THE PILOT, FOLLOWING A LOCAL FLIGHT, HE WAS TAXIING ON THE MAIN RAMP TO HIS HANGAR AREA. HIS PATH ALONG THE RAMP PROCEEDED BEHIND A CRJ 200 JET AIRCRAFT, N699BR THAT, UNKNOWN TO THE PILOT, WAS IN THE PROCESS OF A MAINTENANCE RUN-UP. THE PILOT STATES HE HAD NO IDEA THE CRJ WAS EVEN RUNNING AS IT WAS CONED OFF WITH THE DOOR OPEN AND NO PERSONNEL OUTSIDE THE AIRCRAFT TO WARN OTHER PILOTS OF THE RUN-UP. AS THE PILOT TAXIED, HE WAS ALMOST DIRECTLY BEHIND THE CRJ WHEN HE HEARD THE ENGINES SPOOL UP. AT THIS TIME THE 172 BEGAN AN UNCONTROLLED MOVEMENT ALONG THE CONCRETE THAT RESULTED IN THE TAIL COMING UP AND THE AIRCRAFTS LEFT WING AND PROPELLER STRIKING THE SURFACE. ONCE THE AIRCRAFT WAS NO LONGER IN THE JET BLAST AREA IT CAME BACK DOWN IN AN UPRIGHT POSITION. CFR WAS NOTIFIED AND RESPONDED. THERE WAS NO POST-CRASH FIRE. THE PILOT ALSO STATES HE WAS UNABLE TO MAKE RADIO CONTACT WITH THE MAINTENANCE CREW TO NOTIFY THEM OF THE SITUATION. THE MAINTENANCE CREW DID NOT ANNOUNCE OVER UNICOM THAT THE MAINTENANCE RUN-UP WAS UNDERWAY, SO GAVE NO WARNING TO AIRCRAFT IN THE AREA OF THE CRJ. FOLLOWING THE ACCIDENT, THE MAINTENANCE CREW SHUT THE AIRCRAFT DOWN AND WALKED INTO THE TERMINAL BUILDING UNKNOWING WHAT HAD TRANSPIRED BEHIND THE JET. ACCORDING TO THE AIRPORT MANAGER, IT IS NOT STANDARD PRACTICE FOR MAINTENANCE RUN-UP?S TO BE CONDUCTED ON THE MAIN RAMP/ TAXI AREA AT THE FORD AIRPORT. ACCORDING TO THE MAINTENANCE CREW, THE GATE AGENT GAVE THEM PERMISSION TO CONDUCT THE RUN-UP ON THE RAMP. PHOTOGRAPHS SHOW THE 172 UPRIGHT WITH THE PROPELLER TIPS BENT FORWARD. THE LEFT LANDING GEAR IS BENT OUTWARD SLIGHTLY. THE LEFT WING IS BENT UPWARD OUTBOARD OF THE WING STRUT WITH SKIN WRINKLED ON THE UNDERSIDE. THE MAIN WING SPAR DOES APPEAR TO HAVE BEEN DAMAGED NEAR THE OUTBOARD 3 FEET OF THE WING. THERE IS A LARGE FUEL STAIN UNDER THE LEFT WING CAUSED BY FUEL SPILLAGE DURING THE ACCIDENT. ADDITIONALLY, ACCORDING TO THE PILOT, THE NOSE GEAR WAS OVER STRESSED DURING THE EVENT RESULTING IN RUDDER CABLE STRETCH OR DISCONNECT. WEATHER WAS NOT A FACTOR IN THIS ACCIDENT. THE MAINTENANCE CREW OF THE CRJ 200, PERFORMING AN ENGINE RUN-UP IN AN AIRPORT AREA NOT AUTHORIZED FOR THAT ACTIVITY NOR FOLLOWING APPROVED MAINTENANCE PROCEDURES INCLUDING RADIO COMMUNICATIONS WITH OTHER AIRCRAFT ON GROUND ARE CAUSAL FACTORS IN THIS ACCIDENT. ## NTSB investigation None matched to this report by aircraft and date. Search the NTSB's own records: https://data.ntsb.gov/carol-main-public/basic-search From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.