# NTSB DFW05CA224: Cessna 152, N4670B, Tulsa, OK, August 29, 2005

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: August 28, 2005, 21:18 local (Aug 29, 2005, 02:18 UTC)
- Place: Tulsa, OK
- Coordinates: 36.043609, -95.983329
- Nearby events: https://openairdocs.org/map.md?lat=36.0436&lon=-95.9833&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report December 20, 2005
- Report: Approved by Office Director
- Parties: Federal Aviation Administration
- NTSB case key (mKey): 62353
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=DFW05CA224
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/62353/pdf
- Page: https://openairdocs.org/ntsb/DFW05CA224

## Probable cause

The pilot's improper recovery from a bounced landing.  A contributing factor was the dark night conditions.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Hard landing, landing
  - light condition - dark night (contributing factor)
  - recovery from bounced landing - improper, pilot in command (cause)
- Loss of control - on ground/water, landing
- Nose gear collapsed, landing - roll
- Nose over, landing - roll
  - terrain condition - soft (contributing factor)

## Analysis

On final approach, for his eighth night landing of the evening, the 264-hour instrument rated private pilot observed that he was "high" for runway 1R (a 4,208 foot by 100 foot asphalt runway).  The pilot initiated a forward slip to lose altitude and the airplane momentarily touched down on the runway before becoming airborne again.  The pilot attempted to hold the airplane in a flare but it "started going into oscillations."  He then attempted to "go around", but approximately five feet above the ground (agl) the airplane stalled and impacted the runway. The nose landing gear collapsed and airplane departed the edge of the runway into soft terrain, nosed over, and came to rest in an inverted position.  An examination of the airplane revealed the fuselage, vertical stabilizer, and wings sustained structural damage. The pilot reported that there was no mechanical malfunction or failure with the airplane.

## Factual narrative

On August 28, 2005, about 2118 central daylight time, a single-engine Cessna 152 airplane, N4670B, was substantially damaged following a loss of control during landing at the Richard Lloyd Jones Jr. Airport (RVS), near Tulsa, Oklahoma.  The instrument rated private pilot, the sole occupant of the airplane, was not injured.  The airplane was owned and operated by Spartan Aviation Industries, Inc., of Tulsa, Oklahoma.  Night visual meteorological conditions prevailed and a flight plan was not filed for the 14 Code of Federal Regulations Part 91 personal flight.  The local flight originated from RVS at approximately 2020.

The 264-hour pilot reported that he was on final approach for his eighth night landing of the evening when he observed that he was "high" for runway 1R (a 4,208 foot by 100 foot asphalt runway).  The pilot initiated a forward slip to lose altitude and the airplane momentarily touched down on the runway before becoming airborne again.  The pilot attempted to hold the airplane in a flare but it "started going into oscillations."  He then attempted to "go around", but approximately five feet above the ground (agl) the airplane stalled and impacted the runway.  The nose landing gear collapsed and the airplane departed the edge of the runway into soft terrain, nosed over, and came to rest in an inverted position.

The pilot further reported that there was no mechanical malfunction or failure with the airplane.

A Federal Aviation Administration inspector, who examined the airplane, reported that the fuselage, vertical stabilizer, and wings sustained structural damage.

The pilot reported calm winds, visibility 10 statute miles, clear skies, temperature 75 degrees Fahrenheit, dew point 65 degrees Fahrenheit and a barometric pressure setting of 29.91 inches of Mercury.

## Aircraft

- Registration: [N4670B](https://openairdocs.org/deregistered/N4670B-2005-10-14), registration cancelled 2005-10-14, S/N 15283574, built 1979 (OpenAirDocs)
- Reported make and model: Cessna 152
- Registry model: [Cessna 152](https://openairdocs.org/model/cessna-152) (registry code 2071835) (OpenAirDocs)
- Registry engine: [Lycoming 0-235 series](https://openairdocs.org/engine/lycoming-0-235-series) (registry code 41505, 4 cycle) (OpenAirDocs)
- Category: Airplane
- Serial number: 15283574
- Airframe hours: 18511
- Engines: Lycoming O-235 110 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Spartan Aviation Industries Incorporated
- Airworthiness certificate: Standard, Utility
- Last inspection: 100 hour, July 1, 2005, 99 hours before
- Departed: RVS, Tulsa, OK
- Destination: RVS, Tulsa, OK
- Airport: RVS, Richard Lloyd Jones Jr. Apt, runway 1R, 4,208 × 100 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 22; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 2; last flight review July 1, 2005; seat: left; flight hours: 264 total, 98 in this make and model, 97 as pilot in command, 177 in the last 90 days, 81 in the last 30 days

## Weather

- Conditions: Visual (VMC), Night
- Wind: calm
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 86 °F, dew point 70 °F
- Altimeter: 29.90 inHg

## 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 20050828018849A](https://openairdocs.org/incident/20050828018849A), Aug 28, 2005: Cessna 152, Tulsa, OK, Destroyed. (-23) Pilot stated that he had done about 15 night touch and goes and was performing his last approach. He realized that he was too high but thought he could…

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.
