# NTSB DFW06CA132: Piper PA-28-161, N9419C, Marietta, OK, May 21, 2006

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Data collection · Final report
- Date: May 20, 2006, 21:15 local (May 21, 2006, 02:15 UTC)
- Place: Marietta, OK
- Coordinates: 33.891666, -97.168334
- Nearby events: https://openairdocs.org/map.md?lat=33.8917&lon=-97.1683&mi=10
- Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping)
- Highest injury: Minor injuries
- Injuries: 2 minor, 2 uninjured
- Status: Completed, report October 3, 2006
- Report: Approved by Office Director
- Parties: Oklahoma City, OK
- NTSB case key (mKey): 63717
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=DFW06CA132
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/63717/pdf
- Page: https://openairdocs.org/ntsb/DFW06CA132

## Probable cause

The pilot's failure to maintain airspeed which resulted in an inadvertent stall.  Contributing factors were the dark night conditions and the pilot's inadequate preflight planning and preparation.

## Sequence of events

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

- Loss of control - in flight, takeoff - roll/run
  - airspeed - not maintained, pilot in command (cause)
  - preflight planning/preparation - inadequate, pilot in command (contributing factor)
  - stall - inadvertent, pilot in command (cause)
  - light condition - dark night (contributing factor)
- In flight collision with terrain/water, descent - uncontrolled
  - object - tree(s)

## Analysis

The 175-hour private pilot reported in the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1) that he taxied to runway 17, and completed a run-up.  The pilot reported that "everything checked ok" and he proceeded with a takeoff.  During the night takeoff run from the 2,450-foot long, by 55-foot wide turf runway, the landing light "blinked off."  The pilot stated that despite the landing light going out he continued the takeoff run and rotated at 60 knots; however, he was concerned "about the trees at the end of the runway, so he was trying to get all the lift he could."   The pilot reported that he did not hear the "stall alarm," but thought he might have stalled the airplane.  The pilot also reported that the single-engine airplane with its three passengers was over its gross weight limit by approximately 135 pounds.  The airplane's takeoff performance chart reveals that in order to clear a 50-foot obstacle, the takeoff distance would be about 2,300 feet, with a dry, paved runway at gross weight.  Additionally, the density altitude was calculated by the NTSB Investigator-In-Charge (IIC) to be 3,038 feet.  At 2049, the automated weather observing system at the nearest airport with recorded weather, located approximately 15 miles north of the accident site, reported wind from 180 degrees at 6 knots, 10 miles visibility, a clear sky, temperature 86 degrees Fahrenheit, dew point 66 degrees Fahrenheit, and an altimeter setting of 29.83 inches of Mercury.

## Factual narrative

The 175-hour private pilot reported in the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1) that he taxied to runway 17, and completed a run-up.  The pilot reported that "everything checked ok" and he proceeded with a takeoff.  During the night take-off run from the 2,450-foot long, by 55-foot wide turf runway, the landing light "blinked off."  The pilot stated the despite the landing light going out he continued the take-off run and rotated at 60 knots; however, he was concerned "about the trees at the end of the runway, so he was trying to get all the lift he could."   The pilot reported that he did not hear the "stall alarm," but thought he might have stalled the airplane.  The pilot also reported that the single-engine airplane with its three passengers was over its gross weight limit by approximately 135 pounds.  The airplane's take-off performance chart reveals that in order to clear a 50-foot obstacle, the take-off distance would be about 2,300 feet, with a dry, paved runway at gross weight.  Additionally, the density altitude was calculated by the NTSB Investigator-In-Charge (IIC) to be 3,038 feet.  At 2049, the automated weather observing system at the nearest airport with recorded weather, located approximately 15 miles north of the accident site, reported wind from 180 degrees at 6 knots, 10 miles visibility, a clear sky, temperature 86 degrees Fahrenheit, dew point 66 degrees Fahrenheit, and an altimeter setting of 29.83 inches of Mercury.

## Aircraft

- Registration: [N9419C](https://openairdocs.org/deregistered/N9419C-2006-11-14), registration cancelled 2006-11-14, S/N 28-7816474, built 1978 (OpenAirDocs)
- Reported make and model: Piper PA-28-161
- Registry model: [Piper PA-28-161](https://openairdocs.org/model/piper-pa-28-161) (registry code 7102803) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 28-7816474
- Engines: Lycoming O-320 160 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Departed: T40, MARIETTA, OK
- Destination: 8F7, DECATUR, TX
- Airport: T40, Mcgehee Catfish Restaurant, runway 17, 2,450 × 55 ft, grass/turf

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 52; injuries: minor; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; seat: front; flight hours: 175 total, 26 in this make and model, 134 as pilot in command, 1 in the last 90 days, 1 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Night
- Wind: 180° at 6 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 86 °F, dew point 66 °F
- Altimeter: 29.82 inHg
- Observed at: 1F0, 15 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 20060520007209A](https://openairdocs.org/incident/20060520007209A), May 20, 2006: Piper PA28161, Marietta, OK, Destroyed. (-23) At approximately 2130 pilot and three passengers boarded aircraft and taxied to north end of runway and turned around. After performing runup checks…

## Other investigations on N9419C (2)

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 DFW05LA054](https://openairdocs.org/ntsb/DFW05LA054), Jan 8, 2005: Piper PA-28-161 (N9419C), Decatur, TX, substantial damage. Probable cause: The student pilot's failure to maintain obstacle clearance and the instructor's inadequate supervision. Contributing factors were the prevailing dark night conditions, and the power line.
- [NTSB DEN88LA078](https://openairdocs.org/ntsb/DEN88LA078), Feb 14, 1988: Piper PA-28-161 (N9419C), Aurora, CO, substantial damage

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.
