Cessna 310C
NTSB investigations · 127
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 ('2074210')
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 ('2074210')
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 WPR16LA016Accident · No injuriesLimited investigationFinal reportCessna 310C · Primm, NVThe inadequate visual lookout by the pilots of both airplanes, which resulted in a midair collision. Contributing to the accident was the pilots' failure to tune to, monitor, and communicate over the common traffic advisory frequency their relative positions…NTSB WPR11LA092Accident · No injuriesLimited investigationFinal reportCessna 310C · Lancaster, CAThe pilot did not maintain an appropriate descent profile during the approach. Contributing to the accident was that the pilot did not follow checklist procedures.NTSB CEN10FA493Accident · 2 fatalField investigationFinal reportCessna 310C · Calhan, COThe pilots'failure to maintain control of the airplane which resulted in an inadvertent stall and spin.NTSB CEN10CA436Accident · Minor injuriesData collectionFinal reportCessna 310C · Ashdown, ARThe pilot’s loss of directional control during the takeoff roll and his lack of experience in the airplane.NTSB NYC06CA113Accident · No injuriesData collectionFinal reportCessna 310C · Allentown, PAThe pilot's failure to lower the landing gear during landing.NTSB CHI05LA140Accident · Serious injuriesLimited investigationFinal reportCessna 310C · Ray, MIThe loss of power on the left engine for undetermined reasons and the flightcrew's failure to maintain aircraft control following the loss of power.NTSB LAX04LA030Accident · No injuriesLimited investigationFinal reportCessna 310C · Los Angeles, CAThe pilot's misjudgment of distance and speed on the approach resulting in an overrun.NTSB MIA02LA034Accident · Minor injuriesLimited investigationFinal reportCessna 310C · Reidsville, GAImproper fuel management by the pilot resulting in loss of power in both engines, and the pilots lowering of the landing gear prior to having the runway made resulting in a hard landing short of the runway.NTSB DEN00LA116Accident · No injuriesLimited investigationFinal reportCessna 310C · Erie, COA sudden and unexpected encounter with a downdraft while on final approach. A factor was the transmission wire.NTSB DEN00LA066Accident · No injuriesLimited investigationFinal reportCessna 310C · Cedar City, UTThe failure of the right engine mixture control cable, which prevented the pilot from restarting the engine. Contributing factors were the pilot's failure to follow procedures by not feathering the right propeller, the rough terrain, and the high vegetation.NTSB ATL99LA032Accident · No injuriesLimited investigationFinal reportCessna 310C · Ft Myers, FLThe inadequate preflight inspection of the airplane by the pilot and subsequent malfunction of the nose gear strut, and the pilot's failure to follow the landing checklist.NTSB LAX98LA101Accident · Minor injuriesLimited investigationFinal reportCessna 310C · Lancaster, CAThe pilot's improper use of the mixture controls.NTSB FTW96LA224Accident · No injuriesLimited investigationFinal reportCessna 310C · Los Lunas, NMloss of total engine power due to fuel exhaustion for undetermined reason(s). The lack of suitable terrain for the forced landing was a related factor. The worn and leaking fuel system components and inadequate maintenance by unknown personnel were possible…NTSB MIA96LA062Accident · No injuriesLimited investigationFinal reportCessna 310C · Irvington, ALThe pilot's failure to maintain adequate airspeed during the landing flare, which resulted in a hard landing.NTSB LAX96LA034Accident · No injuriesLimited investigationFinal reportCessna 310C · Boulder City, NVthe pilot's improper aircraft handling during touchdown which resulted in the right wing and horizontal stabilizer dragging on the runway. The poorly planned landing approach was a factor.NTSB ATL94LA016Accident · No injuriesLimited investigationFinal reportCessna 310C · Charleston, SCThe failure of the right main landing gear to extend for undetermined reasons.NTSB CHI93FA267Accident · 4 fatalField investigationFinal reportCessna 310C · Norton, KSThe pilot's failure to maintain aircraft control due to alcohol impairment. Factors which contributed to the accident were: the pilot's intentional flight into adverse weather, fog, and the dark night.NTSB FTW92FA022Accident · 2 fatalField investigationFinal reportCessna 310C · Waller, TXThe loss of directional control as result of the velocity minimum control airspeed not being maintained. A factor was that the maneuver was initiated at an inadequate altitude too low for the pilot to recover.NTSB SEA90LA004Accident · No injuriesLimited investigationFinal reportCessna 310C · Redmond, ORPoor inflight planning, and the pilot did not maintain a proper glide path on final approach, nor perform proper corrective action. Factors related to the accident were: the pilot's attention was diverted due to an open cabin door and the partial loss of…NTSB LAX89LA177Accident · No injuriesLimited investigationFinal reportCessna 310C · Jackson, CAThe failure of the instructor pilot (pilot in command) to reject the takeoff after the loss of power on one engine when sufficient runway remained to stop the aircraft. Contributing to the accident was the disregard of the aircraft manual, failure to use the…NTSB CHI85FEX02Accident · Serious injuriesFinal reportCessna 310C · Greenfield, INWhile en route, the l eng suddenly lost power & would not restart, so the plt feathered the l prop. After letting it cool aprx 5 min, he tried restarting it again, but still was unable. He stated he thought he then secured (feathered) the l eng. The plt…NTSB CHI85LA038Accident · No injuriesLimited investigationFinal reportCessna 310C · Grayslake, ILThe plt reported that the landing was normal but the acft settled to the rwy with the gear up while the selector was in the down position. Post accident examination failed to reveal any malfunction of the retraction/extension assembly.NTSB CHI85FA005Accident · 1 fatalField investigationFinal reportCessna 310C · Allegan, MIThe non inst non multi-eng rated pvt plt/owner occupied the rt seat & employed the CFI for ferrying the newly purchased acft. From the start, the flt experienced comm difficulties & a compass system malfunction problem. ARTCC transcripts reveal that ATC was…NTSB MIA84LA118Accident · Serious injuriesLimited investigationFinal reportCessna 310C · Key West, FLWhile en route, the plt had switched from the main tanks to the aux tanks, then back to the main tanks. About 10 min later, both engs lost power. He was able to restart the right eng, but it lost power again. Subsequently, he ditched the acft at sea. Both…NTSB LAX83LA127Accident · Minor injuriesLimited investigationFinal reportCessna 310C · San Jose, CAThe plt reported that when he was taking off, he heard a noise, during gear retraction, that sounded to him like an explosion & the gear-up light did not illuminate. He then tried to extend the gear, but was unable to get a safe-down indication. He was able…NTSB FTW83LA021Accident · Minor injuriesLimited investigationFinal reportCessna 310C · Bastrop, LAThe pilot was preparing for an enroute landing when he got an unsafe gear light. While trouble-shooting, the left engine stopped. He feathered the left engine and almost immediately the right engine quit. The pilot failed to reach therunway during the power…NTSB ATL82DA250Accident · No injuriesFinal reportCessna 310C · Brunswick, GAThe pilot experienced an electrical failure inflight after takeoff. He hand-cranked the landing gear to the down and locked position prior to landing. After rolling approximately 200 feet, he left main gear collapsed. Examination of the landing gear revealed…NTSB NYC82DA182Accident · No injuriesFinal reportCessna 310C · Schroon Lake, NYThe brakes failed during landing roll and the aircraft went off the end of the runway damaging the prop and nose gear. The left brake was found inoperative and the right brake had excessively worn pucks.NTSB ATL82DA132Accident · No injuriesFinal reportCessna 310 · Allendale, SCThe pilot reported that before landing, the landing gear indicators showed that all gear were down and locked. However, on the landing roll-out, the left main gear collapsed as the nosewheel was lowered to the runway. Subsequently, the left wing, left…NTSB LAX81FVM26Accident · No injuriesClosedCessna 310C · Paso Robles, CANTSB DEN81FA015Accident · 1 fatalClosedCessna 310C · Encampment, WYNTSB DEN80FA008Accident · 2 fatalClosedCessna 310 · Tucumcari, NMNTSB LAX79DVD35Accident · No injuriesClosedCessna 310C · Hayward, CANTSB MIA79FKG55Accident · No injuriesClosedCessna 310C · Chamblee, GANTSB MIA79FKG23Accident · Serious injuriesClosedCessna 310C · Augusta, GANTSB FTW78FPJ36Accident · No injuriesClosedCessna 310C · Oklahoma City, OKNTSB MKC78FER22Accident · No injuriesClosedCessna 310C · Blaine, MNNTSB MIA78FLA11Accident · No injuriesClosedCessna 310C · Jacksonville, FLNTSB CHI76FEK25Accident · No injuriesClosedCessna 310 · Columbus, OHNTSB SEA76FYE48Accident · Minor injuriesClosedCessna 310 · Burlington, WANTSB NYC76DHJ22Accident · No injuriesClosedCessna 310C · New York City, NYNTSB MIA76FLD54Accident · No injuriesClosedCessna 310C · Kissimmee, FLNTSB NYC76FHA22Accident · No injuriesClosedCessna 310 · Allentown, PANTSB OAK76DVA40Accident · No injuriesClosedCessna 310C · Bakersfield, CANTSB MIA76OKT33Accident · No injuriesClosedCessna 310C · West End, Burkina FasoNTSB DEN7LAD004Accident · 1 fatalClosedCessna 310C · Springfield, CONTSB CHI75FEV22Accident · No injuriesClosedCessna 310C · Peoria, ILNTSB OAK75FVD16Accident · No injuriesClosedCessna 310C · Hayward, CANTSB LAX75AL008Accident · 2 fatalClosedCessna 310C · Holbrook, AZNTSB MIA75FLD01Accident · No injuriesClosedCessna 310C · Vero Beach, FL
Back to Cessna 310C