FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA08FA078 · Lancair LC41 550FG

16 Feb 2008 · Portland, OR, United States

Lancair LC41 550FG · Accident: controlled flight into terrain/object (CFIT) on approach

From Crater Lake-Klamath Regional Airport (LMT) to Portland International Airport (PDX)

Report a problem

Event

NTSB case
SEA08FA078
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
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
Instrument Meteorological Cond

Lancair LC41 550FG

Aircraft type
Lancair LC41
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
N621ER
Operator
Richard E. Otoski · private individual
Onboard fatalities
Unknown
Route
From Crater Lake-Klamath Regional Airport (LMT), Klamath Falls, ORTo Portland International Airport (PDX), Portland, OR
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 · IFR missed approach
Defining eventThe 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
Controlled flight into terrain/object (CFIT)
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

  • Personnel issues › Action/decision

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

NTSB narrative

Prior to initiating the first ILS approach to runway 10R, the pilot was advised by the tower controller that the runway visual range (RVR) was 600 feet, followed by being given a landing clearance. A little more than 2 minutes later the pilot declared a missed approach and was given radar vectors for a second ILS approach. After turning inbound on the localizer the pilot was advised that the runway visual range was 600 feet, midfield 800 feet, and roll out 800 feet. The pilot was then cleared to land. When the tower controller observed the airplane turning to the south of the runway on her radar display, she issued missed approach instructions, which was followed by an inaudible transmission. There were no further transmissions from the pilot. The airplane impacted the top of an 85-foot tall tree with its right wingtip, 3,200 feet southeast of the approach end of the runway, then continued on the collision course before impacting the ground about 845 feet from the initial impact point with the tree. The airplane was subsequently consumed by fire. The weather minimums for the approach required a ceiling of 200 feet and an RVR of 1,800 feet or one-half mile; the decision altitude was 224 feet msl. The FAA published missed approach procedure instructed the pilot to climb to 900 feet, then climbing right turn to 4,000 feet, intercept the 160 degree radial of the VORTAC, and proceed to a DME fix and hold. The airplane's turn to the southeast was consistent with the missed approach course of 160 degrees; however, a climb to 900 feet is required prior to commencing the right turn, as outlined on approach plate's missed approach instructions. It appears the pilot likely misinterpreted the missed approach instructions by making the right hand turn prior to initiating a climb to 900 feet, which resulted in the subsequent impact with the tree. No preimpact anomalies were found during an examination of the airframe and engine. The airplane's avionics components revealed that they were too thermally and impact-damaged to provide any data. No anomalies were found during a post accident examination of the instrument landing system components.

Probable cause

The pilot's failure to follow the missed approach procedure. Contributing to the accident were the fog and below landing minimums visibility conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA08FA078
Event ID
20080222X00228
Case number
SEA08FA078
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 0a58bf661979c43ebdc7dfc8bf675acd76b98aee781ec6960ea7b403eb7c91ef; retrieved 2026-09-13T18:57:01.511Z.