# NTSB WPR13LA034: Jeffair Barracuda, N19GS, Payson, AZ, October 27, 2012 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: October 27, 2012, 09:25 local (16:25 UTC) - Place: Payson, AZ - Coordinates: 34.256668, -111.339164 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=34.2567&lon=-111.3392&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Landing gear collapse](https://openairdocs.org/ntsb-events/094) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report May 13, 2015 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: FAA FSDO - NTSB case key (mKey): 85527 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR13LA034 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/85527/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=85527 - Page: https://openairdocs.org/ntsb/WPR13LA034 ## Probable cause The failure of the landing gear to remain extended during the landing roll for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Landing gear system](https://openairdocs.org/ntsb-findings/01023200): Aircraft › Aircraft systems · Failure - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause) ## Analysis The pilot had purchased the experimental, amateur-built airplane from its designer/builder about 32 years after the airplane had been issued its airworthiness certificate. The airplane was the prototype and first-constructed edition of that model. Two years after the purchase, the airplane was damaged on landing due to a problem with the nose landing gear. The pilot subsequently determined that certain nose gear components were of insufficient strength and he had them "repaired and reinforced." About 3 years later, after the airplane had accumulated an undetermined amount of time or cycles since the repairs, the pilot departed on the accident flight, which was a personal cross-country flight, with a passenger. The pilot observed a landing gear annunciation light sequencing abnormality during the gear retraction. The airplane did not experience any additional problems until the pilot selected the landing gear to the extended position and observed that the light indicating that the nose landing gear was down and locked did not illuminate. He conducted a low flyby of the airport, and a ground observer radioed that the nose gear appeared to be fully extended. However, upon landing, first the nose gear and then the two main gear retracted. The airplane sustained substantial damage to the wings. Postaccident examination of the landing gear system did not reveal any anomalies that would have precluded normal operation. ## Factual narrative FAA records indicated that the airplane the first model of its type, and was built by its principal designer, G.L. Siers. The airplane was first issued its airworthiness certificate in 1975. The design was a single-engine, low-wing monoplane constructed primarily of wood. It was equipped with hydraulically-operated tricycle-configuration landing gear, and a Lycoming IO-540 series engine. The accident pilot was the second owner of the airplane; he purchased it from the designer/builder in February 2007. According to the pilot, in July 2007, he "had the engine and prop rebuilt as they were both past TBO." In 2009 the airplane was damaged on landing due to a problem with the nose landing gear. The nose gear contacted a gear door while retracting; the pilot subsequently determined that the components intended to align the nose gear for retraction were of insufficient strength and had deformed, preventing normal nose gear operation. The pilot reported that the components "were repaired and reinforced." The airplane's most recent annual condition inspection was completed on October 27, 2011, exactly 1 year prior to the accident. Maintenance records indicated that at that time, the airplane had accumulated a total time (TT) in service of about 516 hours. The pilot reported that the airplane had flown "about 8 or 9 times" since that inspection, and that "there were no problems." PAN was equipped with a single paved runway designated 06-24. The runway measured 5,504 by 75 feet, and field elevation was reported as 5,157 feet. PAN was not equipped with an operating air traffic control tower. On October 27, 2012, about 0925 mountain standard time, an experimental amateur-built JeffAir Barracuda, N19GS, was substantially damaged when all three landing gear collapsed after touchdown on runway 6 at Payson airport (PAN), Payson, Arizona. Neither the pilot/owner nor his passenger was injured. The personal flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed, and no FAA flight plan was filed for the flight. According to the pilot, the airplane landing gear system was equipped with three green annunciation lights, which illuminate when the landing gear is fully extended for landing, and three amber annunciation lights, which illuminate when the landing gear is fully retracted. On departure from Ernest A. Love field (PRC), Prescott, Arizona, for PAN, the pilot noticed that the nose landing gear (NLG) amber light illuminated about 5 to 8 seconds after the two main landing gear (MLG) lights; normally all three illuminate approximately simultaneously. The pilot was uncertain whether there really was a problem, and the airplane operated normally for most of the remainder of the flight. In the traffic pattern at PAN, after the pilot selected the landing gear to the extended position, he observed that the two green MLG lights illuminated, but the green NLG light did not. He conducted a lowflyby of the airport, and a ground observer radioed that the NLG appeared to be fully extended. The pilot then conducted a normal landing, but the NLG retracted when the pilot lowered the nose of the airplane. Very shortly thereafter, the two MLG then retracted, and the airplane slid to a stop on the runway. Portions of both MLG assemblies pushed up through the upper wing skins after the unintentional retraction. The airplane was partially disassembled, and transported to the pilot's hangar at PRC for further examination. The PAN 1635 automated weather observation included winds from 130 degrees at 8 knots, visibility 10 miles, clear skies, temperature 13 degrees C, dew point -8 degrees C, and an altimeter setting of 30.18 inches of mercury. According to Federal Aviation Administration (FAA) information, the pilot held a private pilot certificate with airplane single- and multi-engine ratings. His most recent FAA third-class medical certificate was issued in November 2011. According to the pilot, he had a total flight experience of about 2,500 hours, including about 40 hours in the accident airplane make and model. His most recent flight review was accomplished in September 2012. Several days after the accident, and FAA inspector examined the wreckage in the pilot's hangar. The inspector reported that "both main gear had punctured through the tops of both wings," the landing gear doors were damaged, and that the "propeller was destroyed." The inspector did not note any obvious underlying reasons for the initial failure of the NLG. According to the pilot, the uncommanded retraction of the MLG was an expected result of the NLG failure, due to the system architecture. ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-landing roll: Landing gear collapse](https://openairdocs.org/ntsb-events/094) (defining event) ## Aircraft - Registration: [N19GS](https://openairdocs.org/deregistered/N19GS-2017-10-20), registration cancelled 2017-10-20, S/N 001, built 1975 (OpenAirDocs) - Reported make and model: JEFFAIR BARRACUDA (NO SERIES) - Registry model: [Jeffair BARRACUDA](https://openairdocs.org/model/jeffair-barracuda) (registry code 05629BP) (OpenAirDocs) - Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: 0001 - Year built: 1975 - Airframe hours: 520 - Engines: Lycoming IO-540 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Condition, October 27, 2011, 25 hours before - Departed: PRC, Prescott, AZ - Destination: PAN, Payson, AZ - Airport: PAN, Payson, runway 06, 5,500 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 66; injuries: none; private; airplane ratings: multi-engine land, single-engine land; medical: class 3, with waivers/limitations; seat: left; restraint: 3-point; flight hours: 2,500 total, 40 in this make and model, 2,410 as pilot in command, 5 in the last 90 days, 3 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 130° at 8 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 55 °F, dew point 18 °F - Altimeter: 30.18 inHg - Observed at: PAN ## 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 20121027024009A](https://openairdocs.org/incident/20121027024009A), Oct 27, 2012: The Jeffair Corp. BARRACUDA, Payson, AZ, Substantial damage. In preparation for landing at Payson Airport, AZ (pan), pilot had an unsafe nose gear indication. He made a low approach and was advised by another pilot on… ## Docket (7 files) The files NTSB released with the investigation on April 8, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=85527. 7.7 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40424908&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Record of Conversation - Pilot (item 2, .PDF, 111 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40424909&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Pilot-Master.PDF - Record of Communication – Pilot (item 3, .PDF, 60 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40424910&FileExtension=.PDF&FileName=Record%20of%20Communication%20%E2%80%93%20Pilot%20-Redacted.PDF - Record of Communication re POH (item 4, .PDF, 303 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40424911&FileExtension=.PDF&FileName=Record%20of%20Communication%20re%20POH-Master.PDF - Record of Communication – FAA Inspector (item 5, .PDF, 33 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40424915&FileExtension=.PDF&FileName=Record%20of%20Communication%20%E2%80%93%20FAA%20Inspector-Redacted.PDF - Maintenance Records Excerpts (item 6, .PDF, 4.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40424920&FileExtension=.PDF&FileName=Maintenance%20Records%20Excerpts-Redacted.PDF - METARs (item 7, .PDF, 230 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40424921&FileExtension=.PDF&FileName=METARs-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date; 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.