# NTSB LAX03LA185: Cessna 175A, N6902E, Ash Fork, AZ, June 7, 2003 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: June 7, 2003, 13:45 local (20:45 UTC) - Place: Ash Fork, AZ - Coordinates: 35.283332, -112.699996 - Nearby events: https://openairdocs.org/map.md?lat=35.2833&lon=-112.7000&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report September 29, 2004 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 57170 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX03LA185 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/57170/pdf - Page: https://openairdocs.org/ntsb/LAX03LA185 ## Probable cause The pilot's failure to attain and maintain an adequate airspeed, which resulted in a stall mush condition. Factors were the loose and uneven dirt runway surface, the known tailwind with gusts, and high density altitude. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - in flight, takeoff - initial climb - weather condition - tailwind (contributing factor) - weather condition - gusts (contributing factor) - weather condition - high density altitude (contributing factor) - airport facilities,runway/landing area condition - rough/uneven (contributing factor) - airport facilities,runway/landing area condition - short runway/landing area (contributing factor) - airspeed - not obtained/maintained, pilot in command (cause) - stall/mush - encountered, pilot in command - In flight collision with object, descent - uncontrolled - object - tree(s) ## Analysis The pilot collided with trees during the takeoff initial climb. When the pilot departed runway 2 with full fuel and retracted flaps, he was aware of a quartering tailwind he believed to be around 10 knots. The normal procedure was to depart to the north, due to the downward sloping runway. He flew in and out of the airstrip regularly and did not find the current weather conditions unusual. In the past, the pilot calculated the takeoff distance many times, and usually required about 900 feet to rotate. He could not remember if he had performed any takeoff calculations using the weather and airplane conditions immediately prior to the accident. The trees that the airplane collided with were located about 60 feet from the north end of the runway and were approximately 12 feet tall. Due to the slope of the terrain, the treetops were at the runway elevation. The runway was described as being in "poor condition." Density altitude was about 9,800 feet msl. No mechanical problems were noted with the airplane prior to the accident. The pilot stated that future accidents could be prevented by not departing from short airstrips with a tailwind. ## Factual narrative On June 7, 2003, about 1345 mountain standard time, a Cessna 175A, N6902E, collided with trees during takeoff from a private airstrip near Ash Fork, Arizona. The pilot was operating the airplane under the provisions of 14 CFR Part 91. The private pilot, the sole occupant, sustained minor injuries; the airplane sustained substantial damage. The local personal flight originated from the pilot's privately owned airstrip near Ash Fork. Day visual meteorological conditions prevailed, and no flight plan had been filed. The primary wreckage was at 35 degrees 07 minutes north latitude and 112 degree 03 minutes west longitude. The pilot stated that he took off on runway 02 with full fuel, and was aware of a quartering tail wind he believed to be around 10 knots. He always took off to the north because the runway slopes downward from south to north. The winds regularly blow from the southwest to northeast and began gusting in the afternoon, and such gusty wind conditions were noted by a neighbor of the airstrip around the time of the accident. Having flown in and out of the airstrip regularly, the pilot was accustomed to departing under such wind conditions. Although much of his memory from the day of the accident has not returned, it is unclear to the pilot what went wrong. In the past, he had calculated the takeoff distance many times, and usually only needed about 900 feet to get off the ground. He could not remember if he had performed any takeoff calculations using the weather and airplane conditions immediately prior to the accident. The trees that he collided with were located approximately 60 feet from the north end of the runway and were about 12 feet tall. Due to the slope of the terrain, the treetops were at the runway elevation. The pilot did not report any mechanical malfunctions with the airplane prior to the accident, and stated that future accidents could be prevented by not taking off from short airstrips with a tailwind. A deputy sheriff that responded to the accident described the airstrip as having numerous uneven patches of loose dirt and large rocks. A Federal Aviation Administration (FAA) inspector reported that the airstrip was about 1,200 feet long and in poor condition. Furthermore, a 20- to 30-knot quartering tailwind was present at the time of the accident. Density altitude was approximately 9,800 feet mean sea level (msl). The airplane flaps were in the retracted position. The takeoff performance chart in the airplane Owner's Manual does not address the effects of a dirt or soft runway condition, a tail wind, or sloping terrain. In addition, it only addresses takeoffs with the flaps set to 20 degrees. ## Aircraft - Registration: [N6902E](https://openairdocs.org/deregistered/N6902E-2017-07-20), registration cancelled 2017-07-20, S/N 56402, built 1960 (OpenAirDocs) - Reported make and model: Cessna 175A - Registry model: [Cessna 175A](https://openairdocs.org/model/cessna-175a) (registry code 2072504) (OpenAirDocs) - Registry engine: [Continental GO-300 series](https://openairdocs.org/engine/continental-go-300-series) (registry code 17024, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 56402 - Airframe hours: 1994 - Engines: Continental GO-300C 175 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: John T. Vanderbeek - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 8, 2002, 40 hours before - Departed: PVT, Ash Fork, AZ - Airport: PVT, Private, runway 03, 1,300 × 50 ft, dirt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 60; injuries: minor; private; airplane ratings: single-engine land; medical: class 3, expired; last flight review August 31, 2002; seat: left; flight hours: 450 total ## Weather - Conditions: Visual (VMC), Day - Wind: 230° at 12 knots, gusting 19 - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 79 °F, dew point 36 °F - Altimeter: 30.10 inHg - Observed at: FLG, 52 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 20030607010299A](https://openairdocs.org/incident/20030607010299A), Jun 7, 2003: Cessna 175A, Ashfork, AZ, Substantial damage. (-23) On June 7, 2003, john thomas vanderbeek, pilot in command of N6902E (a Cessna 175A) took off from a crude strip located in the vicinity of Ashfork,… 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.