# NTSB LAX95LA278: Fox Peregrine PJ-2, N62PJ, Minden, NV, August 4, 1995 - Type: NTSB accident investigation - Classification: Accident · Fatal · Limited investigation · Final report - Date: August 4, 1995, 09:26 local (16:26 UTC) - Place: Minden, NV - Coordinates: 39.009574, -119.74942 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.0096&lon=-119.7494&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: Fatal - Injuries: 1 fatal - Status: Completed, report April 1, 1996 - Report: Approved by Office Director - NTSB case key (mKey): 29172 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX95LA278 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/29172/pdf - Page: https://openairdocs.org/ntsb/LAX95LA278 ## Probable cause a failure of the wing flap control system due to inadequate design, which led to an asymmetrical flap deployment during a critical flight condition and in-flight loss of control. A related factor was the lack of a split-flaps warning system. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Airframe/component/system failure/malfunction, go-around (vfr) - flt control syst,wing flap control cable/rod - sheared (cause) - acft/equip,inadequate design, production/design personnel (cause) - Loss of control - in flight, go-around (vfr) - warning system(other) - not installed (contributing factor) - flight control,flap - asymmetrical (cause) - aircraft control - not possible, pilot in command - In flight collision with terrain/water, descent - uncontrolled ## Analysis THE AIRCRAFT WAS ON A DEVELOPMENTAL FLIGHT TEST PROGRAM. THE PILOT REPORTED A SPLIT FLAP SITUATION DURING THE GO-AROUND. WITNESSES OBSERVED THE AIRPLANE TURN ONTO A LEFT CROSSWIND, THEN BEGIN A RIGHT ROLL TO GROUND IMPACT. A PIN IN THE LEFT FLAP DRIVE WAS FOUND SHEARED. THE PIN WAS EXAMINED AND FOUND TO MEET THE MANUFACTURER'S MATERIAL SPECIFICATIONS. IT WAS DETERMINED THE PIN HAD FAILED DUE TO OVERLOAD SHEAR FORCES WHILE TORSIONAL AND AXIAL LOADS WERE APPLIED. THE FLAPS ARE DRIVEN BY A SINGLE ELECTRIC MOTOR WHICH ROTATES TWO INDEPENDENT FLEXIBLE DRIVE SHAFTS THAT ACTUATE THE RIGHT AND LEFT FLAP PANELS. THE SHEARED PIN BROKE THE CONTINUITY OF THE LEFT FLAP PANEL DRIVE STOPPING THE FLAP PANEL WHILE THE RIGHT FLAP PANEL WOULD CONTINUE TO EXTEND OR RETRACT. THERE WAS NO SYSTEM OR MECHANISM IN THE AIRPLANE THAT DETECTED AN ASYMMETRICAL FLAP CONDITION. TESTS OF THE FLAP SYSTEM REVEALED THE ELECTRICAL MOTOR IN THE FLAP SYSTEM WAS CAPABLE OF SHEARING THE PIN BEFORE A CIRCUIT BREAKER WOULD INTERRUPT ELECTRICAL POWER TO THE MOTOR. ## Factual narrative On August 4, 1995, at 0926 hours Pacific daylight time, a Fox Aircraft Corp., Peregrine PJ-2, N62PJ, collided with terrain after an in-flight loss of control during a go-around from runway 34 at the Douglas County Airport, Minden, Nevada. The airplane was being operated as a developmental test flight under 14 CFR Part 91 when the accident occurred. The airplane was destroyed. The commercial pilot was fatally injured. Visual meteorological conditions prevailed at the time. The pilot reported a split flap situation by radio to his company during the go-around. Witnesses reported seeing the airplane turn left to the crosswind leg of the traffic pattern and then roll to the right. The airplane pitch attitude was observed decreasing and the airplane continued to roll until colliding with terrain. Examination of the flap system revealed a pin sheared on the left-hand drive shaft. The flaps are driven by a single electric motor which rotates two independent flexible drive shafts that actuate the right and left flap panels. Examination of system drawings and descriptions revealed that a sheared pin would break the continuity of the respective flap panel drive, stopping the flap panel while the other flap panel would continue to extend or retract. There was no system or mechanism in the airplane that detected an asymmetrical flap condition. The pin was submitted to metallurgical lab for analysis. According to the metallurgist, the pin conformed to the material specifications of the pin manufacturer and had failed due to overload shear forces on an approximate 45-degree plane. The metallurgist indicated the orientation of the direction of shear would indicate that a combination of torsional and axial loads were being applied at the time of the shear failure. The airplane manufacturer conducted tests of the flap system. The manufacturer determined the electrical motor in the flap system was capable of shearing the pin before a circuit breaker would interrupt electrical power to the flap motor. ## Aircraft - Registration: [N62PJ](https://openairdocs.org/deregistered/N62PJ-1997-03-28), registration cancelled 1997-03-28, S/N 001 (OpenAirDocs) - Reported make and model: Fox Aircraft Corp. PEREGRINE PJ-2 (PEREGRINE) - Registry model: [Fox PJ-2](https://openairdocs.org/model/fox-pj-2) (registry code 05630B3) (OpenAirDocs) - Category: Airplane - Serial number: 001 - Airframe hours: 34 - Engines: GE J85-17A 2950 lbs thrust turbo jet - Damage: Destroyed - Flight: Part 91 - Registered owner: Fox Aircraft Corp. - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Continuous airworthiness, July 30, 1995, 24 hours before - Departed: MEV - Airport: MEV, Douglas County, runway 34, 7,395 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 53; military, commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; seat: front; toxicology performed; flight hours: 5,922 total, 14 in this make and model, 5,922 as pilot in command, 43 in the last 90 days, 18 in the last 30 days, 3 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 180° at 5 knots - Visibility: 40 statute miles - Lowest ceiling: none - Temperature: 75 °F, dew point 45 °F - Altimeter: 30.00 inHg - Observed at: RNO, 28 nm away 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.