# NTSB LAX97LA312: Cessna T210J, N2280R, Avra Valley, AZ, August 29, 1997 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: August 28, 1997, 21:30 local (Aug 29, 1997, 04:30 UTC) - Place: Avra Valley, AZ - Coordinates: 32.199348, -110.950691 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=32.1993&lon=-110.9507&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report November 10, 1998 - Report: Approved by Office Director - NTSB case key (mKey): 29893 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX97LA312 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/29893/pdf - Page: https://openairdocs.org/ntsb/LAX97LA312 ## Probable cause The pilot became lost/disoriented during his taxiing into the ramp area. Factors in the accident were the lack of taxiway lights, the pilot's lack of familiarity with the layout of the airport, and the airport operator's failure to either identify the drainage ditch in the airport/facility guide or to mark the ditch with signs. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Airframe/component/system failure/malfunction, descent - electrical system - failure,total - reason for occurrence undetermined - On ground/water encounter with terrain/water, taxi - from landing - light condition - night - airport facilities,taxiway lighting - not installed (contributing factor) - terrain condition - ditch (contributing factor) - unsafe/hazardous condition warning - not deployed, airport personnel (contributing factor) - became lost/disoriented, pilot in command (cause) - lack of familiarity with geographic area, pilot in command (contributing factor) - taxispeed - excessive, pilot in command (contributing factor) ## Analysis The pilot stated that he had a total electrical failure while en route to his destination. He decided to land at an uncontrolled airport that had a lighted runway instead of his usual destination. The landing was made uneventfully, but during the taxi to the ramp area the pilot misjudged his position on the unlighted taxiway and ran off the taxiway into a large drainage ditch. The ditch was not marked, nor was it mentioned in the airport remarks in the Airport Facility Directory or in the NOTAMS. The ditch was estimated to have a depth of approximately 3-4 feet below the surface of the runway, with an estimated slope in excess of 35 degrees. A postaccident examination of the electrical system did not identify the problem other than it was noted that one cell of the battery only charged to 50 percent. Examination of the taxiway found skid marks just prior to the aircraft departing the paved surface of the taxiway. The pilot told investigators that he was unfamiliar with the layout of this airport. ## Factual narrative On August 28, 1997, at 2130 hours mountain standard time, a Cessna T210J, N2280R, collided with a ditch after landing at Avra Valley Airport, Tucson, Arizona. The aircraft sustained substantial damage, and the private pilot was not injured. The aircraft was operated by the pilot as a personal flight under 14 CFR Part 91 when the accident occurred. The flight originated in Sierra Vista, Arizona, at 2100. Visual meteorological conditions prevailed at the time. The pilot reported that the aircraft sustained a complete electrical system failure while en route to La Cholla Airpark, his intended destination. He was unable to activate the airport lighting or use the aircraft taxi/landing lights. He decided to land at Avra Valley Airport which had a lighted runway. Following the landing on runway 30, he turned off the runway on what he believed was a taxiway that led to the terminal. The attached airport diagram annotates the taxiway in question as taxiway "B". The pilot claimed that the floodlights on top of the "T" hangers were in his eyes and he could not see where he was going. Shortly after he turned toward the area he thought was the ramp/terminal area, the aircraft encountered the drainage ditch. The pilot told the FAA Airworthiness Inspector that he was unfamiliar with the airport layout. The Safety Board examined the drainage ditch and adjoining taxiway and determined that the aircraft was traveling in a direction opposite the path that would have taken it to the ramp area when the accident occurred. Additionally, skid marks were left on the taxiway at a point just before the tire left the paved area. The taxiway does not have any lights. A postaccident examination of the electrical system did not identify the source of the electrical problem. The alternator and voltage regulator were tested satisfactorily. The wiring system was tested, with no faults located. The only discrepancy noted was that one cell of the battery only charged to 50 percent of the load. The pilot told the Safety Board that the aircraft departed the taxiway about 20 feet from the intersection of the two taxiways. The airport manager said he was going to take steps to redirect the floodlight's beam to light the terminal area in a way that would be less conducive to restricting night vision. The Safety Board examined the Southwest U.S. Airport/Facility Directory to see if there was any mention of the drainage ditch in the remarks section listed under Avra Valley Airport. The Safety Board was unable to locate any descriptive data concerning the ditch from the NOTAM files when Prescott FSS was contacted. ## Aircraft - Registration: [N2280R](https://openairdocs.org/aircraft/N2280R), registered now, S/N T210-0430 (OpenAirDocs) - Reported make and model: Cessna T210J - Registry model: [Cessna T210J](https://openairdocs.org/model/cessna-t210j) (registry code 2073440) (OpenAirDocs) - Registry engine: [Continental IO-520 series](https://openairdocs.org/engine/continental-io-520-series) (registry code 17032, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 210-0430 - Airframe hours: 5412 - Engines: Continental TSIO-520-H 285 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Kenneth J. Smith - Airworthiness certificate: Standard, Normal - Last inspection: Annual, January 4, 1997, 18 hours before - Departed: FHU, SIERRA VISTA, AZ - Destination: LA CHOLLA, AZ - Airport: E14, Avra Valley, runway 30, 6,901 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 65; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, valid medical--w/ waivers/lim; seat: left; flight hours: 1,317 total, 606 in this make and model, 1,259 as pilot in command, 7 in the last 90 days, 7 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Night/dark - Wind: 260° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 90 °F, dew point 61 °F - Altimeter: 29.00 inHg - Observed at: TUS, 43 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 19970828026859A](https://openairdocs.org/incident/19970828026859A), Aug 28, 1997: Cessna T210J, Tucson, AZ, Substantial damage. (.4)The pilot stated that he had a total electrical failure while en route to his destination. He decided to land at an uncontrolled airport that had a lighted… ## Other investigations on N2280R (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 DEN78FTE10](https://openairdocs.org/ntsb/DEN78FTE10), Nov 4, 1977: Cessna T210J (N2280R), Glenwood Sprgs, CO, substantial damage - [NTSB DEN73DTC25](https://openairdocs.org/ntsb/DEN73DTC25), May 9, 1973: Cessna T210J (N2280R), Riverton, WY, 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.