SEA84FA123 · Piper PA-34-200
Piper PA-34-200 · Accident: in flight collision with object on approach
From 60S · Vancouver, WA to Southwest Oregon Regional Airport (OTH)
Event
- NTSB case
- SEA84FA123
- 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
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Piper PA-34-200
- Aircraft type
- Piper PA-34
- 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
- N1067U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 60S · Vancouver, WATo Southwest Oregon Regional Airport (OTH)
- 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 135: Air Taxi & Commuter
- 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 · IFR missed approach
- 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 collision with object
- 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 › In-flight planning/decision, improper
- Pilot in command › Missed approach, delayed
- Pilot in command › Proper altitude, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT WAS CLEARED FOR AN ILS RWY 4 APCH WHILE 9 MILES NORTH OF OTH (NORTH BEND) VOR. INSTRUCTIONS WERE GIVEN TO CROSS OTH VOR AT OR ABOVE 3700 FT MSL. 14 MIN LATER, THE PLT REPORTED TO NORTH BEND FSS 'MY NEEDLE DOESN'T SEEM TO BE MOVING ON MY LOCALIZER HERE UH YOU KNOW MY LOCATION.' INDICATIONS OF NAV/COM DIFFICULTIES CONTINUED. ACFT WAS CLEAREDBY ARTCC TO DESCEND FROM 5000 FT TO 3000 FT HEADING 360 DEGS WHILE 11 MILES SW OF ARPT. AFTER A HEADING CHANGE TO 035 DEG, THE PLT STATED 'I GOT IT CENTERED NOW'. AT THE OUTER MARKER HE SAID 'I'M A LITTLE HIGHER TWO THOUSAND I'LL TRY TO GET DOWN.' ARPX 2 MIN LATER, THE PLT REPORTED AN ALT OF 800 FT. THE ACFT CRASHED IN A HILLY WOODED AREA APRX 3 MI NNE OF THE ARPT. A CHIEF PLT & AN FAA EXAMINER REPORTED THE PLT'S IFR PERFORMANCE WAS UNSATISFACTORY IN A PART 135 CHECKRIDE. ACCORDING TO ANOTHER PLT AND MAINTENANCE RECORDS, N1067U HAD A HISTORY OF DISCREPANCIES WITH THE NAV EQUIP. A COMPANY PLT STATED THE COMPANY PUT PRESSURE ON THE PLTS TO FLY ACFT WHICH SOMETIMES WERE NOT AIRWORTHY.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA84FA123
- Event ID
- 20001214X40126
- Case number
- SEA84FA123
- 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: 6793a193725f4f45db126dd6561572f2e5e64ca6707a4c211e3a1ff195ae2ac5; retrieved 2026-09-18T14:28:20.152Z.