# NTSB ERA15LA019: Piper PA32 301FT, N106C, Winona, MS, October 16, 2014 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: October 16, 2014, 12:15 local (17:15 UTC) - Place: Winona, MS - Coordinates: 33.465, -89.730278 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=33.4650&lon=-89.7303&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff-rejected takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report March 26, 2015 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 90266 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA15LA019 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/90266/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=90266 - Page: https://openairdocs.org/ntsb/ERA15LA019 ## Probable cause A loss of directional control during takeoff for reasons that could not be determined because postaccident examination of the airplane revealed no anomalies. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [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 PA32-301FT, 2 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=7103300), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Piper PA32-301FT, 1 case](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=7103300), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/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 PA32-301FT, 1 case](https://openairdocs.org/ntsb-findings/03022047/cases.md?model=7103300), [All aircraft, 313 cases](https://openairdocs.org/ntsb-findings/03022047/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Takeoff-rejected takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Piper PA32-301FT, 2 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=7103300), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Takeoff-rejected takeoff: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper PA32-301FT, 3 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7103300), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The pilot reported that he had maintenance conducted on the airplane's avionics, which included the replacement of the primary flight display (PFD). After the maintenance was completed, the pilot prepared to return to his home airport. A preflight inspection revealed no anomalies, and the steering system operated normally during taxi. During the takeoff roll, the pilot observed a red "X" indication over the airspeed indicator on the PFD. He "immediately started an emergency shutdown" of the airplane, during which the airplane began to drift left. He applied right rudder with no effect. The airplane subsequently departed the left side of the runway, continued across a grassy area, and impacted the airport perimeter fence, which resulted in substantial damage to the right wing and engine firewall. Postaccident examination of the nose landing gear steering system, rudder controls, and brake system revealed no anomalies, and no evidence of flight control binding or chafing was found. Maintenance facility personnel removed the newly replaced PFD before it could be examined; therefore, it could not be determined if its installation interfered with the airplane's flight control system. According to the Pilot's Operating Handbook, the emergency procedure for a loss of air data on the PFD was to maintain airspeed and altitude by referring to the standby airspeed and altimeter. ## Factual narrative On October 16, 2014, about 1215 central daylight time, a Piper PA32-301FT, N106C, was substantially damaged during an aborted takeoff at Winona-Montgomery County Airport (5A6), Winona, Mississippi. The private pilot was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight, which was operated under the provisions of Title 14 Code of Federal Regulations Part 91. The pilot stated that he flew the airplane to 5A6 so that maintenance could be conducted on the airplane's avionics. After completion of the maintenance, the pilot conducted a preflight inspection, started the engine, and taxied to the runway in preparation for departure. Neither the preflight inspection nor pre-takeoff checks revealed any anomalies with the airplane. During the takeoff roll, the pilot observed a red X indication over the airspeed indicator on the PFD, and "immediately started an emergency shutdown." He stated that the airplane began drifting to the left, and he applied right rudder to correct, but the airplane was unresponsive. The airplane continued off the left side of the runway and into the grass, where it impacted the airport perimeter fence, resulting in substantial damage to the engine firewall and right wing. Review of records provided by the maintenance facility revealed that the airplane's PFD was replaced, and the multifunction display (MFD) software card was upgraded in accordance with a manufacturer's service bulletin. The airplane also received altimeter system and transponder tests, fuel system calibration, and compass calibration, and was subsequently returned to service. The 1153 weather observation at Greenwood-Leflore Airport (GWO), Greenwood, Mississippi, located about 18 nautical miles west of the accident airport, included wind from 270 degrees at 5 knots, 10 miles visibility, temperature 21 degrees C, dew point 7 degrees C, and an altimeter setting of 30.01 inches of mercury. The pilot held a private pilot certificate with a rating for airplane single-engine land. His most recent flight review was conducted in January 2014. His most recent third class Federal Aviation Administration (FAA) medical certificate was issued in August 2013. He reported 190 total hours of flight experience, of which 110 hours were in the accident airplane make and model. The airplane was manufactured in 2005, and registered to the pilot in November 2013. Its most recent annual inspection was completed in May 2014. At the time of the accident, the airplane had accumulated 1,021.8 total hours. According to manufacturer and FAA airworthiness records, the airplane was equipped with a standby airspeed indicator, altimeter, and attitude indicator. The airport was equipped with a single asphalt runway, in a 03/21 configuration. The runway measured 4,000 feet long by 60 feet wide. The airplane was examined at the accident site by an FAA inspector. He observed substantial damage to the right wing and engine firewall. Theairplane was then recovered from the site for further examination; however, before the examination could be conducted, the maintenance facility removed the newly-replaced PFD unit. Follow-up examinations by the FAA inspector established flight control continuity from the rudder pedals to the rudder. There was no evidence of binding or chafing of the flight controls indicative of control interference. No anomalies of the braking system were observed. The airplane was placed on jacks to facilitate inspection of the nose landing gear steering system. The left steering rod remained attached at the steering yoke, and the right steering rod had been disconnected from the steering yoke by recovery personnel. The steering yoke was separated from the nose landing gear strut at impact, and the bolts were sheared. According to the pilot's operating handbook, the emergency procedure for a loss of air data on the PFD was: "Maintain aircraft airspeed and altitude by referring to the standby airspeed and altimeter. If time and conditions permit: PFD Circuit Breaker……..PULL and RESET If air data is still invalid: Refer to standby airspeed indicator and altimeter. Land as soon as practical." ## Aircraft - Registration: [N106C](https://openairdocs.org/deregistered/N106C-2023-01-14), registration cancelled 2023-01-14, S/N 3232039 (OpenAirDocs) - Reported make and model: PIPER PA32 301FT (301FT) - Registry model: [Piper PA32-301FT](https://openairdocs.org/model/piper-pa32-301ft) (registry code 7103300) (OpenAirDocs) - Registry engine: [Lycoming IO-540-K1G5D](https://openairdocs.org/engine/lycoming-io-540-k1g5d) (registry code 41598, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 3232039 - Year built: 2005 - Airframe hours: 1021.8 - Engines: LYCOMING IO-540-K1G5D 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Knight Brothers Inc - Registered owner: Knight Brothers Inc - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 9, 2014 - Departed: 5A6, Winona, MS - Destination: CRX, Corinth, MS - Airport: 5A6, Winona-Montgomery County, runway 21, 4,000 × 60 ft, asphalt - Equipment: Onboard weather, Handheld GPS, Electronic flight bag or handheld device, Auto-pilot, Stall warning system, Satellite tracking device ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 46; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; seat: left; restraint: 3-point; flight hours: 190 total, 110 in this make and model, 114 as pilot in command ## Weather - Conditions: Visual (VMC), Day - Wind: 270° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 70 °F, dew point 45 °F - Altimeter: 30.01 inHg - Observed at: KGWO, 18 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 20141016020069A](https://openairdocs.org/incident/20141016020069A), Oct 16, 2014: Piper PA32-301FT, Winona, MS, Substantial damage. During takeoff pilot aborted after MFD displayed red x. pilot run off left side of runway striking fence. ## Other investigations on N106C (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 CEN10CA375](https://openairdocs.org/ntsb/CEN10CA375), Jul 6, 2010: Piper PA32 (N106C), Albuquerque, NM, substantial damage. Probable cause: The pilot's failure to maintain directional control of the airplane during takeoff. ## Docket (7 files) The files NTSB released with the investigation on March 13, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=90266. 7.6 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40423384&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Memorandum for Record – FAA Inspector (item 2, .PDF, 108 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40423385&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20%E2%80%93%20FAA%20Inspector-Master.PDF - Memorandum for Record - Pilot (item 3, .PDF, 110 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40423386&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20-%20Pilot-Master.PDF - Photo 1 – Airplane from right (Courtesy of FAA) (item 4, .PDF, 3.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40423387&FileExtension=.PDF&FileName=Photo%201%20%E2%80%93%20Airplane%20from%20right%20(Courtesy%20of%20FAA)-Master.PDF - Photo 2 – Right wing damage (Courtesy of FAA) (item 5, .PDF, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40423388&FileExtension=.PDF&FileName=Photo%202%20%E2%80%93%20Right%20wing%20damage%20(Courtesy%20of%20FAA)-Master.PDF - Maintenance Log Entry (item 6, .PDF, 82 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40423389&FileExtension=.PDF&FileName=Maintenance%20Log%20Entry-Redacted.PDF - Pilots Operating Handbook Excerpt (item 7, .PDF, 75 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40423390&FileExtension=.PDF&FileName=Pilots%20Operating%20Handbook%20Excerpt-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.