# Accident 20000818038639A: Cessna 172N, Flagstaff, AZ, August 18, 2000 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: August 18, 2000, 09:13 local time - Place: Flagstaff, AZ - Airport: Flagstaff Pulliam Airport - Damage: Substantial damage - Phase of flight: Go Round (Aborted VFR) - Operating rules: General operating rules (Part 91) - Location: 35.2292° N, 111.7191° W: From the FAA, an estimate near the named town, within about 3 miles - Nearby events: https://openairdocs.org/map.md?lat=35.2292&lon=-111.7191&mi=10 - Aircraft: N2078E, a cancelled registration (https://openairdocs.org/deregistered/N2078E-2019-03-19) (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: LYC O360* - People aboard: 1 - Fatal injuries: 0 - Pilot flight hours: 80 total, 35 in this make and model, 2 in the last 90 days - NTSB investigation: [NTSB LAX00LA305](https://openairdocs.org/ntsb/LAX00LA305) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20000818038639A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (-23)PILOT STATED THAT HE MADE A NORMAL APPROACH AND AFTER TOUCH-DOWN, BALLOONED SLIGHTLY AND ADDED A SMALL AMOUNT OF POWER TO CORRECT. THE A/C BALLOONED EVEN MORE, SO FULL POWER WAS ADDED TO INITIATE A BALKED LANDING (GO-AROUND), FLAPS WERE REDUCED ONE NOTCH(TO 20 DEGREES). A HIGH SINK RATE DEVELOPED, FLAPS WERE PUT BACK IN, A HARD LANDING RESULTED, THE AIRCRAFT BOUNCED AGAIN, CONTROL WAS LOST AND A DISTANCE REMAINING SIGN WAS STUCK, RESULTING IN SUBSTANTIAL DAMAGE TO THE RIGHT WING SPAR AND NOSEWHEEL. (.4)ON AUGUST 18, 2000, ABOUT 0913 HOURS MOUNTAIN STANDARD TIME, A CESSNA 172, N2078E, WAS SUBSTANTIALLY DAMAGED DURING LANDING AT FLAGSTAFF, ARIZONA. THE PRIVATE PILOT WAS NOT INJURED. THE AIRPLANE WAS OPERATED UNDER THE PROVISIONS OF 14 CFR PART 91 BY GLENDALE AVIATION, GLENDALE, ARIZONA, AND RENTED BY THE PILOT FOR A LOCAL AREA PERSONAL FLIGHT. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AND NO FLIGHT PLAN WAS FILED. THE FLIGHT ORIGINATED AT GLENDALE ON THE MORNING OF THE ACCIDENT ABOUT 0700. ACCORDING TO THE FLAGSTAFF CONTROL TOWER, THE PILOT WAS LANDING ON RUNWAY 21 WHEN DIRECTIONAL CONTROL WAS LOST AND THE AIRPLANE VEERED OFF THE LEFT SIDE OF THE RUNWAY COLLIDIN G WITH A 5,000-FOOT REMAINING MARKER SIGN. THE WINDS WERE REPORTED AS 220 DEGREES AT 6 KNOTS AND THE DENSITY ALTITUDE WAS 9,083 FEET. THE 80-HOUR PRIVATE PILOT REPORTED THAT DURING THE LANDING TOUCHDOWN ON RUNWAY 21, THE AIRPLANE BOUNCED AND BALLOONED. HE ADDED POWER TO SOFTEN THE LANDING, BUT THE AIRPLANE BALLOONED FURTHER. AT THAT POINT, THE PILOT DECIDED TO PERFORM A GO-AROUND. HE APPLIED FULL POWER AND STARTED CLIMBING. THE STALL WARNING WAS GOING OFF, SO HE REDUCED THE ANGLE OF ATTACK. HE REMOVED THE FIRST NOTCH OF FLAPS, AS DIRECTED BY THE BALKED LANDING PROCEDURE, AND THE AIRPLANE STARTED SETTLING BACK DOWN QUICKLY. HE PUT THE FLAPS BACK DOWN, BUT THE DESCENT WAS NOT STOPPED. ABOUT THE SAME TIME, THE AIRPLANE WAS HIT BY A WIND GUST FROM THE RIGHT, PUSHING THE PLANE LEFT. THE PILOT ATTEMPTED TO CORRECT BUT WAS BLOWN OFF THE RUNWAY, COLLIDING WITH A RUNWAY LENGTH REMAINING SIGN AND SUBSEQUENTLY, A DITCH. HE REPORTED THAT HE WAS NUMBER THREE TO LAND ON A LONG FINAL WITH FULL FLAPS. HE STATED THAT THERE WERE NO MECHANICAL ISSUES WITH THE AIRPLANE. ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB LAX00LA305](https://openairdocs.org/ntsb/LAX00LA305), Aug 18, 2000: Cessna 172 (N2078E), Flagstaff, AZ, substantial damage. Probable cause: The pilot's improper go-around procedure and his failure to maintain directional control on landing. ## Other reports on N2078E (1) Matched to the same aircraft by N-number and date. - [Incident 19970330014489I](https://openairdocs.org/incident/19970330014489I), Mar 30, 1997: Cessna 172N (N2078E), Buckeye, AZ, Substantial damage. Narrative: engine started running very rough and vibration unacceptable to continue level flight. The pilot made a precautionary emergency landing on a runway… 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.