NTSB investigations: Fokker F.28 MK 0100

6 cases on aircraft the registry lists as Fokker F.28 MK 0100, where the first occurrence was “Airframe/component/system failure/malfunction”. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.

Defining event

Finding

Phase of flight

Aircraft model

Cases per year

19902026

NTSB investigations: Fokker F.28 MK 0100 per year, 1990–2026: 6 cases
1990	1
1997	1
2001	3
2002	1

Where

Open the map

Latest cases

Query with SQL

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_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1 WHERE c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('4990807') AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 130)) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

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_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
  WHERE c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('4990807')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 130))
  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_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('4990807')
    AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 130))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

Run 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 CHI02IA270Incident · No injuriesIncident investigationFinal reportFokker 100 · Minneapolis, MNThe improper installation of the #2 main landing gear wheel, including the axle nut not being properly torqued and safetied, which resulted in the wheel separation during takeoff.Sep 5, 2002 · N1473K · Minor damage NTSB FTW02FA003Accident · No injuriesField investigationFinal reportFokker F28 Mk 0100 · DFW Airport, TXThe collapse of the nose landing gear as a result of the failure of company maintenance personnel to follow the proper procedures for a towing the airplane with an unsafe nose landing gear indication. Contributing factors were the inadequate communication…Oct 3, 2001 · N1448A · Substantial damage NTSB FTW01FA127Accident · No injuriesField investigationFinal reportFokker F28 Mk 0100 · DFW Airport, TXA forging fold that was introduced during the manufacture of the right main landing, which resulted in a fatigue crack in the right main landing gear cylinder, and its subsequent failure during landing.May 23, 2001 · N1419D · Substantial damage NTSB CHI01IA102Incident · No injuriesIncident investigationFinal reportFokker F28 MK 0100 · Montreal, Canadathe inaccurate aircraft deicing service the ground personnel performed alowing fluid injestion and the auxiliary power unit's turbine failure while standing. A factor was the auxiliary power unit's overspeed.Mar 6, 2001 · N1426A · Minor damage NTSB MIA98FA025Accident · No injuriesField investigationFinal reportFokker F100 · Charlotte, NCImproper written instructions (job/task card) by company maintenance personnel. The procedures did not reflect the correct manufactures maintenance manual servicing procedure, and did not ensure that the proper tool (replenishing gun) was available for the…Nov 7, 1997 · N865US · Substantial damage NTSB ATL91IA017Incident · No injuriesIncident investigationFinal reportFokker F28 MK0100 · Atlanta, GAFrozen moisture in the stabilizer actuator hydraulic servo valve which resulted in reduced movement of the servo valve and limited its ability to respond to flight control inputs. The lack of response from the servo valve resulted in the jammed stabilizer…Nov 11, 1990 · N850US · No damage