# Accident 20020419008239A: Cessna T206H, Sedona, AZ, April 19, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 19, 2002, 12:50 local time
- Place: Sedona, AZ
- Airport: Sedona Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 34.8486° N, 111.7883° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=34.8486&lon=-111.7883&mi=10
- Aircraft: N377ME, registered now (https://openairdocs.org/aircraft/N377ME) (OpenAirDocs)
- Registry model: Cessna T206H (registry code 2073303, https://openairdocs.org/model/cessna-t206h) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: CESSNA T206H
- NTSB investigation: [NTSB LAX02LA140](https://openairdocs.org/ntsb/LAX02LA140) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020419008239A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(.19) ON APRIL 19, 2002, AT 1250 MOUNTAIN STANDARD TIME, A CESSNA T206H, N377ME, SUSTAINED SUBSTANTIAL FUSELAGE STRUCTURAL DAMAGE AFTER PORPOISING FOLLOWING A BOUNCED LANDING AT THE SEDONA, ARIZONA, AIRPORT. THE AIRCRAFT WAS OWNED AND OPERATED BY THE PILOT UNDER THE PROVISIONS OF 14 CFR PART 91 OF THE FEDERAL AVIATION REGULATIONS. NEITHER THE PRIVATE PILOT NOR THE THREE PASSENGERS ON BOARD WERE INJURED. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AND NO FLIGHT PLAN WAS FILED FOR THE PERSONAL CROSS-COUNTRY FLIGHT THAT ORIGINATED AT CAMARILLO, CALIFORNIA, AT 1000. THE AIRPLANE WAS LANDING ON RUNWAY 21, AND THE OFFICIAL ASOS OBSERVATION AT THE TIME OF THE ACCIDENT INCLUDED WINDS FROM 170 DEGREES AT 19 KNOTS WITH HIGHER GUSTS TO 26 KNOTS. THE ACCIDENT SEQUENCE WAS WITNESSED BY THE OWNER OF AN FBO ON THE AIRPORT. HE REPORTED THAT THE PILOT WAS TRYING TO LAND ON RUNWAY 21 WITH A STRONG QUARTERING HEADWIND THAT HAD A SIGNIFICANT GUST COMPONENT. THE WITNESS SAID THAT RUNWAY 21 HAS ABOUT A 2 PERCENT DOWNSLOPE. HE SAW THE AIRPLANE BOUNCE OFF THE MAIN GEAR AND BEGIN A SERIES OF PORPOISE LIKE PILOT INDUCED OSCILLATIONS WHERE THE AIRPLANE BOUNCED FROM THE NOSE WHEEL TO THE MAIN GEAR AND BACK AGAIN, WITH AN INCREASING AMPLITUDE. ON THE FOURTH PORPOISE, THE AIRPLANE'S TAIL STRUCK THE RUNWAY. THE AIRPORT MANAGER EXAMINED THE AIRPLANE AND REPORTED THAT THE SKIN WAS WRINKLED IN THE AREA OF THE FIREWALL, AND THAT A COMPRESSION BUCKLE EXTENDED CIRCUMFERENTIALLY AROUND THE FUSELAGE AT A POINT 3 FEET FORWARD OF THE HORIZONTAL STABILIZER LEADING EDGE. ACCORDING TO THE FEDERAL AVIATION ADMINISTRATION AIRMAN RECORD FILES, AN ORIGINAL ISSUANCE PRIVATE PILOT CERTIFICATE WAS ISSUED TO THE PILOT ON FEBRUARY 27, 2002. (-23) PIC DEPARTED CAMARILLO CA. (CMA) ON A CROSS COUNTRY FLIGHT TO SEDONA, AZ (SEZ) ITH 3 PASSENGERS. FLIGHT WAS SMOOTH UNTIL ARRIVAL AT SEZ. PIC STATES THAT ON SHORT FINAL TO RUNWAY 21, WINDS WERE REPORTED AS 170 DEGREES AT 19 KNOTS, GUSTS TO 26. HE APPROACHED AT A HIGHER AIRSPEED DUE TO THE TURBULENCE. AIRCRAFT BOUNCED UPON TOUCHDOWN AND BEGAN TO "PORPOISE", FOR A TOTAL OF FOUR "BUMPS" AS DESCRIBED BY THE PIC. ON THE FINAL BUMP, THE AIRCRAFT'S TAIL STRUCK THE RUNWAY WITH ENOUGH FORCE TO CAUSE SUBSTANTIAL DAMAGE TO THE TAIL SECTION. THE AIRCRAFT WAS THEN BROUGHT UNDER CONTROL AND WAS TAXIIED TO THE RAMP.

## 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 LAX02LA140](https://openairdocs.org/ntsb/LAX02LA140), Apr 19, 2002: Cessna T206H (N377ME), Sedona, AZ, substantial damage. Probable cause: The pilot's inadequate compensation for the variable, gusty and crosswind conditions, which led to a bounced landing and a subsequent pilot induced porpoise oscillation. A factor in the accident was…

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.