Globe GC-1A
NTSB investigations · 19
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 ('9230102')
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 ('9230102')
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 CEN18LA012Accident · 1 fatalLimited investigationFinal reportGlobe GC 1A · Los Lunas, NMThe loss of directional control during takeoff and impact with a steel culvert.NTSB ERA13FA032Accident · 2 fatalField investigationFinal reportSwift Museum Foundation GC-1A · East Moriches, NYThe failure of the pilot to maintain airspeed, while attempting a precautionary landing for reasons that could not be determined from the available evidence. Contributing to the accident was the pilot’s pitch-up reaction to birds that took flight during his…NTSB ATL05CA119Accident · Minor injuriesData collectionFinal reportGlobe GC-1B · Athens, TNThe pilot's improper landing flare, which resulted in a hard landing.NTSB IAD97LA066Accident · No injuriesLimited investigationFinal reportGlobe GC-1-A · Wilmington, OHfailure of the pilot to maintain directional control of the airplane during the landing, which resulted in a collision with trees. Related factors were: the crosswind, and lack of experience in the make and model of airplane.NTSB LAX87FA040Accident · Serious injuriesField investigationFinal reportGlobe GC-1A · Corona, CAThe plt of N621SR said that as he entered the pattern downwind he saw only one low wing acft which was just turning final for rwy 25. On short final the plt said he noticed the wing and cockpit of the other acft in his left side periphial vision one second…NTSB FTW84LA037Accident · No injuriesLimited investigationFinal reportGlobe GC-1A · Houston, TXThe plt was on a local flt from the weiser airpark arpt to the lakeside arpt. There was construction at the destination & the plt was unsure which rwy was in use. He made a go-around from his 1st apch. After UNICOM had clarified where the landing area was at,…NTSB MIA79FA083Accident · 1 fatalClosedGlobe Swift GC1B · Arcadia, FLNTSB LAX73FUJ67Accident · Minor injuriesClosedGlobe GC-1B · Flagstaff, AZNTSB MIA72AM110Accident · 1 fatalClosedGlobe GC-1B · Hanahan, SCNTSB IAD70AI060Accident · 1 fatalClosedGlobe GC-1B · Blue Ridge, VANTSB CHI69F0538Accident · Serious injuriesClosedGlobe GC-1B · Brohman, MINTSB CHI68F0578Accident · No injuriesClosedGlobe Swift GC-1B · W Lafayette, INNTSB MIA68D0172Accident · Minor injuriesClosedGlobe GC-1B · Arcadia, FLNTSB NYC67F0221Accident · Serious injuriesClosedGlobe GC-1A · East Taunton, MANTSB NYC67F0085Accident · No injuriesClosedGlobe GC-1B · Fairfield, NJNTSB MIA66F0398Accident · No injuriesClosedGlobe GC-1A · Orlando, FLNTSB NYC66F0034Accident · No injuriesClosedGlobe GC-1A · Allentown, PANTSB CHI66D0030Accident · Minor injuriesClosedSwift GC-1B · Linton, INNTSB MIA66F0132Accident · Serious injuriesClosedGlobe 6C-1A · Augusta, GA
Back to Globe GC-1A