NYC90LA014 · Cessna T337G
Cessna T337G · Accident: airframe, component or system failure on approach
From Fulton County Airport Brown Field (FTY) to Allegheny County Airport (AGC)
Event
- NTSB case
- NYC90LA014
- 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
- Accident
- 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
- 0
- 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
- General aviation
- 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
Cessna T337G
- Aircraft type
- Cessna 337
- 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
- N197
- Operator
- Robert A. Harder · private individual
- Onboard fatalities
- Unknown
- Route
- From Fulton County Airport Brown Field (FTY), Atlanta, GATo Allegheny County Airport (AGC), West Mifflin, PA
- 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 91: General Aviation
- 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
- Approach · VFR pattern final
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel exhaustion; Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Fluid, fuel › Exhaustion
- Pilot in command › Diverted attention
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT DIVERTED TO ALLEGHENY COUNTY AIRPORT TO AVOID WEATHER AND TO REFUEL. DURING A VECTOR TO FINAL APPROACH, THE LANDING GEAR WOULD NOT EXTEND. FOR ABOUT 1 HR AND 10 MIN, THE PILOT TRIED TO EXTEND THE LANDING GEAR. HE DECIDED TO MAKE A GEAR UP LANDING; HOWEVER. BEFORE REACHING THE AIRPORT, FUEL TO BOTH ENGINES WAS EXHAUSTED. THE AIRPLANE CRASHED INTO TREES SHORT OF THE RUNWAY. AN INVESTIGATION SHOWED THERE WAS A HYDRAULIC LEAK ON THE NOSE GEAR DOOR ACTUATOR AND A SUBSEQUENT LOSS OF HYDRAULIC FLUID. AFTER THE LEAK WAS REPAIRED AND THE SYSTEM WAS FILLED WITH HYDRAULIC FLUID, THE LANDING GEAR OPERATED WITH USE OF THE POWER PACK OR HAND PUMP.
Probable cause
THE PILOT'S IMPROPER IN-FLIGHT PLANNING AND DECISION, AND DIVERTING OF HIS ATTENTION, WHICH RESULTED IN FUEL EXHAUSTION TO BOTH ENGINES. DARKNESS AND TREES IN THE EMERGENCY LANDING AREA WERE RELATED FACTORS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC90LA014
- Event ID
- 20001213X29699
- Case number
- NYC90LA014
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1989-10-19.
- API snapshot SHA-256: c13371ead1500d5b9cda80d4d02f519203a3d0ba92f088a5792bbdef5a6eef9b; retrieved 2026-09-21T15:48:07.769Z.