FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14FA278 · Hermann Bjorn LANCAIR IV

7 Jun 2014 · Duluth, MN, United States

Hermann Bjorn LANCAIR IV · Accident: loss of control in flight en route

From Duluth International Airport (DLH) to Goose Bay Airport (CYYR)

Report a problem

Event

NTSB case
CEN14FA278
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
Visual Meteorological Cond

Hermann Bjorn LANCAIR IV

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
N86NW
Operator
Alexander G. Obersteg · private individual
Onboard fatalities
Unknown
Route
From Duluth International Airport (DLH), Duluth, MNTo Goose Bay Airport (CYYR), Goose Bay
Aircraft age
About 9 years (built 2005)
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 · climb to cruise
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
Loss of control in flight
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

  • Aircraft › Aircraft systems
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

The pilot/owner was ferrying the airplane from the United States to Europe, and he had installed an auxiliary fuel bladder in place of the rear seat. Before takeoff, the airplane's fuel tanks were topped off, and 60 gallons of fuel were added to the auxiliary fuel bladder. The estimated weight of the airplane during takeoff was about 509 lbs over its maximum gross weight. The estimated center of gravity (CG) of the airplane was 93.2, which was near the aft limit of the CG range.

The flight departed in marginal visual flight rules conditions and, soon after takeoff, climbed into instrument flight rules (IFR) conditions while passing through 1,000 ft above ground level. Air traffic control (ATC) cleared the pilot to fly a northeasterly heading and climb to 12,000 ft, but the pilot did not acknowledge the instruction, and radar track data indicated that the airplane turned right within 1 minute after departure. ATC instructed the pilot to turn back on course, and the pilot complied. The airplane continued on course for about 1.5 minutes, but then it turned right again while still in a climb. ATC instructed the pilot to turn back on course, but the pilot did not respond. The airplane continued to turn right, reached a maximum altitude of about 6,600 ft, and then entered a steep, descending right turn. ATC instructed the pilot to climb immediately, but there was no response, and the airplane continued the steep descending turn and impacted a lake about 5 minutes after departure.

A comparison of the radar track data with the flight data recovered from the airplane's primary flight display (PFD) and multifunction display revealed discrepancies between the two data sources regarding airspeed, bank angle, heading, wind speed, and wind direction, indicating that erroneous information was being displayed on the PFD during the flight. Specifically, the flight data indicated periods of straight and level flight when the radar track data indicated the airplane was banking and changing heading. The erroneous information would have made it difficult for the pilot to control the airplane and navigate effectively in IFR conditions. The reason for the erroneous flight data could not be determined.

The pilot's toxicology report indicated 0.146 ug/ml diphenhydramine (a sedating antihistamine) in cavity blood, which was above the therapeutic range of 0.0250 to 0.1120 ug/ml. Although diphenhydramine undergoes postmortem redistribution, the postmortem level detected suggests that the pilot likely had impairing levels of diphenhydramine in his system at the time of the accident. To maintain control of the airplane, the pilot would have needed to recognize that the PFD display was faulty and use the information from the standby attitude indicator, turn and bank indicator, and magnetic compass. However, it is likely that diphenhydramine, which impairs cognitive and psychomotor performance, diminished the pilot's ability to recognize and manage the erroneous PFD indications.

The pilot's failure to acknowledge the clearance to turn to the northeast and climb to 12,000 feet only a few seconds after he initiated contact with ATC suggests that his attention was diverted for some reason about that time. The pilot verbally acknowledged and responded to a subsequent call to return to course. However, after about 1.5 minutes the airplane again deviated from course and entered a steep descending turn, most likely due to the pilot experiencing spatial disorientation as a result of the erroneous heading and bank angle information on the PFD and his ineffective use of standby flight instruments in restricted visibility conditions. The airplane's aft CG and over gross weight condition would have reduced the airplane's longitudinal stability, and this likely also contributed to the loss of control.

Probable cause

The pilot's failure to maintain airplane control while operating in instrument flight rules (IFR) conditions, which was due to spatial disorientation resulting from erroneous heading and bank angle information shown on the primary flight display. Contributing to the accident were the pilot's impairment due to diphenhydramine and his improper decision to operate in IFR conditions with the airplane over gross weight and at an aft center of gravity.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14FA278
Event ID
20140609X83225
Case number
CEN14FA278
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, 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: 5862e0b65a079b3f27b3b6241653ca1374f3593e11e298dce98f4104e411aed9; retrieved 2026-09-14T17:19:19.947Z.