# NTSB ATL99LA080: Cessna 182, N6382B, Murfreesboro, TN, May 2, 1999

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: May 2, 1999, 17:22 local (22:22 UTC)
- Place: Murfreesboro, TN
- Coordinates: 35.92947, -86.440025 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=35.9295&lon=-86.4400&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report June 21, 2000
- Report: Approved by Office Director
- NTSB case key (mKey): 46245
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ATL99LA080
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/46245/pdf
- Page: https://openairdocs.org/ntsb/ATL99LA080

## Probable cause

The pilot's misjudgment of altitude and distance to the runway.

## Analysis

The pilot reported that, he had completed one touch and go landing and was on short final for the second landing on runway 36.  The pilot reported that the airplane got low on final approach and collided with the airport perimeter fence approximately 300 feet from the approach end of  runway 36. The pilot did not report a mechanical problem with the airplane.

## Factual narrative

On May 2, 1999, at 1722 central daylight time, a Cessna 182, N6382B, collided with the top two strains of a chain link fence during an approach to land at the Murfreesboro, Municipal Airport in Murfreesboro, Tennessee.  The personal flight was operated by the pilot under the provisions of Title 14 CFR Part 91 with no flight plan. Visual weather conditions prevailed at time of the accident.  The pilot and his passenger were not injured; the airplane sustained substantial damage. The flight departed Murfreesboro, Tennessee, at 1700.

According to the pilot, he had completed one touch and go landing and was on short final for the second landing on runway 36.  The pilot reported that the airplane got low on final approach and collided with the airport perimeter fence approximately 300 feet from the approach end of  runway 36.

The pilot did not report a mechanical problem with the airplane.

## Sequence of events

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

- Undershoot, approach - vfr pattern - final approach
  - altitude - misjudged, pilot in command (cause)
  - distance - misjudged, pilot in command (cause)
- In flight collision with object, landing - flare/touchdown
  - object - fence

## Aircraft

- Registration: [N6382B](https://openairdocs.org/deregistered/N6382B-2002-07-09), registration cancelled 2002-07-09, S/N 34282 (OpenAirDocs)
- Reported make and model: Cessna 182
- Registry model: [Cessna 182A](https://openairdocs.org/model/cessna-182a) (registry code 2072704) (OpenAirDocs)
- Category: Airplane
- Serial number: 34282
- Airframe hours: 620
- Engines: Continental O-470-R 230 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: James J. Akins
- Registered owner: Mid Tenn Flying Club Inc.
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, November 5, 1998, 49 hours before
- Departed: MQY, SMYRNA, TN
- Airport: MBT, Murfreesboro Municipal, runway 36, 3,898 × 100 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 76; private; airplane ratings: single-engine land; medical: class 3, valid medical--w/ waivers/lim; seat: left

## Weather

- Conditions: Visual (VMC), Day
- Wind: 360° at 5 knots
- Visibility: 15 statute miles
- Lowest ceiling: 2,000 ft broken
- Temperature: 75 °F
- Altimeter: 29.00 inHg
- Observed at: MQY, 10 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 19990502004419A](https://openairdocs.org/incident/19990502004419A), May 2, 1999: Cessna 182A, Murfreesboro, TN, Substantial damage. Pilot was practicing touch and go landings when the pilot lost control of the acft on landing, and the acft was destroyed, other circumstances are unknown.…

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date; 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.