FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flying Boat Grumman G-73 incident

22 May 2001 · Fort Lauderdale, FL, United States

Grumman G-73 · Incident: airframe, component or system failure while taxiing

From PID · Paradise Island to Fort Lauderdale Hollywood International Airport (FLL)

Report a problem

Event

NTSB case
MIA01IA144
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Incident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Grumman G-73

Aircraft type
Grumman G-73
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N142PA
Operator
Flying Boat
Onboard fatalities
Unknown
Route
From PID · Paradise IslandTo Fort Lauderdale Hollywood International Airport (FLL), Fort Lauderdale, FL
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 121: Air Carrier
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Taxi
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Airframe, component or system failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Company maintenance personnel › Maintenance, improper

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airplane was taxing to the ramp when the right main landing gear collapsed. Examination of the landing gear revealed evidence of preexisting cracks. Review of paper work by company maintenance personnel revealed that components had been sent to a laboratory for examination. Upon return of the components the paperwork indicated that two components had been rejected due to cracks. Company maintenance personnel stated that unserviceable components had been tagged as serviceable and installed on an operational airplane which resulted in the subsequent failure and collapse of the right main landing gear.

Probable cause

The improper review of component records by company maintenance personnel of returned landing gear components from a laboratory for magnaflux and x-ray. This resulted in unserviceable components being tagged as serviceable, installation of unserviceable parts on an operational airplane, and subsequent failure/collapse of the right main landing gear during taxi.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA01IA144
Event ID
20010529X01018
Case number
MIA01IA144
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 6e2a935e1579d7d8960779f4ce63458cc9c29f3f467c739d62e3547b6d21ea3c; retrieved 2026-09-18T16:13:22.167Z.