FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA90LA054 · de Havilland DH 82A

20 Mar 1990 · White City, OR, United States

de Havilland DH 82A · Accident: undershoot on approach

From Rogue Valley International-Medford Airport (MFR) to an unrecorded destination

Report a problem

Event

NTSB case
SEA90LA054
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
1 · 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

de Havilland DH 82A

Aircraft type
de Havilland DH-82
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
N353FG
Operator
Unknown
Onboard fatalities
Unknown
Route
From Rogue Valley International-Medford Airport (MFR), Medford, ORTo not recorded
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
Undershoot
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
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
Substantial

Cause areas

  • Pilot in command › Remedial action, delayed

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

NTSB narrative

THE PILOT ENTERED A HIGH TRAFFIC PATTERN FOR LANDING AND REDUCED THE THROTTLE TO MINIMUM POWER SETTING. HE SLOWLY INCREASED THE THROTTLE TO CORRECT FOR AN UNDER SHOOT ANGLE OF DESCENT ON SHORT FINAL APPROACH AND THE ENGINE DID NOT INSTANTLY RESPOND. HE FURTHER INCREASED THE THROTTLE AND ENGINE POWER INCREASED ABOUT THE TIME THE AIRCRAFT STRUCK TREES 250 FT FROM THE END OF THE AIRSTRIP.

Probable cause

PILOT'S DELAY IN TAKING REMEDIAL ACTION TO PREVENT AN UNDERSHOOT. HIS MISJUDGEMENT OF DISTANCE AND ALTITUDE ON FINAL APPROACH WERE RELATED FACTORS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA90LA054
Event ID
20001212X22819
Case number
SEA90LA054
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: 1860db120e9ea45ab1b3419a549fb9e04d04c8a3d75aae409a38e1c5c544bf6f; retrieved 2026-09-21T02:52:31.441Z.