FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA83LA209 · Bellanca 14-19-3

8 Jan 1983 · Goldendale, WA, United States

Bellanca 14-19-3 · Accident: in flight encounter with weather en route

From Yakima Air Terminal McAllister Field (YKM) to Long Beach, CA

Report a problem

Event

NTSB case
SEA83LA209
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
2 · 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
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

Bellanca 14-19-3

Aircraft type
Bellanca 14
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
N8807R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Yakima Air Terminal McAllister Field (YKM), Yakima, WATo Long Beach, CA
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
En route · cruise
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
In flight encounter with weather
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
Destroyed

Cause areas

  • Pilot in command › Clearance, not maintained
  • Pilot in command › In-flight planning/decision, inadequate
  • Pilot in command › Preflight planning/preparation, inadequate

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The aircraft failed to arrive at its destination and was declared missing on January 10, 1983. Search and rescue efforts along the route of flight were suspended on January 15, 1983. An area forecast indicated a series of fronts moving across the Pacific Northwest. The forecast indicated ceilings below 1,000 feet and visibility below 3 miles in fog. Additionally, the forecast for Oregon and Washington east of the Cascade mountain range revealed thin broken to overcast clouds from 5,000 to 7,000 feet, occasional visibility between 3 and 5 statute miles in light rain and fog, and mountains occasionally obscured in clouds and precipitation. The outlook was for marginal visual flight rule conditions. There was no record of the pilot requesting a weather briefing, but prior to his departure air traffic control advised the pilot that SIGMETS for severe turbulence and icing in clouds were in effect along the route of flight. Air traffic control subsequently recommended that the pilot contact Seattle Flight Watch for detailed information; there is no record of the pilot contacting Seattle Flight Watch. Subsequent to departure communications with Yakima tower, there was no further contact with the accident airplane. On August 30, 2005, the airplane wreckage was located approximately 15 nautical miles north-northwest of Goldendale, Oregon. The first impact point was evidenced by damage to the top of a tree grove prior to the main wreckage impact area. The energy path extended approximately 340 feet on a magnetic heading of 138 degrees. Photographs revealed that the airplane was destroyed. The cockpit was unrecognizable, with two sections of a seat located 75 feet from the main wreckage area. The engine came to rest in an upright position separated from the airframe and both propeller blades remained attached to the propeller flange. There was no postcrash fire and no planned recovery of the wreckage.

Probable cause

The pilot's inadequate preflight and in-flight planning, which resulted in flight into adverse weather conditions and clearance from trees not maintained. Factors contributing to the accident included the clouds, low ceilings, and turbulence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA83LA209
Event ID
20051208X01953
Case number
SEA83LA209
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, coordinates. 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: 35d9316c4229ce93132681f21c2cccb013709d9fb65923709b14ee7ac45a0545; retrieved 2026-09-21T07:17:27.774Z.