Casualties unknown

Nighttime Go-Around Failure Results in Tree Impact (N2897U)

Portland, OR, US

On May 30, 1983, a Cessna 172D (registration N2897U) was involved in an aviation accident near Portland, OR. Investigators recorded the probable cause as: The pilot's failure to execute a timely go-around during a night landing, which resulted in the aircraft colliding with trees while attempting to depart from the runway. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 2026-06-23Data APIEditorial standards

A pilot attempted a go-around during a night landing but collided with trees at the departure end of the runway after floating past the threshold.

What happened

The accident occurred during nighttime operations while the aircraft was attempting to land on Runway 34. As the pilot descended toward the runway, he observed that the aircraft had traveled more than half its length without contacting the ground, indicating a significant float. Recognizing that a safe landing was no longer possible, the pilot initiated a go-around procedure.

However, during the initial climb out from the departure end of the runway, the aircraft collided with trees. The impact caused the aircraft to crash. The pilot reported that several of the threshold and runway lights at the approach end were not illuminated or were missing, which may have affected his depth perception and situational awareness during the final approach.

The investigation

Investigation details regarding the mechanical condition of the aircraft are not provided in the source text. However, environmental factors were noted. The density altitude at the airport was approximately 3,800 feet at the time of the accident. This elevated density altitude can reduce aircraft performance, particularly during takeoff and landing phases, by decreasing lift generation and engine power output.

Findings

The primary factor leading to the accident was the pilot's decision to continue the approach despite floating past the halfway point of the runway. The subsequent collision with trees occurred during the go-around maneuver. Contributing factors included the nighttime conditions and the reported absence of several runway lights at the approach end, which likely degraded visual cues necessary for accurate altitude and distance judgment.

Safety message

Pilots should be aware that floating during landing can significantly reduce available runway length for stopping. If a safe landing cannot be achieved by the midpoint of the runway, a go-around should be initiated immediately. Additionally, pilots must account for reduced visual references caused by missing or inoperative lighting systems, especially at night or in low-visibility conditions.

Probable cause

The pilot's failure to execute a timely go-around during a night landing, which resulted in the aircraft colliding with trees while attempting to depart from the runway.

Frequently asked questions

What happened in the 30 May 1983 Cessna 172D accident near Portland, OR?

A pilot attempted a go-around during a night landing but collided with trees at the departure end of the runway after floating past the threshold.

What aircraft was involved and where did it happen?

The accident on 30 May 1983 involved a Cessna 172D, registration N2897U, at Portland, OR.

What was the probable cause of the accident?

The pilot's failure to execute a timely go-around during a night landing, which resulted in the aircraft colliding with trees while attempting to depart from the runway.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20001214X43160. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.