Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

January 31, 2000 · Cessna 177 · N3433T

Snohomish, WA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
January 31, 2000
Injury Outcomes
2 injuries (1 serious injury, 1 minor injury)
Location
Snohomish, WA
Aircraft
Cessna 177
Tail Number
N3433T
Injuries
Serious
Aircraft Damage
Destroyed
NTSB Number
SEA00LA041

While on short-final to a full-stop landing, the wind shifted and the aircraft's rate of descent increased. The pilot corrected with partial power, but did not initiate the landing flare soon enough to keep the aircraft from hitting the runway hard enough to bounce back into the air. After ballooning back into the air, the aircraft started drifting sideways and touched down in an open grassy area alongside the runway. Although the power was at idle at that point, and the pilot had ample room to bring the aircraft to a stop on the grass, he elected to abort the landing. After adding power and trying to get the aircraft to lift off using two different flap settings, the pilot elected to abort the go-around because he thought he might not clear obstacles ahead. During his attempt to stop the aircraft on the wet grass, it slid into a residence just off to the side of the southeast end of the runway. After impacting the house, both the residence and the aircraft caught on fire.

NTSB Probable Cause

The pilot's improper decision to attempt a go-around, then attempt to stop on the wet grass. Factors include variable winds, the pilot's inadequate compensation for the winds conditions, his inadequate recovery from a bounced landing, wet grass along the side of the runway, and a residence near the edge of the runway surface.

Full Narrative

On January 31, 2000, approximately 1530 Pacific standard time, a Cessna 177, N3433T, collided with a personal residence during a balked landing at Harvey Airfield, Snohomish, Washington. The private pilot received serious injuries, his passenger received minor injuries, and the aircraft, which was owned by a friend of the pilot, was destroyed by a post-impact fire. The CFR Part 91 pleasure flight, which departed Skagit Regional Airport, Burlington, Washington, about 30 minutes prior to the accident, was operating in visual meteorological conditions. No flight plan had been filed, and there was no report of an ELT activation. According to both the pilot and his pilot-rated passenger, while they were on final approach to runway 14, the wind seemed to shift about the time the aircraft crossed over the 22 foot-high wires just off the north end of the runway. As a result of the wind shift, the aircraft's rate of descent increased and the pilot added power. According to the pilot, there might have been a delay in engine response, but the passenger reported that the engine responded normally. According to the pilot, as the aircraft approached the runway surface, he began the landing flare, but not soon enough to properly arrest the rate of descent prior to contacting the runway surface. The aircraft then hit the runway hard, bounced back into the air, and began drifting to the left. According to the passenger, the pilot added partial power when the aircraft ballooned, but pulled the throttle to idle as the aircraft touched down on the grass along the northeast side of the runway. With about 1,500 feet of grass surface remaining on which to stop, the pilot put the flaps in the full-up position, turned off the carburetor heat, and added full power in an effort to abort the landing. Both the passenger and a number of other witnesses said that the pilot then pulled the nose of the aircraft up so high that the tiedown tang under the tail was digging into the dirt. Since the aircraft did not lift off as soon as the pilot thought it should, he told the passenger to "give me flaps," and the passenger moved the flaps to the 10 degree position. Soon thereafter, the pilot partially reduced power, moved the flaps back to the full-up position, and added full power again. Within a few seconds of adding power this second time, the pilot realized that the aircraft might not clear the fence at the southeast end of the airport property or the cars on the road just beyond the fence. He therefore brought the power to idle and tried to turn to the right away from the hangars that were under construction just off his left wing tip. This resulted in the aircraft heading toward the residence near the end of the runway. The pilot applied hard breaking, but due to the slippery wet grass he was unable to stop the aircraft prior to it contacting the house. After colliding with the house, the aircraft caught fire. Both the pilot and the passenger reported that the engine was running smooth with no evidence of coughing, backfiring, or missing. The FAA inspector who responded to the scene reported that he saw no evidence that would lead him to believe there had been an engine malfunction or flight control anomaly.

Flight

Event TypeAccident
Event Time15:30 PST
Nearest AirportHarvey Field (0nm)
Runway14
Runway Length2660 ft
Runway Width36 ft
Flight Plan FiledNone
Aircraft FireGrd
Aircraft ExplosionNo

Aircraft

AircraftCessna 177
Tail NumberN3433T
Aircraft CategoryAir
DamageDestroyed
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 · Reciprocating · 150
Seats4

People & Injuries

Injury Summary2 injuries (1 serious injury, 1 minor injury)
Fatal0
Serious1
Minor1
Uninjured0
Total2
Crew 1Age 68 · Second Class

Conditions

ConditionsVMC
LightDaylight
Wind130° @ 5 kt
Visibility10 sm
CeilingOvercast 15000 ft
Temperature / Dew Point48 / 0 C
Altimeter29.00 inHg
Weather SourceWIT

Appendix: Source Data