Beech F33A
NTSB investigations · 172
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 ('1151425')
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 ('1151425')
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 FTW95LA095Accident · No injuriesLimited investigationFinal reportBeech 33-A · Lago Vista, TXThe pilot's failure to execute a missed approach at minimums for the non-precision approach and an excessive rate of descent during the circle to land maneuver.NTSB BFO94LA117Accident · No injuriesLimited investigationFinal reportBeech F33A · Quarryville, PAThe pilot's failure to touchdown at the proper point and his delayed remedial action. A factor related to the accident was a tailwind.NTSB CHI94LA026Accident · Minor injuriesLimited investigationFinal reportBeech F33A · Saint Paul, MNother maintenance personnel's improper maintenance installation and fuel system line fitting undertorqued. Factors related to the accident were the dark night, along with the fence and posts which were contacted.NTSB LAX93FA377Accident · 3 fatalField investigationFinal reportBeech F33A · Baker, CAA loss of control for undetermined reason(s).NTSB CHI93LA261Accident · No injuriesLimited investigationFinal reportBeech F33A · Kahoka, MOThe pilot's premature liftoff. The soft runway condition was a factor.NTSB MIA93FA129Accident · Serious injuriesField investigationFinal reportBeech F33A · Oxford, MSLoss of engine power for undetermined reasons. The lack of suitable terrain for a forced landing was a factor.NTSB LAX93LA036Accident · Minor injuriesLimited investigationFinal reportBeech F33A · Phoenix, AZThe dual students premature retraction of the landing gear during the takeoff portion of a touch and go, and, the inadequate supervision of the flight by the instructor pilot. Factors which contributed to the accident were the deactivation of the landing gear…NTSB DEN93LA001Accident · Minor injuriesLimited investigationFinal reportBeech F33A · Steamboat Sprgs, COThe pilot's selection of an unsuitable landing area when a suitable forced landing area was available. A factor was: fuel starvation for unknown reasons.NTSB NYC92LA125Accident · Minor injuriesLimited investigationFinal reportBeech 33A · Farmingdale, NJThe pilot's improper recovery from a bounced landing which resulted in collapsing of the nose gear. A factor in the accident was gusting cross winds.NTSB LAX92LA153Accident · 2 fatalLimited investigationFinal reportBeech F33A · Payson, AZThe pilot's poor preflight planning/preparation by intentionally flying into known adverse weather and his poor in-flight decision by not flying to an alternate airport when the airplane began to encounter icing. Contributing to this accident was the icing…NTSB CHI92LA117Accident · No injuriesLimited investigationFinal reportBeech F33A · Langdon, NDFailure of the pilot to fully extend the landing gear using manual procedures after an electrical system failure. A factor associated with the accident is the pilot misreading a published emergency procedure.NTSB ATL92LA004Accident · Serious injuriesLimited investigationFinal reportBeech F33A · Franklin, NCThe pilot's failure to lower the landing gear resulting in a gear up contact with the runway, and the eventual loss of control of the airplane.NTSB LAX91FA329Accident · 4 fatalField investigationFinal reportBeech F33A · Earp, CAThe pilot's failure to maintain adequate airspeed, while maneuvering during a low pass, which resulted in a stall. A factor related to the accident was: lack of altitude to recover from the stall.NTSB LAX91LA258Accident · No injuriesLimited investigationFinal reportBeech F33A · Mobile, AZThe failure of the pilot of the other aircraft to exit the runway onto the taxiway at a speed sufficient to stop prior to colliding with the stopped aircraft.NTSB LAX91LA258Accident · No injuriesLimited investigationFinal reportBeech F-33A · Mobile, AZThe failure of the pilot of the other aircraft to exit the runway onto the taxiway at a speed sufficient to stop prior to colliding with the stopped aircraft.NTSB LAX91LA187Accident · No injuriesLimited investigationFinal reportBeech F33A · Goodyear, AZThe pilot's failure to ensure that the airplane's landing gear was extended by the passenger who he was allowing fly the airplane. A contributing factor related to the pilot's inadequate supervision of the passenger.NTSB CHI91FA126Accident · 2 fatalField investigationFinal reportBeech F.33A · Chippewa Falls, WIThe first pilot's continued flight in known adverse weather. Factors in the accident were the first pilot's poor weather evaluation, the second pilot's complacency and the first pilot's self induced pressure to complete a checkout in model.NTSB ATL91LA071Accident · No injuriesLimited investigationFinal reportBeech F33A · Chamblee, GAThe hole in the airport taxiway, which was created by the erosion of soil beneath the taxiway, and the failure of the airport to inspect and maintain ditches which run beneath the runways and taxiways.NTSB DEN91FA049Accident · 2 fatalField investigationFinal reportBeech F33A · Sterling, COPoor judgement of the pilot and his misjudgement of altitude while buzzing over glassy water. His lack of visual ques to judge altitude over glassy water was a related factor.NTSB NYC91FA080Accident · Serious injuriesField investigationFinal reportBeech F-33A · West Brookfield, MAThe decision of the pilot to fly the airplane in conditions that prevented him from seeing and avoiding higher terrain. Factors related to the accident were the pilot's decision to not follow the instrument approach into palmer, and the reduced visibility due…NTSB SEA91LA050Accident · 4 fatalLimited investigationFinal reportBeech F33A · Ogden, UTThe pilot elected to fly into known adverse weather and encountered icing conditions. Contributing to the accident was the pilot's inadequate evaluation of the weather and a loss of engine power for undetermined reasons.NTSB LAX91LA017Accident · Minor injuriesLimited investigationFinal reportBeech F33A · Mobile, AZA fuel flow interruption due to a fuel system seal fragment becoming lodged in the fuel control unit and the manufacturer's inadequate quality control procedures.NTSB CHI90LA270Accident · Serious injuriesLimited investigationFinal reportBeech F-33A · Osage Beach, MOThe pilot's failure to establish a proper glide path, resulting in contact with trees short of the intended runway.NTSB CHI90LA115Accident · Minor injuriesLimited investigationFinal reportBeech F33A · Milwaukee, WIThe utilization of improper procedures on the part of the pilot in command by attempting to execute a coupled approach outside the parameters of the autopilot.NTSB LAX90LA147Accident · No injuriesLimited investigationFinal reportBeech F-33A · Goodyear, AZThe pilot's failure to follow directives and his misjudgement of distance. Contributing to the accident was the airport management's failure to ensure that the building did not pose a hazard.NTSB LAX90LA146Accident · No injuriesLimited investigationFinal reportBeech F33A · Yuba City, CAA dog suddenly running onto the active runway in front of the aircraft resulted in a collision and substantial airframe damage.NTSB LAX90FA088Accident · 1 fatalField investigationFinal reportBeech F-33A · Oro Valley, AZThe pilot's poor judgement in performing low level aerobatic maneuvers.NTSB LAX90FA008Accident · 3 fatalField investigationFinal reportBeech F33A · Goodyear, AZThe inflight separation of one propeller blade due to a fatigue fracture of undetermined origin, and failure of the pilot to maintain control of the aircraft during an attempt to return to the runway. A factor in the accident was the oil covered windsheild,…NTSB NYC89LA162Accident · No injuriesLimited investigationFinal reportBeech F33A · Waterville, METhe pilot's disregard of NOTAMS and the excessive landing speed which resulted in a long landing roll.NTSB MIA89LA126Accident · No injuriesLimited investigationFinal reportBeech F-33A · Reddington Bch., FLLoss of engine power for undetermined reasons.NTSB DEN89LA095Accident · No injuriesLimited investigationFinal reportBeech F33A · Lamar, COFailure of an alternator bearing which resulted in total loss of electrical power after the battery became discharged, and failure of the pilot to insure the gear was fully extended during a precautionary landing. The pilot's lack of familiarity with the gear…NTSB ATL89FA113Accident · 1 fatalField investigationFinal reportBeech F33A · Ashland, ALThe pilot continued VFR flight into instrument meteorological conditions (IMC). Factors related to the accident were: high terrain, the adverse weather conditions, and trees.NTSB LAX88DUJ03Accident · No injuriesFinal reportBeech F33A · Goodyear, AZDuring an instructional flight, after takeoff, at 300 feet, the pilot and student said they heard a loud bang. The engine experienced a loss of power and the pilot noted that the top of the engine cowling was gone. A forced landing was made off the runway.…NTSB NYC88FA032Accident · 2 fatalField investigationFinal reportBeech F-33A · Forked River, NJThe pilot and passenger departed white plains, new york on a VFR flight to kill devil hills, north carolina. Search efforts were initiated when the aircraft failed to arrive at its destination. A witness in a hunting camp near the crashsite saw the aircraft…NTSB NYC88LA008Accident · 1 fatalLimited investigationFinal reportBeech F-33A · Concord, NHThe plt obtained a telephone wx briefing then filed an IFR flt plan for a 1030 EDT departure fm Concord municipal airport. The plt rptd off Concord at 800 ft and climbing at 1047. Manchester departure control acknowledged, assigned a transponder code, and…NTSB LAX87FA121Accident · 4 fatalField investigationFinal reportBeech F33A · Anza, CAThe non-instrument rated plt & 3 pax planned a pleasure flt to mx. The weather was below VFR minimums however the plt elected to attempt the flt. Several minutes after departure the acft was observed to enter an area where it was snowing, the cloud base was…NTSB LAX86FA057Accident · 1 fatalField investigationFinal reportBeech F33A · Sacramento, CAOn December 4, 1985 at 2230 PST, a Beech F33A, operated by the owner, collided with trees during a missed approach at Sacramento metropolitan airport, Sacramento, California, while on a business flight. Instrument meteorological conditions prevailed at the…NTSB DEN86LA019Accident · No injuriesLimited investigationFinal reportBeech F33A · Santa Teresa, NMThe plt reported the cylinder head temp began 'falling back out of green' shortly after takeoff. The plt reversed direction & landed at the arpt, but failed to extend the gear, substantially damaging the acft. The investigation of theeng revealed the exhaust…NTSB LAX85FA213Accident · 1 fatalField investigationFinal reportBeech F33A · Goleta, CAWhen the plt was advised the destn arpt (santa ynez) was directly ahead at 12 mi, he requested a freq change & radar svc was terminated. About 9 min later, he reestablished radio contact (with ARTCC) & reported he was not sure of his psn. The controller told…NTSB DEN84LA220Accident · No injuriesLimited investigationFinal reportBeech F33A · Glen Canyon, UTAccording to the plt, a slightly higher than normal apch speed with partial flap extension was used for the apch due to the turbulance and wind gusts to 25 KTS. After crossing the threshold at 20 to 30 ft AGL the flare resulted in what the pilot described as…NTSB NYC84LA174Accident · No injuriesLimited investigationFinal reportBeech Bonanza F33A · Tarentum, PAPlt made lndg apch to rwy 02 at 95 mph, flaps one-third down and rt wing down for wind compensation. Plt stated winds were at 090 deg. At 30 ft above the rwy the acft encountered a sudden gust of wind from 270 deg. The acft drifted to thert side of the rwy…NTSB CHI84LA082Accident · Minor injuriesLimited investigationFinal reportBeech BE-33A · Crystal, MNThe acft collided with trees and a residence near the destination airport after experiencing a total non-mechanical loss of power resulting from fuel starvation. The pilot reported he had estimated the fuel on board by a visual inspection of the tanks. This…NTSB LAX83LA406Accident · No injuriesLimited investigationFinal reportBeech F33A · San Carlos, CAThe plt stated that during the final approach sequence he encountered a gust of wind followed by immediate sinking of the acft, causing the acft to bounce. During the recovery from the bounced landing, the nose gear struck the rwy & collapsed.NTSB CHI83LA171Accident · No injuriesLimited investigationFinal reportBeech F33A · Peoria, ILPlt forgot to lower landing gear.NTSB MKC82IA071Incident · No injuriesIncident investigationFinal reportBeech F33A · Chesterfield, MOWhen the aircraft was returning for landing, the pilot selected gear down and stated that he felt it extend but could not recall seeing the green gear down lights because he was scanning for traffic. Shortly afterwards he experienced a rapid electrical power…NTSB MIA82DA099Accident · No injuriesFinal reportBeech F33A · Ft. Lauderdale, FLDuring the landing roll, the landing gear retracted. The pilot recommended that the gear retract lever be located higher on the panel and not near the flap or cowl flap switch.NTSB MIA82DA073Accident · No injuriesFinal reportBeech F33A · West Palm Beach, FLPersonnel on duty in the tower observed the aircraft bounce during landing. They stated that the nose gear appeared to collapse on the final touchdown. The pilot stated that he felt a vibration when the nose gear contacted the runway. He stated that pulled…NTSB ATL82FKQ08Accident · Serious injuriesClosedBeech F33A · Grenada, MSNTSB CHI81FA063Accident · 1 fatalClosedBeech F33A · Spring Valley, ILNTSB LAX81DUJ59Accident · No injuriesClosedBeech F33A · Goodyear, AZ
Back to Beech F33A