# Incident 20220721009369I: Cessna 172N, Omaha, NE, July 21, 2022 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: July 21, 2022, 18:14 local time - Place: Omaha, NE - Airport: Eppley Airfield - Damage: Minor damage - Phase of flight: Taxi - Operating rules: Pilot school (Part 141) - Operator: 2OAS - Location: 41.3032° N, 95.8941° W: Placed by OpenAirDocs at EPPLEY AIRFIELD (OMA), within about a mile (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=41.3032&lon=-95.8941&mi=10 - Aircraft: N737NU, registered now (https://openairdocs.org/aircraft/N737NU) (OpenAirDocs) - Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs) - Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs) - Reported make and model: CESSNA 172N - Reported engine: LYCOMING 0-320 SERIES - People aboard: 2 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Commercial pilot, flight instructor - Pilot flight hours: 2,366 total, 468 in this make and model, 57 in the last 90 days - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20220721009369I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ON JULY 21, 2022, AT APPROXIMATELY 1814 LOCAL TIME ^PRIVACY DATA OMITTED^ A CESSNA 172 CONDUCTING PILOT TRAINING WAS DAMAGED WHEN IT TAXIED THROUGH UNEXPECTED HIGH VELOCITY JET EXHAUST AT EPPLEY AIRFIELD, IN OMAHA NEBRASKA. THE AIRCRAFT WAS TRAVELING ON AN ACTIVE TAXIWAY, WHILE COMPLYING WITH A TAXI CLEARANCE BY AIR TRAFFIC CONTROL. THE SECOND AIRCRAFT, ^PRIVACY DATA OMITTED^ A DASSAULT FALCON 2000EX, COMPLIED WITH A TAXI CLEARANCE TO ENTER THE RUNWAY 18 RUN UP AREA. ^PRIVACY DATA OMITTED^ POSITIONED THE AIRCRAFT IN THE RUNUP AREA WITH THE NOSE OF THE AIRCRAFT FACING AWAY FROM THE TAXIWAY PRIOR TO ^PRIVACY DATA OMITTED^ PASSING BEHIND IT. THE POSITION AND ORIENTATION OF ^PRIVACY DATA OMITTED^ CAUSED THE JET ENGINE EXHAUST TO BE DIRECTED TOWARD AND ACROSS THE ACTIVE TAXIWAY. ACCORDING TO THE FALCON PILOT ^PRIVACY DATA OMITTED^ WAS CONDUCTING A POWER ASSURANCE ENGINE RUN WHICH REQUIRED ENGINE POWER SETTINGS AS HIGH AS TAKEOFF POWER FOR PERIODS AS LONG AS 2 MINUTES, THEN DECREASING INCREMENTALLY. DURING THE PERIOD THE CESSNA PASSED DIRECTLY BEHIND ^PRIVACY DATA OMITTED^ ON THE TAXIWAY THE POWER WAS ESTIMATED AT APPROXIMATELY 85% N1 ACCORDING TO THE CREW OF^PRIVACY DATA OMITTED^. THE EXHAUST FROM ^PRIVACY DATA OMITTED^ CAUSED LOSS OF DIRECTIONAL CONTROL OF THE CESSNA BY LIFTING THE RIGHT WING OF THE CESSNA RESULTING IN THE LEFT WING IMPACTING THE TAXIWAY. THE RESULTING FRICTION OF THE LEFT WINGTIP IMPACT CAUSED THE CESSNA TO YAW TO THE LEFT. THE LEFT YAW ROTATION OF THE TAIL HIGH LEFT WING LOW POSITION OF THE CESSNA RESULTED IN THE PROPELLER STRIKING THE TAXIWAY. FOLLOWING THE PROPELLER STRIKE THE CESSNA RE-ESTABLISHED POSITION ON ALL THREE LANDING GEAR AS IT EXITED THE JETBLAST ENVIRONMENT AND TAXIIED INTO THE RUNUP AREA. THE CFI IN THE CESSNA REPORTED THE ENCOUNTER TO AIR TRAFFIC CONTROL, THEN REQUESTED, AND WAS PROVIDED, TAXI CLEARANCE TO RETURN TO THE RAMP TO INSPECT THE AIRCRAFT FOR DAMAGE. THERE WERE NO INJURIES TO THE OCCUPANTS OF EITHER AIRCRAFT. THE FALCON WAS NOT DAMAGED, HOWEVER ON INSPECTION DAMAGE TO THE CESSNA PROPELLER AND LEFT WINGTIP WAS OBSERVED. AFTER FURTHER INSPECTION, THE DAMAGE TO THE CESSNA WAS NOT CLASSIFIED AS SUBSTANTIAL. 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.