Luscombe 8E
NTSB investigations · 308
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 ('8190112')
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 ('8190112')
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 IAD98LA011Accident · No injuriesLimited investigationFinal reportSilvaire Luscombe 8B · Bluefield, WVThe pilot failed to maintain control of the airplane.NTSB NYC97LA112Accident · No injuriesLimited investigationFinal reportLuscombe LL-8-E · Charlottesville, VAThe left main landing gear collapsed due to corrosion.NTSB FTW97LA062Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Ardmore, OKThe loss of engine power for undetermined reasons. A factor was the lack of suitable terrain for the pilot to execute the forced landing.NTSB NYC96LA115Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Macedon, NYa blocked gascolator, inadequate maintenance, and the pilot's decision to fly with a known fuel flow deficiency, which resulted in a loss of engine power, forced landing, and subsequent nose over.NTSB CHI95LA275Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Lowell, INa loss of engine power due to carburetor ice. The lack of suitable terrain for a forced landing was a factor.NTSB LAX95LA247Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Columbia, CAthe pilot's inadequate compensation for the gusty crosswind condition and failure to maintain directional control.NTSB LAX95LA055Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Hemet, CAThe other aircraft pilot's inadequate bounced landing recovery and his failure to maintain directional control.NTSB CHI94LA285Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Hettinger, NDthe pilot's improper use of the wheel brakes.NTSB MIA94LA140Accident · Minor injuriesLimited investigationFinal reportLuscombe 8E · Deland, FLCorrosion and subsequent failure of the left main landing gear strut.NTSB SEA94LA099Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Coalville, UTThe failure of the connecting rod. Factors include the rough uneven terrain encountered during the forced landing.NTSB LAX94LA161Accident · No injuriesLimited investigationFinal reportLuscombe 8EZ · Prescott, AZthe flying pilot's inadequate compensation for the existing crosswind condition, his failure to maintain directional control, and the inadvertent entry into a ground loop. A factor in the accident was the flying pilot's lack of experience in conventional…NTSB LAX93LA358Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Napa, CAThe loss of engine power for undetermined reasons. The rough/uneven terrain was a factor in this accident.NTSB FTW93LA110Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Abbeville, LAThe pilot's failure to compensate for crosswind conditions and the subsequent loss of directional control. Factors were the gusting crosswinds and the soft wet groundNTSB BFO92LA147Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Rochester, MAThe pilot's abrupt application of the brakes which resulted in the airplane nosing over.NTSB FTW92LA115Accident · Minor injuriesLimited investigationFinal reportLuscombe 8E · Acton, TXThe excessive airspeed during the landing. Factors were the carburetor icing conditions, the carburetor ice induced power loss, and the pilot's delayed use of carburetor heat.NTSB CHI92LA091Accident · Minor injuriesLimited investigationFinal reportLuscombe 8E · Farrar, MOPremature liftoff and poor planning by the pilot. Factors related to the accident were the tailwind and misjudged compensation for it along with the rough uneven terrain.NTSB CHI91LA256Accident · Serious injuriesLimited investigationFinal reportLuscombe 8E · Valparaiso, INThe pilot in command's failure to maintain airspeed. A factor contributing was improper maintenance (design change) performed by an unqualified person (pilot in command).NTSB CHI91FA159Accident · 1 fatalField investigationFinal reportLuscombe 8E · Clinton, MIPhysical impairment of the pilot due to heart attack.NTSB CHI91LA118Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Flushing, MIThe pilot's failure to attain proper runway alignment and not maintaining directional control which resulted in a ground loop. Factors relating to this accident were the gusty crosswind conditions which existed at the time.NTSB FTW89FA025Accident · 1 fatalField investigationFinal reportLuscombe 8E · Port Lavaca, TXThere were no records to indicate the non-instrument rated pilot received a pre-flight weather briefing from any weather reporting service. Witnesses in the area of the accident stated the night was dark and the ground was covered with fog. The airplane…NTSB NYC88LA140Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Rochester, NYThe Luscombe 8E experienced a failure of the right main landing gear axle during a bounced landing. The failure occurred at the weld where the axle attaches to the landing gear strut. Examination of the fracture revealed a pre-existing crack that was not…NTSB ATL87LA253Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Cartersville, GAThe plt reported a loss of power on climb out. An off arpt landing attempt resulted in impact with trees and substantial damage to the acft. Temperature and dewpoint were within the range for carburetor ice buildup. Examination of the acft revealed a cruise…NTSB LAX87FA286Accident · 2 fatalField investigationFinal reportLuscombe 8A · Oakdale, CAThe plt & his plt-rated wife (flying in their Luscombe) & another couple (in a rented Mooney) had dinner & drank wine. By about 0015 the couples had taken off in their respective acft for a return flt home and they had each other in sight. The couple in the…NTSB CHI87LA141Accident · Minor injuriesLimited investigationFinal reportLuscombe 8E · Dodgeville, WIWhile landing on runway 30, the pilot reported that the wind shifted from a crosswind to a tailwind. During an attempted go-around the pilot lost directional control and struck a metal utility shed prior to impacting the ground.NTSB MKC87LA008Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Macon, MOThe pilot stated that he encountered more severe crosswinds than planned upon landing and that he tried remedial action, including a rejected landing, but it came too late. The wind was blowing from the right on the landing roll as he shut down the engine and…NTSB SEA86LA118Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Juneau, AKAcft had history of water in fuel and the system was purged. During winter, the plt did not fly acft but ran the eng periodically. On the day of the accident, the plt refueled the acft, completed a normal pwr run-up and took off. Shortlyafter takeoff, a pwr…NTSB NYC85LA209Accident · Minor injuriesLimited investigationFinal reportLuscombe 8E · Carthage, NYAccording to the pilot,while climbing to cruise, the engine began to run rough; however it did not quit. The pilot decided to return to the field for a precautionary landing. While turning onto final approach, the engine quit and the pilot attempted to glide…NTSB DEN85LA157Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Albuquerque, NMThe plt reported that during a normal landing, the right main gear folded back, followed by collapse of the left main gear. An exam revealed evidence of fatigue failure of a clevis bolt in the threaded area.NTSB FTW85FA209Accident · 2 fatalField investigationFinal reportLuscombe 8E · Verden, OKAt about 1700 CDT on 5/5/85, the acft was observed taking off at chickasha, OK. At sometime after 1700, an acft matching its description was observed flying low over a lake. A witness in that area observed it pulled up in a steep climb over the dam, until it…NTSB DEN85LA030Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Oaks, NDPlt stated that immediately after touchdown, the right wheel seemed to drag. Right drift was initially corrected by use of opposite aileron to reduce weight on right wheel and rudder for directional control. However, as the acft slowed weight settled on the…NTSB ANC84LA111Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Seldovia, AKThe acft nosed over during landing on a 2600 ft gravel rwy nestled in the hills with variable winds. The plt had temporarily traded acft for this trip and had not flown this type of acft for the preceding 90 day period. He normally flew his Cessna 185. He was…NTSB DEN84LA015Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Oakes, NDAfter a brief stop at oaks, ND, for fuel, the plt took off to fly about 5 mi to his private strip in an alfalfa field. During the landing roll, the gear hit a gopher mound & the acft nosed over.NTSB LAX83LA111Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Chino, CAThe acft bounced ground looped off the runway and nosed over during landing. The acft left the runway and went into grass that was about 3 feet high. When the landing gear dug into soft dirt the acft nosed over. The pilot had only about 3 hours flying time in…NTSB ATL83FKJ02Accident · Serious injuriesFinal reportLuscombe 8E · Elba, ALThe plt had received a wx briefing aprx 4 hrs before departure. He stated that on arrival, the arpt beacon light was not on & patches of ground fog were in the area. During the arrival, he approached from the south, flew north over the arpt, circled to the…NTSB FTW82FQD12Accident · Serious injuriesFinal reportLuscombe 8E · Timberon, NMPlt stated he could not gain sufficient altitude to clear terrain. A witness observed the acft at approximately 150-200 ft AGL, well below the top of the canyon.NTSB CHI82DA258Accident · No injuriesFinal reportLuscombe 8F · Belleville, MIDuring the approach the acft stalled about 20 ft AGL. The plt added power but the acft touched down short of the rwy & collided with a ditch.NTSB MKC82DA090Accident · No injuriesFinal reportLuscombe 8E · Goodland, KSWhile en route, the pilot encountered headwinds and elected to land at Goodland, Kansas to refuel. He landed on runway 12 with a crosswind from 320 degrees at 6 knots. The pilot stated that after touchdown, he got a cramp in his right leg and removed his…NTSB SEA82DA040Accident · No injuriesFinal reportLuscombe 8E · Blaine, WAUpon arrival the pilot observed the wind to be 90 degrees to the runway with an estimated velocity of 5 to 7 knots. A low pass was completed followed by a landing on runway 32. During the rollout the aircraft drifted right, the landing gear encountered…NTSB NYC82DA061Accident · No injuriesFinal reportLuscombe 8E · Poestenkill, NYThe pilot stated that during landing flare while holding full aft on the control stick the right wing came up and the aircraft drifted left. Full right rudder and aileron were applied but the main gear struck a snowbank along the left side of the runway and…NTSB NYC81DFJ24Accident · No injuriesClosedLuscombe 8E · Nunda, NYNTSB CHI81FEM85Accident · No injuriesClosedLuscombe 8E · Gladwin, MINTSB LAX80DVA45Accident · No injuriesClosedLuscombe 8-E · Selma, CANTSB NYC79DFJ27Accident · No injuriesClosedLuscombe 8E · Gasport, NYNTSB MKC79DCD34Accident · No injuriesClosedLuscombe 8E · Oskaloosa, IANTSB NYC79FNE19Accident · No injuriesClosedLuscombe 8E · Plainville, CTNTSB CHI79FEX23Accident · Minor injuriesClosedLuscombe 8E · Lanesville, INNTSB LAX79FUG26Accident · No injuriesClosedLuscombe 8E · Redlands, CANTSB MKC78FER68Accident · Serious injuriesClosedLuscombe 8E · Webster, MNNTSB MKC78DCJ26Accident · No injuriesClosedLuscombe 8E · Utica, NENTSB LAX78FUQ31Accident · Minor injuriesClosedLuscombe 8E · Pearblossom, CA
Back to Luscombe 8E