# NTSB WPR12CA083: Piper PA-28-181, N4297S, Santa Barbara, CA, January 26, 2012 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: January 26, 2012, 14:10 local (22:10 UTC) - Place: Santa Barbara, CA - Coordinates: 34.426109, -119.841392 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=34.4261&lon=-119.8414&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report April 2, 2012 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 82757 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR12CA083 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/82757/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=82757 - Page: https://openairdocs.org/ntsb/WPR12CA083 ## Probable cause The pilot did not maintain directional control during takeoff. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-28-181, 53 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7102807), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Object/animal/substance: sign/marker](https://openairdocs.org/ntsb-findings/03022015): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Piper PA-28-181, 8 cases](https://openairdocs.org/ntsb-findings/03022015/cases.md?model=7102807), [All aircraft, 214 cases](https://openairdocs.org/ntsb-findings/03022015/cases.md) - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-28-181, 37 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=7102807), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Piper PA-28-181, 33 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=7102807), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Takeoff: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper PA-28-181, 35 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7102807), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Takeoff: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-28-181, 70 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7102807), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot reported that, after aligning the airplane with the runway centerline and adding full power for takeoff, the airplane accelerated and then began to veer left. The pilot immediately added right rudder to correct for the deviation, but the airplane did not respond to the control input. He then reduced power to abort the takeoff, but, seeing runway signs in his path, he added full power again in an attempt to get airborne to avoid colliding with the signs. After becoming airborne, the airplane impacted a sign with its right main landing gear and right stabilator, which resulted in substantial damage to the airplane. Neither the pilot nor a Federal Aviation Administration inspector, who examined the airplane after the accident, reported any pre-impact mechanical malfunctions or anomalies. ## Factual narrative The pilot reported that after aligning the airplane with the runway centerline and adding full power, the airplane accelerated and then began to veer to the left. The pilot further said that he immediately added right rudder to correct for the deviation but the airplane did not respond to the control input. The pilot stated that he then elected to abort the takeoff, but seeing runway signs in his path he added full power again in an attempt to get airborne to avoid colliding with the signs. After becoming airborne the airplane impacted an airport sign with its right main landing gear and right stabilator, which resulted in substantial damage to the airplane. Neither the pilot nor a Federal Aviation Administration inspector, who examined the airplane after the accident, reported any pre-impact mechanical malfunctions or anomalies. The pilot added that he was using runway 25 at the time of the accident, that the wind was 250 degrees at 8 knots, and that there were no gust reported. ## Aircraft - Registration: [N4297S](https://openairdocs.org/deregistered/N4297S-2012-03-28), registration cancelled 2012-03-28, S/N 28-8390045, built 1983 (OpenAirDocs) - Reported make and model: PIPER PA-28-181 - Registry model: [Piper PA-28-181](https://openairdocs.org/model/piper-pa-28-181) (registry code 7102807) (OpenAirDocs) - Registry engine: [Lycoming O&VO-360 series](https://openairdocs.org/engine/lycoming-o-vo-360-series) (registry code 41514, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28-8390045 - Airframe hours: 11476 - Engines: LYCOMING O&VO-360 SER 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Marco A. Perez - Registered owner: Uaa International Inc - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: Annual, December 9, 2011, 82 hours before - Departed: SBA, Santa Barbara, CA - Destination: EMT, El Monte, CA - Airport: SBA, Santa Barbara Municipal, runway 25, 6,052 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 40; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review August 19, 2010; seat: left; flight hours: 317 total, 272 in this make and model, 265 as pilot in command, 7 in the last 90 days, 2 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 250° at 8 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 79 °F, dew point 50 °F - Altimeter: 30.00 inHg - Observed at: SBA ## 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 20120126001659A](https://openairdocs.org/incident/20120126001659A), Jan 26, 2012: Piper PA-28-181, Santa Barbara, CA, Substantial damage. 1/26/2012 @ 1408 Hours: aircraft N4297S, Piper PA-28 lost control on takeoff roll rwy 25 at Santa Barbara airport (sba), departed left side of runway just… ## Docket (4 files) The files NTSB released with the investigation on February 21, 2012, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=82757. 2.8 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 2.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363101&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Weather Data (item 2, .PDF, 46 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363102&FileExtension=.PDF&FileName=Weather%20Data-Master.PDF - FAA Inspector's Report (item 3, .PDF, 76 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363103&FileExtension=.PDF&FileName=FAA%20Inspector%27s%20Report-Redacted.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 4, .PDF, 146 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363105&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Redacted.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.