# NTSB WPR10LA374: Lancair 320, N360N, Spokane, WA, July 27, 2010 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: July 27, 2010, 10:00 local (17:00 UTC) - Place: Spokane, WA - Coordinates: 47.67889, -117.331947 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=47.6789&lon=-117.3319&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Flight control sys malf/fail](https://openairdocs.org/ntsb-events/333) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report December 13, 2011 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 76795 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10LA374 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/76795/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=76795 - Page: https://openairdocs.org/ntsb/WPR10LA374 ## Probable cause Loss of airplane control due to the asymmetric flap condition. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Flight control system: tE flap control system](https://openairdocs.org/ntsb-findings/01022750): Aircraft › Aircraft systems · Malfunction (probable cause); cases with it: [Smith Martin P LANCAIR 320, 1 case](https://openairdocs.org/ntsb-findings/01022750/cases.md?model=05606AY), [All aircraft, 74 cases](https://openairdocs.org/ntsb-findings/01022750/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Smith Martin P LANCAIR 320, 1 case](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=05606AY), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: lateral/bank control](https://openairdocs.org/ntsb-findings/01062023): Aircraft › Aircraft oper/perf/capability · Attain/maintain not possible (probable cause); cases with it: [Smith Martin P LANCAIR 320, 1 case](https://openairdocs.org/ntsb-findings/01062023/cases.md?model=05606AY), [All aircraft, 390 cases](https://openairdocs.org/ntsb-findings/01062023/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Initial climb: Flight control sys malf/fail](https://openairdocs.org/ntsb-events/333) (defining event); cases with it: [Smith Martin P LANCAIR 320, 1 case](https://openairdocs.org/ntsb-events/333/sequence.md?model=05606AY), [All aircraft, 410 cases](https://openairdocs.org/ntsb-events/333/sequence.md) - [Approach-VFR pattern final: Loss of control in flight](https://openairdocs.org/ntsb-events/240); cases with it: [Smith Martin P LANCAIR 320, 1 case](https://openairdocs.org/ntsb-events/240/sequence.md?model=05606AY), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Smith Martin P LANCAIR 320, 1 case](https://openairdocs.org/ntsb-events/470/sequence.md?model=05606AY), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot reported that, after initiating a go-around and during a climbing left turn to re-enter the traffic pattern, his attempt to roll out of the turn was unsuccessful. The bank angle continued to near 90 degrees before he was able to maneuver the airplane close to the runway. The airplane ultimately stalled and collided with the runway surface. A postaccident examination of the airplane revealed an asymmetric flap condition. Shortly after the accident, the airplane kit manufacturer issued a Service Bulletin that addressed the asymmetric flap problem. The bulletin advised operators to inspect for adequate clearance and ensure that sufficient stiffness is established such that when fully deployed, the flap’s leading edge will not have a tendency to flex upward and snag the trailing edge of the wing. The condition could jam the flap and subsequently preclude its retraction. ## Factual narrative On July 27, 2010, about 1000 Pacific daylight time, an experimental Lancair 320, N360N, was substantially damaged after impacting terrain following a loss of control while maneuvering on final approach to land at Felts Field (SFF), Spokane, Washington. The commercial pilot, the sole occupant, sustained minor injuries. Visual meteorological conditions prevailed for the local flight, which was operated in accordance with Title 14 Code of Federal Regulations Part 91, and a flight plan was not filed. The flight had departed SFF at 0904. In a report submitted to the National Transportation Safety Board investigator-in-charge (IIC), the pilot reported that after turning onto final approach to land, he observed another airplane just ahead landing on the same runway. The pilot further reported that he commenced a go-around as instructed by the air traffic control tower controller, during which he raised the landing gear, but left the flaps at 10 degrees. The pilot stated that after establishing himself on downwind he put the gear handle down, but at about the same time he experienced a complete electrical failure. The pilot added that with no gear down indication he continued the pattern, and that the airplane responded normally to power and flight controls. The pilot revealed that he descended to his normal touchdown height, and when the wheels did not touch the runway as expected he initiated a go-around in a left climbing turn back to pattern altitude where he tried a manual gear extension. The pilot reported that at this time the airplane would not roll out of the left turn, but in fact with full right stick and rudder, the airplane continued to a near 90-degree left bank. The pilot stated that he reduced power and lowered the nose enough to maintain airspeed just above a stall, then banked enough to get over to runway heading. The pilot added that when he was about 4 to 5 feet above the runway he brought the nose up just slightly and instantly the airplane stalled and collided with the edge of the runway, sliding to a stop on the runway surface. According to a Federal Aviation Administration (FAA) airworthiness inspector who performed a post accident inspection of the airplane, the right-hand flap leading edge structure was located above the trailing edge of the wing’s surface, which resulted in an asymmetric flap condition. The inspector further reported substantial damage to the airplane’s left wing, damage to the propeller, and that all three landing gear had separated due to impact forces with the ground. On September 23, 2010, Lancair issued Service Bulletin SB073-0910, Flaps and Wing Skin Interface – 235,/320/360, Ref: 320/360 Build Manual, Chapters 9 & 10. The SB states, “All Lancair 235, 320, and 360’s with flaps hinged on the bottom of the wing skin must review Chapter 9 and 10 of the 320/360 build manual. Apparently there has been an instance where the flap can travel above the trailing edge of the wing, but only when the trailing edge isnot stiffened as per the manual instructions.” The SB further states, “This service bulletin is an advisory requesting an inspection of the flaps and trailing edge interface on Lancair 235, 320 and 360 kit aircraft. Before the next flight, inspect flap hinge attachments and lower wing skin trailing edge structure for proper stiffness.” The SB also noted under the subheading Action: WARNING: Adequate clearances must be established and sufficient stiffness established such that the flaps upper rolled L.E. when fully deployed, will not have a tendency to flex upward and snag on the upper wing T.E. Such a condition could jam the flap and thus not allow retraction of the flap. This could be dangerous on an aborted landing and subsequent “go-around.” Check this closely. ## Aircraft - Registration: [N360N](https://openairdocs.org/deregistered/N360N-2019-09-06), registration cancelled 2019-09-06, S/N 330, built 1999 (OpenAirDocs) - Reported make and model: LANCAIR 320 (NO SERIES) - Registry model: [Smith Martin P LANCAIR 320](https://openairdocs.org/model/smith-martin-p-lancair-320) (registry code 05606AY) (OpenAirDocs) - Registry engine: [Lycoming 0-360-C1F](https://openairdocs.org/engine/lycoming-0-360-c1f) (registry code 41573, reciprocating) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: 330 - Airframe hours: 437 - Engines: Lycoming IO-360 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Larry O. Sundholm - Registered owner: Larosun Services Inc. - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Annual, July 22, 2010, 1 hours before - Departed: SFF, Spokane, WA - Destination: SFF, Spokane, WA - Airport: SFF, Felts Field, runway 03L, 4,500 × 150 ft, concrete ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 71; injuries: minor; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review October 8, 2009; seat: left; flight hours: 2,355 total, 42 in this make and model, 2,300 as pilot in command, 3 in the last 90 days, 3 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 50° at 3 knots - Visibility: 12 statute miles - Lowest ceiling: none - Temperature: 75 °F, dew point 55 °F - Altimeter: 29.93 inHg - Observed at: SFF ## 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 20100727038979A](https://openairdocs.org/incident/20100727038979A), Jul 27, 2010: Smith Marti LANCAIR 320, Spokane, WA, Substantial damage. On July 27, 2010 a Smith martin p Lancair 360 crash landed short of runway 3L at Felts field. On scene investigation revealed aircraft impacted terrain… ## Docket (6 files) The files NTSB released with the investigation on October 21, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=76795. 1.4 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 425 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40355240&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Weather Data (item 2, .PDF, 56 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40355241&FileExtension=.PDF&FileName=Weather%20Data-Master.PDF - FAA Inspector's Statement (item 3, .PDF, 43 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40355242&FileExtension=.PDF&FileName=FAA%20Inspector%27s%20Statement-Master.PDF - Excerpts from Maintenance Records (item 4, .PDF, 603 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40355243&FileExtension=.PDF&FileName=Excerpts%20from%20Maintenance%20Records-Redacted.PDF - Lancair Service Bulletin SB073-0910 (item 5, .PDF, 236 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40355249&FileExtension=.PDF&FileName=Lancair%20Service%20Bulletin%20SB073-0910-Master.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 6, .PDF, 56 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40355244&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.