NTSB CAROL · Event
Event WPR10LA374
Registry · N360N
FAA Aircraft Registry record.
Make / Model
DASSAULT AVIATION FALCON 7X
Year of manufacture
2009 · 1 years old at event
Engine
P&W CANADA PW307A
Seats / Engines
11 seats · 3 engines
Last airworthiness date
20240621
ADS-B equipped
Yes — Mode-S A40D78
Registrant of record
FALCON 7X MSN 041 LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
Loss of airplane control due to the asymmetric flap condition.
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 is not 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. 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. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Aircraft-Aircraft systems-Flight control system-TE flap control system-Malfunction - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Lateral/bank control-Attain/maintain not possible - C
Verbatim from NTSB's published report. Source file
NTSB_2010_WPR10LA374.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, loss of control, go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- arXiv 2022 · arXiv preprint
Experimental investigations on the characteristics of snow accretion using the EMU-320 model train
This paper presents a snow accretion test conducted in a climate wind tunnel to investigate the icing process on a model train.
- Embry-Riddle Scholarly Commons 2017 · Conference paper
Pilot Control Design Influences on Pilot Monitoring Effectiveness of Crew Resource Management in Airbus 320 Landings
The purpose of this paper is to examine the effects of Airbus flight control design on pilot perception of Crew Resource Management (CRM) in the landing phase of flight.
- Embry-Riddle Scholarly Commons 2015 · Journal article (JAAER)
Is “Green Dot” Always the Optimum Engines-Out Glide Speed on the Airbus A320 Aircraft?
The dual-engine failure checklist of the Airbus A320 states that the optimum airspeed at which the aircraft can be flown is the “green dot” speed when an engine restart is considered impossible.
- NTSB Aircraft Accident Reports 2021 · Accident report
Crash of Atlas Air Flight 3591, Boeing 767-300 (N1217A)
Atlas Air 3591 crashed into Trinity Bay, Texas, February 23, 2019. Investigation of the in-flight loss-of-control crash of Atlas Air 3591 into Trinity Bay, Texas.
- Semantic Scholar 2016 · Article (Interacción)
Trajectory Recovery System: Angle of Attack Guidance for Inflight Loss of Control
This paper describes the design and development of an ecological display to aid pilots in the recovery of an In-Flight Loss of Control event due to a Stall (ILOC-S).
- NTSB Aircraft Accident Reports 2010 · Accident report
Loss of Control on Approach — Colgan Air Flight 3407
Colgan Air 3407 / Continental Connection (Q400) Buffalo NY, February 12, 2009 — 50 fatalities. Definitive investigation of the Colgan 3407 stall-stick-pusher crash on approach to Buffalo.
Browse the full corpus — academia portal ↗