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 ('7100610', '7104216')
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 ('7100610', '7104216')
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 ATL05CA080Accident · No injuriesData collectionFinal reportPiper J4E · Akron, ALThe pilot's premature liftoff and his failure to attain adequate airspeed which resulted in a stall/mush. Also causal was the pilot's delay in aborting the takeoff.NTSB SEA04LA084Accident · No injuriesLimited investigationFinal reportPiper J4/E · Bigfork, MTA loss of engine power due to fuel exhaustion while in cruise flight as a result of inadequate preflight planning / preparation. Factors contributing to the accident were the short landing field and trees.NTSB MIA92LA048Accident · Serious injuriesLimited investigationFinal reportPiper J-4E · Timmonsville, SCTotal loss of engine power (nonmechanical) due to inadequate fuel consumption calculation by the pilot-in-command, resulting in an engine failure due to fuel exhaustion, a forced landing, and in-flight collision with terrain.NTSB CHI84LA075Accident · No injuriesLimited investigationFinal reportPiper J-4E · White Bear Lake, MNThe ski-equipped acft suffered landing gear failure during a landing on a snow covered turf rwy. The landing gear separated when an attach point failed. The plt gave fatigue failure as a reason for the failure.NTSB CHI84LA021Accident · No injuriesLimited investigationFinal reportPiper J4E · Troy, MIThe acft departed the side of the rwy during landing and nosed over. A private pilot was being accompanied by a commercial pilot whose CFI cirtificate had expired. During landing roll the private pilot began 's' turns for better forward visibility. The…NTSB SEA80FA043Accident · 2 fatalClosedPiper J4E · Mountain Home, IDNTSB FTW80DRG28Accident · No injuriesClosedPiper J4 · Eagle Pass, TXNTSB FTW76DRG21Accident · No injuriesClosedPiper J4E · Port Lavaca, TXNTSB OAK72AP026Accident · 2 fatalClosedPiper J4E · Vacaville, CANTSB LAX70D0056Accident · No injuriesClosedPiper J4E · Yucca Valley, CANTSB IAD69F0104Accident · Serious injuriesClosedPiper J4E · Sharpsburg, NCNTSB ANC69D0084Accident · No injuriesClosedPiper J4E · Fairbanks, AKNTSB CHI69F0048Accident · No injuriesClosedPiper J4E · Edinburg, INNTSB CHI68D0248Accident · No injuriesClosedPiper J4E · Streator, ILNTSB ANC68F0018Accident · No injuriesClosedPiper J4E · Soldotna, AK
Back to Piper J4E