Luscombe 8F
NTSB investigations · 109
Matched to the registry by N-number and event date, newest first.
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
WHERE a.aircraft_model_code IN ('8190114')
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.aircraft_model_code IN ('8190114')
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB ERA25LA180Accident · No injuriesClass 4 · LimitedFinal reportLuscombe 8F · Punta Gorda, FLThe pilot’s failure to maintain direction control of the airplane during the landing roll.NTSB CEN23LA170Accident · No injuriesClass 3 · LimitedFinal reportLuscombe 8F · Palmer, TXThe installation of an unapproved rudder control cable, which resulted in a fatigue failure and subsequent loss of rudder control during cruise flight. Contributing to the accident was the mechanic’s inadequate inspection of the rudder control system.NTSB CEN21FA327Accident · 1 fatalClass 3 · FieldFinal reportLuscombe 8F · Comstock, TXImpact with terrain for reasons that could not be determined based on the available information.NTSB GAA20CA028Accident · Minor injuriesData collectionFinal reportLuscombe 8 · Lebanon, NHThe pilot's failure to maintain directional control during landing, which resulted in a runway excursion and impact with a ditch.NTSB GAA19CA224Accident · No injuriesData collectionFinal reportLuscombe 8 · Bremen, ALThe pilot's delayed decision to abort the takeoff, which resulted in a runway overrun, impact with a fence, and a nose-over.NTSB GAA18CA448Accident · Minor injuriesData collectionFinal reportLuscombe 8 · Lawrenceville, VAThe pilot’s failure to maintain directional control during the landing roll with a tailwind.NTSB GAA18CA061Accident · Minor injuriesData collectionFinal reportLuscombe 8 · Caldwell, TXThe pilot’s failure to maintain yaw control and the exceedance of the airplane’s critical angle of attack in the traffic pattern, which resulted in an aerodynamic stall/spin.NTSB CEN17LA135Accident · 1 fatalLimited investigationFinal reportLuscombe 8F · Vicksburg, MIThe pilot's inadvertent contact with the propeller while hand propping the engine, which resulted in a fatal injury.NTSB CEN13LA127Accident · No injuriesLimited investigationFinal reportLuscombe 8 · Elkhart, INThe pilot’s improper flare, which resulted in a bounced landing.NTSB WPR11CA271Accident · No injuriesData collectionFinal reportLuscombe 8F · McCall, IDThe pilot's failure to maintain adequate airspeed that resulted in a stall/mush. Contributing to the accident was the pilot's failure to maintain an adequate spacing from the aircraft ahead of him.NTSB CEN10CA313Accident · No injuriesData collectionFinal reportLuscombe 8F · Shell Knob, MOA total loss of engine power for undetermined reasons.NTSB SEA07LA098Accident · No injuriesLimited investigationFinal reportLuscombe 8F · Ocala, FLThe failure of the left main axle during the landing roll, which resulted in the collapse of the left main landing gear. A crosswind on the landing runway was a factor.NTSB DEN07CA019Accident · No injuriesData collectionFinal reportLuscombe 8F · Wellsville, KSA loss of engine power due to the ingestion of the number 2 intake valve into its cylinder. Contributing factors included the pilot allowing the airspeed and altitude to drop, making a safe landing not possible.NTSB LAX05LA103Accident · No injuriesLimited investigationFinal reportLuscombe 8F · Kapolei, HIthe pilot's inadequate compensation for the quartering tailwind conditions, and his failure to maintain directional control of the airplane during landing. Related factors were the tailwind and crosswind.NTSB NYC04CA159Accident · No injuriesData collectionFinal reportLuscombe 8F · Andover, NJThe pilot's failure to maintain aircraft control during approach. A factor was windshear.NTSB LAX04LA009Accident · Minor injuriesLimited investigationFinal reportLuscombe 8F · Murrieta, CAThe pilot's inadequate evaluation of the weather which resulted in VFR flight into IMC, and his failure to maintain terrain clearance. Fog and rising terrain were contributing factors.NTSB NYC03LA044Accident · Serious injuriesLimited investigationFinal reportLuscombe 8F · Newport, METhe fatigue failure of a the cylinder wall.NTSB CHI02LA204Accident · No injuriesLimited investigationFinal reportLuscombe 8F · Farmington, MOThe locked brake and the aircraft control not being possible due to the locked brake.NTSB LAX01LA090Accident · Minor injuriesLimited investigationFinal reportLuscombe 8F · Tombstone, AZThe pilot's lack of directional control on the landing roll, which resulted in a ground loop and inadvertent nose over.NTSB SEA99LA096Accident · No injuriesLimited investigationFinal reportLuscombe 8F · Nampa, IDDirectional control was not maintained. Diverted attention was a factor.NTSB ANC99LA050Accident · Serious injuriesLimited investigationFinal reportLuscombe L-8F · Kodiak, AKThe pilot's inadequate terrain clearance during the initial climb, and the inadvertent stall/spin during the turn to avoid terrain. A factor in this accident was the pilot exceeding the allowable maximum gross weight of the airplane.NTSB SEA98LA010Accident · No injuriesLimited investigationFinal reportLuscombe 8F · Boise, IDThe student pilot's failure to maintain directional control due to excessive taxispeed. Pressure perceived by the student pilot to expedite clearing the runway after landing in order to facilitate an aircraft departure was a contributing factor.NTSB IAD97LA119Accident · Minor injuriesLimited investigationFinal reportLuscombe LL-8-F · Carrollton, OHThe pilot's inadequate preflight which resulted in fuel exhaustion.NTSB NYC97LA114Accident · No injuriesLimited investigationFinal reportLuscombe 8F · New Town, PAThe pilot's improper fuel management, which resulted in an intermittent fuel supply, and a loss of engine power.NTSB FTW97LA052Accident · No injuriesLimited investigationFinal reportLuscombe 8F · Floydada, TXThe pilot's inadequate compensation for the crosswind during landing. Factors were the crosswind and the locked left main wheel brake.NTSB LAX95LA102Accident · Minor injuriesLimited investigationFinal reportLuscombe 8F · Wickenburg, AZThe pilot-rated passenger's failure to maintain directional control of the airplane during the takeoff ground roll, and the pilot-in-command's inadequate supervision of the pilot-rated passenger, who had sole access to the airplane's brakes.NTSB ATL94LA015Accident · Serious injuriesLimited investigationFinal reportLuscombe 8F · Griffin, GAThe pilot's failure to maintain airspeed while maneuvering following a loss of engine power for unknown reasons.NTSB CHI94LA009Accident · No injuriesLimited investigationFinal reportLuscombe 8F · Benton, KSThe failure of the student pilot to maintain directional control and proper runway alignment during the landing roll. The proximity of the ditch to the runway was a related factor.NTSB CHI93LA369Accident · No injuriesLimited investigationFinal reportLuscombe 8F · Festus, MOa fatigue failure of the tailwheel spring.NTSB CHI92LA051Accident · No injuriesLimited investigationFinal reportLuscombe 8-F · Chapin, IAFailed connecting rod which resulted in a catastrophic engine failure. A factor related to the accident was unsuitable terrain.NTSB DEN90LA117Accident · No injuriesLimited investigationFinal reportLuscombe 8F · Morgan, UTPilot's improper use of the brakes during landing roll.NTSB MKC89LA111Accident · No injuriesLimited investigationFinal reportLuscombe 8F · Ramsey, MNThe passengers interference with the flight controls and the pilot's failure to maintain control of the aircraft. Contributing to the severity of the accident was the ditch located short of the runway which the aircraft contacted.NTSB LAX88LA139Accident · No injuriesLimited investigationFinal reportLuscombe 8F · Lompoc, CADuring the landing roll with a crosswind of 15-20 knots, the pilot lost control of the aircraft, collided with the terrain and, approximately 200 yards off the runway, the aircraft nosed over.NTSB LAX86LA322Accident · 2 fatalLimited investigationFinal reportLuscombe 8F · Marble Canyon, AZWitnesses rprtd that prior to the acdnt, the plt made a low pass over a raft on the Colorado river to 'wave his wings' at the rafting group. Rprtdly, he was attempting to reverse his direction when the acft suddenly crashed in the river. A search was…NTSB LAX86LA096Accident · Minor injuriesLimited investigationFinal reportLuscombe 8F · Half Moon Bay, CAThe plt reported that on approach he was 'a little high & hot' for the 5000-FT-long rwy. He said that at midfield he was 100 ft. AGL & he decided to go around. Upon applying power only 700 RPM was obtained, so he then attempted to land the acft at the end of…NTSB BFO85LA010Accident · No injuriesLimited investigationFinal reportLuscombe 8F · Newburg, MDDuring ldg roll the PIC felt a vibration as the tailwheel contacted the rwy. In an effort to minimize the vibration the plt lifted the tailwheel off the rwy. The acft began to ground loop to the right toward a pole. Heavy application of the wheel brakes…NTSB SEA84FA198Accident · Serious injuriesField investigationFinal reportLuscombe 8F · Levenworth, WAAccording to the plt, downdrafts encountered after takeoff prevented a normal climb and resulted in a collision with trees at 60 to 80 ft AGL aprx 1 mile from the arpt.NTSB DEN82DA124Accident · No injuriesFinal reportLuscombe 8F · Calhan, COThe pilot took off from an airport with a density altitude of about 9500 ft. after lift-off, the aircraft reached an altitude of about 100 ft AGL and then stopped climbing. The pilot initiated emergency procedures which included leaning the mixture and…NTSB NYC82FHD09Accident · Minor injuriesFinal reportLuscombe 8F · Essington, PAThe float equipped Luscombe stalled during fanal approach to a water landing near a dock. There was considerable rotorcraft activity near the seaplane base due to the presence of the queen elizabeth ii ocean liner.NTSB SEA82DYA02Accident · Minor injuriesClosedLuscombe 8F · Howe, IDNTSB SEA81FYE26Accident · No injuriesClosedLuscombe 8F · Index, WANTSB CHI81FEC11Accident · No injuriesClosedLuscombe 8E · Belleville, MINTSB NYC80FHJ17Accident · Minor injuriesClosedLuscombe 8F · Amagansett, NYNTSB NYC79DFA03Accident · No injuriesClosedLuscombe 8F · Saratoga Spgs, NYNTSB ANC78DAG70Accident · Serious injuriesClosedLuscombe 8F · Homer, AKNTSB DEN78FTE50Accident · Minor injuriesClosedLuscombe 8F · Monte Vista, CONTSB IAD77FLJ28Accident · Serious injuriesClosedLuscombe 8F · Louisburg, NCNTSB CHI77FEC34Accident · No injuriesClosedLuscombe 8F · Clio, MINTSB CHI77FEC05Accident · Minor injuriesClosedLuscombe 8F · Manchester, MINTSB CHI76FEM35Accident · No injuriesClosedLuscombe 8E · Glen, MI
Back to Luscombe 8F