# NTSB DEN08CA117: Cessna T182T, N2164Y, Omaha, NE, June 13, 2008

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: June 12, 2008, 22:30 local (Jun 13, 2008, 03:30 UTC)
- Place: Omaha, NE
- Coordinates: 41.305278, -95.89389
- Nearby events: https://openairdocs.org/map.md?lat=41.3053&lon=-95.8939&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092)
- Highest injury: No injuries
- Injuries: 5 uninjured
- Status: Completed, report August 28, 2008
- Report: Approved by Office Director
- Parties: Lincoln Flight Standards District Office
- NTSB case key (mKey): 68354
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=DEN08CA117
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/68354/pdf
- Page: https://openairdocs.org/ntsb/DEN08CA117

## Probable cause

The pilot's improper use of the elevator trim resulting in a nose low/hard landing.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation; cases with it: [Cessna T182T, 10 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072738), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md)
- [Light condition: dark](https://openairdocs.org/ntsb-findings/03036020): Environmental issues › Conditions/weather/phenomena · Not specified; cases with it: [Cessna T182T, 1 case](https://openairdocs.org/ntsb-findings/03036020/cases.md?model=2072738), [All aircraft, 448 cases](https://openairdocs.org/ntsb-findings/03036020/cases.md)
- [Flight control system: elevator tab control system](https://openairdocs.org/ntsb-findings/01022731): Aircraft › Aircraft systems · Incorrect use/operation (probable cause); cases with it: [Cessna T182T, 1 case](https://openairdocs.org/ntsb-findings/01022731/cases.md?model=2072738), [All aircraft, 37 cases](https://openairdocs.org/ntsb-findings/01022731/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Cessna T182T, 9 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072738), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md)

## Analysis

The pilot reported that the aircraft bounced several times while attempting a night time landing causing a nose tire blowout and substantial damage to the airplane. The pilot stated that he utilized too much nose down trim. An examination of the airplane systems revealed no anomalies.

## Factual narrative

According to the pilot, the airplane was landing runway 32R. Prior to the flare, "the nose wheel touched the runway and the airplane bounced." The pilot "held the yoke steady and the airplane settled" unto the runway a second time resulting in another "bounce" that was higher than the first. Following a third "bounce" the pilot reported hearing a "thud", after which he applied power and initiated a go-around. During a second landing attempt the pilot reported that he was unable to raise the nose for the flare which resulted in the nose wheel touching the runway prematurely and another go-around. The third landing attempt was successful and the aircraft was towed from the runway due to a blown nose gear tire. The pilot stated, "Apparently I dialed in too much nose-down trim. This made it harder to pull the nose up for a good flare at the right time."

Examination of the airframe, conducted by the Federal Aviation Administration (FAA) on June 27, revealed a blown front tire, a wrinkled firewall, and forward nose gear tunnel damage.  The accident was reported to the National Transportation Safety Board on this same date. The pilot did not report any systems or control anomalies leading up to the accident.  An examination of the airplane systems conducted by the FAA revealed no anomalies.

## Aircraft

- Registration: [N2164Y](https://openairdocs.org/aircraft/N2164Y), registered now, S/N T18208685, built 2007 (OpenAirDocs)
- Reported make and model: Cessna T182T
- Registry model: [Cessna T182T](https://openairdocs.org/model/cessna-t182t) (registry code 2072738) (OpenAirDocs)
- Registry engine: [Lycoming TIO-540-AK1A](https://openairdocs.org/engine/lycoming-tio-540-ak1a) (registry code 42005, turbo-prop) (OpenAirDocs)
- Category: Airplane
- Serial number: T18208685
- Airframe hours: 338
- Engines: Lycoming TIO-540-AK1A 235 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, April 1, 2008
- Departed: FCM, MINNEAPOLIS, MN
- Destination: OMA, OMAHA, NE
- Airport: OMA, Eppley Airfield, runway 32R, 8,500 × 150 ft, concrete

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 60; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 2; seat: left; flight hours: 340 total, 34 in this make and model, 236 as pilot in command, 50 in the last 90 days, 14 in the last 30 days

## Weather

- Conditions: Visual (VMC), Night
- Wind: 330° at 4 knots
- Visibility: 3 statute miles
- Lowest ceiling: 4,700 ft broken
- Temperature: 66 °F, dew point 66 °F
- Altimeter: 29.73 inHg
- Observed at: KOMA, 1 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20080612840449A](https://openairdocs.org/incident/20080612840449A), Jun 12, 2008: Cessna T182T, Omaha, NE, Substantial damage. (-23) On June 12, 2008 at 22:30 CDT, a Cessna T182T, N2164Y arrived at Omaha, Nebraska Eppley Airfield on a night time vft cross country flight from flying…

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.

---
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.
