Hughes 269B
NTSB investigations · 372
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 ('4470502')
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 ('4470502')
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 ERA27FA004Accident · 1 fatalClass 3 · FieldInvestigation openHughes 269B · Lahmansville, WVNTSB ERA19LA173Accident · No injuriesClass 3 · LimitedFinal reportHughes 269B · Hampton, GAGround resonance during landing for reasons that could not be determined based on the available information.NTSB ERA16LA326Accident · Minor injuriesLimited investigationFinal reportHughes 269B · Ozark, ALA total loss of engine power for reasons that could not be determined following a successful postaccident engine run on the accident helicopter.NTSB ERA15LA376Accident · Serious injuriesLimited investigationFinal reportHughes 269 · Eustis, FLThe pilot's failure to maintain yaw control as he slowed the helicopter during a landing approach, which resulted in a loss of helicopter control due to a loss of tail rotor effectiveness.NTSB ERA15CA364Accident · Minor injuriesData collectionFinal reportHughes 269B · Hartford, ALThe pilot's inadequate preflight planning, and his subsequent failure to attain adequate altitude during takeoff, which resulted in a collision with a wire fence.NTSB CEN15LA341Accident · Serious injuriesLimited investigationFinal reportHughes 269B · Atkinson, ILThe pilot's improper decision to intentionally fly the helicopter at a low altitude and his subsequent failure to maintain clearance from a power line.NTSB WPR13CA337Accident · No injuriesData collectionFinal reportHughes 269B · Lewiston, IDThe pilot's incorrect application of the cyclic control during the landing.NTSB CEN11LA315Accident · No injuriesLimited investigationFinal reportHughes 269B · Edgerton, INA loss of clearance between the tail rotor drive shaft and the tailboom bulkhead for undetermined reasons, which resulted in the overstress failure of the drive shaft.NTSB CEN10CA469Accident · Serious injuriesData collectionFinal reportHughes 269B · Lakeview, MIThe pilot's excessive descent angle during landing approach, which resulted in a settling with power condition.NTSB DEN08FA122Accident · 2 fatalField investigationFinal reportHughes 269B · Salesville, ARThe pilot's failure to maintain clearance from the crossing transmission line.NTSB CHI08CA164Accident · Minor injuriesData collectionFinal reportHughes 269B · Cook, MNThe pilot not maintaining tail rotor effectiveness while turning in cruise.NTSB DFW07CA037Accident · No injuriesData collectionFinal reportHughes 269B · Houma, LAA partial loss of engine power as a result of a cracked engine cylinder and broken spark plug which resulted in a hard landing. A factor was that it was not possible to attain proper rotor RPM.NTSB CHI06LA124Accident · No injuriesLimited investigationFinal reportHughes 269B · Sullivan, OHFatigue failure of the fuselage-to-tail boom cluster fitting, and the secondary failure of the tail rotor drive shaft. An additional cause was the incomplete compliance with an applicable Airworthiness Directive. A factor was the ditch.NTSB NYC04CA096Accident · No injuriesData collectionFinal reportHughes 269B · Farmingdale, NYThe pilot's failure to maintain aircraft control while hover-taxiing. A factor in this accident was the high wind condition.NTSB CHI04LA030Accident · Minor injuriesLimited investigationFinal reportHughes 269B · Louisville, KYThe pilot's improper in-flight decision to allow the passenger to manipulate the aircraft flight controls, his failure to maintain altitude/clearance from the river, and his inadequate remedial action. A related factor was the low altitude.NTSB LAX03FA134Accident · 2 fatalField investigationFinal reportHughes 269B · Auburn, CAthe misjudged flare maneuver by an unknown crewmember during a likely practice autorotation that resulted in an in-flight collision with terrain.NTSB CHI01LA293Accident · No injuriesLimited investigationFinal reportHughes 269B · Pontiac, MIthe checklist not compiled with by the operator and not verified by the operator’s pilot and the operator's flight instructor. An additional cause was the improper autorotation by the pilot in command. The out of calibration engine idle speed was a…NTSB FTW01LA109Accident · Minor injuriesLimited investigationFinal reportHughes 269B · Nacogdoches, TXthe pilot's failure to maintain clearance with the wires during takeoff. Contributory factors were the sunglare and the unmarked wires.NTSB SEA00LA193Accident · No injuriesLimited investigationFinal reportHughes 269B · Laurel, MTFailure to maintain aircraft control during hover operations. Inadequate remedial action by the pilot was a factor.NTSB SEA00LA188Accident · Minor injuriesLimited investigationFinal reportHughes 269B · Burlington, WAMintenance personnel not following the mandatory service bulletin procedure of not exceeding 0.0005 inch paint thickness on the cylinder flange. Factors were the fatigue separation of multiple cylinder hold down bolts resulting in looseness of the cylinder;…NTSB FTW99LA234Accident · Minor injuriesLimited investigationFinal reportHughes 269B · Russellville, ARThe improper touchdown by the flight instructor.NTSB FTW98LA356Accident · No injuriesLimited investigationFinal reportHughes 269B · Uvalde, TXThe pilot's failure to maintain control during a vertical, out of ground effect takeoff which resulted in a hard emergency landing. Factors were; the exceeded hover performance of the helicopter, the high density altitude, and the lack of suitable terrain for…NTSB NYC98LA025Accident · No injuriesLimited investigationFinal reportHughes 269B · Cleveland, OHthe pilot's failure to recover from settling-with-power. Factors relating to the accident were: the pilot's downwind approach and low airspeed.NTSB NYC97LA138Accident · Minor injuriesLimited investigationFinal reportHughes 269B · Paducah, KYThe failure of maintenance personnel to identify and correct the worn holes on the lower fuselage fairing and the failure of the flight instructor to maintain main rotor RPM during the autorotative landing. A contributing factor was the flight instructor's…NTSB FTW96LA375Accident · No injuriesLimited investigationFinal reportHughes 269B · Frisco, TXThe pilot's improper touchdown procedure.NTSB LAX96LA217Accident · No injuriesLimited investigationFinal reportHughes 269B · Georgetown, CAloss of engine power for undetermined reason(s), while practicing an autorotation, which resulted in a forced landing; and the flight instructor's misjudged landing flare during the emergency autorotation/landing.NTSB ATL95LA175Accident · Serious injuriesLimited investigationFinal reportSchweizer 269C · Hoover, ALThe pilot's failure to maintain directional control when he positioned the helicopter in a hover so as to induce a loss of tail rotor effectiveness.NTSB NYC95LA170Accident · No injuriesLimited investigationFinal reportHughes 269B · Honesdale, PACorrosion and subsequent failure of the attaching lugs for the left (4H) shock strut assembly, which resulted in collapse of the landing gear/skid.NTSB SEA95LA112Accident · Minor injuriesLimited investigationFinal reportHughes 269B · Caldwell, IDThe pilot's failure to maintain clearance from power lines. Factors include sunglare encountered when he turned into the sun.NTSB ATL95LA053Accident · No injuriesLimited investigationFinal reportSchweizer 269B · Addison, ALThe pilot's improper use of the throttle control during a descent which resulted in a hard landing.NTSB ATL94LA002Accident · No injuriesLimited investigationFinal reportHughes 269B · Linville, NCThe pilot's failure to maintain airspeed that would have avoided a loss of tail rotor effectiveness (lte), and his improper compensation for tailwind condition. A factor was the lack of information in the pilot's operating handbook regarding the conditions…NTSB SEA93IA073Incident · No injuriesIncident investigationFinal reportHughes 269B · Mcminnville, ORAn inflight loss of control, and inadequate remedial action. Factors include a tailwind, and gusts.NTSB LAX93LA063Accident · No injuriesLimited investigationFinal reportHughes 269B · Kahului, HIFailure of the pilot to maintain adequate rotor RPM during downwind flight and adequate altitude to recover the loss of main rotor RPM before settling into the water. Contributing to the accident was the pilot's lack of rotorcraft flight experience.NTSB SEA92LA005Accident · No injuriesLimited investigationFinal reportHughes 269B · Hillsboro, ORThe failure to maintain rotor RPM. Factors include inadequate preflight planning, overconfidence in aircraft's ability, and non-suitable terrain.NTSB FTW91FA123Accident · 1 fatalField investigationFinal reportHughes 269B · Brickeys, ARThe failure of the clutch control cable due to fraying which initiated the forced landing and the operator's failure to perform recommended inspections on the aircraft. Factors were the pilot's failure to maintain rotor RPM and the unsuitable terrain.NTSB SEA91LA137Accident · Minor injuriesLimited investigationFinal reportHughes 269B · Warrenton, ORThe pilot failed to maintain proper rotor speed during a simulated autorotation.NTSB LAX91LA257Accident · 1 fatalLimited investigationFinal reportSchweizer 269B · Cottonwood, CAThe pilot's inadequate visual lookout. The transmission wire was a factor in the accident.NTSB SEA91LA104Accident · No injuriesLimited investigationFinal reportHughes 269B · Grand Ronde, ORThe pilot inadvertently interfered with the controls.NTSB LAX90LA210Accident · No injuriesLimited investigationFinal reportHughes 269B · Paso Robles, CAThis accident was dynamic rollover due to the terrain slope exceeding the capability of the helicopter.NTSB MIA89LA255Accident · Minor injuriesLimited investigationFinal reportHughes 269B · Lexington, MSFatigue failure of the linear actuator lug. A related factor was: trees in the emergency landing area.NTSB LAX89LA152Accident · Minor injuriesLimited investigationFinal reportHughes 269B · Long Beach, CAImproper in-flight planning/decision by the pilot, which led to an inadequate supply of fuel to reach the airport and subsequent fuel exhaustion. The pilot's lack of flight time in this make and model of helicopter was considered to be a factor.NTSB CHI88FA214Accident · 3 fatalField investigationFinal reportHughes 269B · Hampton, ILNTSB CHI88FA190Accident · 2 fatalField investigationFinal reportMcdonnell Douglas 269B · Braceville, ILConducting maneuvering flight the PIC failed to monitor the helicopter systems and allowed the main rotor RPM to decay to the point where it would not produce enough lift to sustain flight.NTSB LAX88LA233Accident · No injuriesLimited investigationFinal reportHughes 269B · Big Bear, CAWhile cruising, the plt perceived he was experiencing a loss of engine & rotor RPM. The plt stated that he attempted to regain RPM by autorotating. The RPM was regained in the autorotative descent. The plt elected to continue the descent to a landing. Upon…NTSB CHI88LA108Accident · Minor injuriesLimited investigationFinal reportHughes 269B · Minneapolis, MNThe pilot was executing a downwind takeoff, the winds reportedly gusting to 25 knots, loaded with two passengers, when just after takeoff the pilot stated the helicopter experienced a loss of power. The pilot then attempted to execute an autorotation, but…NTSB SEA88LA022Accident · Minor injuriesLimited investigationFinal reportHughes 269B · Las Vegas, NVDuring practice autorotation the pilot flared excessively high and the tail boom struck the ground. The pilot then lost control of the aircraft. The density alt was 2616 feet. A rt quartering tailwind was present.NTSB LAX87LA190Accident · Minor injuriesLimited investigationFinal reportHughes 269B · Rubidoux, CAA Hughes 269B went out of control and collided with the ground during a t/o to a hover. The pilot had purchased the aircraft recently and was learning to fly it. He was scheduled for his first flight lesson on the day of the accident. The CFI reported that he…NTSB CHI87LA098Accident · No injuriesLimited investigationFinal reportHughes 269B · South Bend, INAccording to the plt, after departure from aurora municipal airport, he landed at an airfield west of elgin, Illinois and picked up the two passengers. The plt stated that he then departed for elkhart, Indiana. According to an Indiana state police aircraft…NTSB ANC87LA008Accident · No injuriesLimited investigationFinal reportHughes 300-269B · Fairbanks, AKThe helicopter exhausted its fuel supply during climbout. During the ensuing autorotation landing, the rotor speed was allosed to decay and the helcopter spun at touchdown. It rolled over and failed the rotor blades.NTSB CHI86LA236Accident · No injuriesLimited investigationFinal reportHughes 269B · Baldwin, WIAfter picking up his passenger at williams pipeline, minneapolis, Minnesota, the plt flew eastward along interstate 90 enroute to a pipeline near wausau, Wisconsin. While flying at approximatelly 400 feet, the plt and passenger stated that the engine started…
Back to Hughes 269B