# NTSB WPR10CA035: Piper PA-28-140, N1721T, Angwin, CA, October 30, 2009 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: October 29, 2009, 19:31 local (Oct 30, 2009, 02:31 UTC) - Place: Angwin, CA - Coordinates: 38.580001, -122.435279 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.5800&lon=-122.4353&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff: Wrong surface or wrong airport](https://openairdocs.org/ntsb-events/284) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report March 3, 2010 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 74976 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10CA035 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/74976/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=74976 - Page: https://openairdocs.org/ntsb/WPR10CA035 ## Probable cause The pilot's failure to properly identify the runway surface for takeoff and his subsequent failure to abort the takeoff when he realized he was not on the runway. Contributing to the accident was the pilot’s failure to select the appropriate radio frequency to activate the runway lights. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-28-140, 15 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=7102802), [All aircraft, 1,387 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) - [Action: lack of action](https://openairdocs.org/ntsb-findings/02041030): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-28-140, 8 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md?model=7102802), [All aircraft, 792 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md) - [Object/animal/substance: fence/fence post](https://openairdocs.org/ntsb-findings/03022047): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Piper PA-28-140, 6 cases](https://openairdocs.org/ntsb-findings/03022047/cases.md?model=7102802), [All aircraft, 315 cases](https://openairdocs.org/ntsb-findings/03022047/cases.md) - [Airport facilities/design](https://openairdocs.org/ntsb-findings/03017000): Environmental issues › Operating environment · Awareness of condition (probable cause); cases with it: [Piper PA-28-140, 1 case](https://openairdocs.org/ntsb-findings/03017000/cases.md?model=7102802), [All aircraft, 52 cases](https://openairdocs.org/ntsb-findings/03017000/cases.md) - [Use of equip/info: use of equip/system](https://openairdocs.org/ntsb-findings/02063015): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-28-140, 16 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md?model=7102802), [All aircraft, 1,397 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md) - [Airport facilities/design: runway lighting](https://openairdocs.org/ntsb-findings/03017015): Environmental issues › Operating environment · Use of related info; cases with it: [Piper PA-28-140, 1 case](https://openairdocs.org/ntsb-findings/03017015/cases.md?model=7102802), [All aircraft, 18 cases](https://openairdocs.org/ntsb-findings/03017015/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Taxi-into takeoff position: Miscellaneous/other](https://openairdocs.org/ntsb-events/900); cases with it: [Piper PA-28-140, 14 cases](https://openairdocs.org/ntsb-events/900/sequence.md?model=7102802), [All aircraft, 1,558 cases](https://openairdocs.org/ntsb-events/900/sequence.md) - [Takeoff: Wrong surface or wrong airport](https://openairdocs.org/ntsb-events/284) (defining event); cases with it: [Piper PA-28-140, 2 cases](https://openairdocs.org/ntsb-events/284/sequence.md?model=7102802), [All aircraft, 58 cases](https://openairdocs.org/ntsb-events/284/sequence.md) ## Analysis The pilot reported that he positioned the airplane for the night takeoff approximately 1/4-mile from the start of Runway 34. He attempted to activate the runway lights using the radio; however, he had selected an incorrect frequency. He used his landing light and positioned the airplane where he believed the runway was located. As the airplane approached 65 miles per hour, he saw grass and dirt. His passenger requested that he stop the airplane; however, the pilot felt that his options were better if he continued the takeoff. The passenger continued to request that he stop the airplane and the groundspeed was about 80 miles per hour. The pilot further reported that the passenger’s seat was positioned further back than his and that the passenger was pulling the yoke aft and her feet were pushing on the rudder pedals. The airplane then impacted a fence. Later activation of the airport lighting system revealed no operational anomalies when the correct radio frequency was selected. ## Factual narrative The pilot reported that he positioned the airplane for the night time takeoff approximately 1/4-mile from the start of runway 34. He attempted to activate the runway lights using the radio; however, he had selected an incorrect frequency. He used his landing light and positioned the airplane where he believed the runway was located. As the airplane approached 65 miles per hour, he saw grass and dirt. His passenger requested that he stop the airplane but in his opinion, he felt his options were better if he continued the takeoff. The passenger continued to request that he stop the airplane and the groundspeed was about 80 miles per hour. The pilot further reported that the passenger’s seat was positioned farther back than his and that the passenger was pulling the yoke aft and her feet were pushing on the rudder pedals. The airplane then impacted a fence. Later activation of the airport lighting system revealed no operational anomalies when the correct radio frequency was selected. ## Aircraft - Registration: [N1721T](https://openairdocs.org/deregistered/N1721T-2014-09-10), registration cancelled 2014-09-10, S/N 28-7125034, built 1970 (OpenAirDocs) - Reported make and model: PIPER PA-28-140 - Registry model: [Piper PA-28-140](https://openairdocs.org/model/piper-pa-28-140) (registry code 7102802) (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-7125034 - Airframe hours: 2300 - Engines: LYCOMING O-320 SERIES 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Lee Mize - Registered owner: Lee Mize - Airworthiness certificate: Standard, Normal - Last inspection: Annual, December 1, 2008 - Departed: 2O3, Angwin, CA - Destination: AUN, Auburn, CA - Airport: 2O3, Angwin-Parrett Field Airport, runway 34, 3,217 × 50 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 75; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; seat: left; flight hours: 3,800 total, 1,600 in this make and model ## Weather - Conditions: Visual (VMC), Night - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 57 °F, dew point 48 °F - Altimeter: 30.07 inHg - Observed at: STS, 19 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 20091029021689A](https://openairdocs.org/incident/20091029021689A), Oct 29, 2009: Piper PA28140, Angwin, CA, Substantial damage. Aircraft N1721T attempted a take off from the Angwin CA airport (2O3) at approximately 1930 hrs. The pilot stated that he tuned in the wrong radio frequency… ## Other investigations on N1721T (1) 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 SEA73FYI02](https://openairdocs.org/ntsb/SEA73FYI02), Aug 3, 1972: Piper PA-28 (N1721T), Roseburg, OR, substantial damage ## Docket (4 files) The files NTSB released with the investigation on November 17, 2009, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=74976. 966 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 640 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40321428&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - FAA Takeoff Profile (item 2, .PDF, 172 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40321144&FileExtension=.PDF&FileName=FAA%20Takeoff%20Profile-Master.PDF - Record of Conversation Pilot (item 3, .PDF, 13 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40321146&FileExtension=.PDF&FileName=Record%20of%20Conversation%20Pilot-Master.PDF - Photo 1. Airplane (Provided by FAA) (item 4, .PDF, 142 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40321145&FileExtension=.PDF&FileName=Photo%201.%20Airplane%20(Provided%20by%20FAA)-Master.PDF 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.