Skip to content

Atlas / NTSB / SEA00LA002

NTSB CAROL · Event

Event SEA00LA002

1999-10-16 IDAHO FALLS, Idaho, United States Airport · IDA None 1 aircraft Status: Completed

Registry · N95CF

FAA Aircraft Registry record.

Make / Model

BEECH F33A

Year of manufacture

1988 · 11 years old at event

Engine

CONT MOTOR IO 520 SERIES (285 hp)

Seats / Engines

5 seats · 1 engine

Last airworthiness date

19881028

ADS-B equipped

Yes — Mode-S AD3286

Registrant of record

UES BLUESKY AVIATION LLC

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot's failure to adequately compensate for wind conditions. Factors include gusty, turbulent, variable crosswinds, and a fence in the vicinity of the runway.

Factual narrative

On October 16, 1999, approximately 1045 mountain daylight time, a Beechcraft F33A, N95CF, impacted a fence after departing the runway during the landing roll at Fanning Field, Idaho Falls, Idaho. The private pilot and his passenger were not injured, but the aircraft, which was owned and operated by the pilot, sustained substantial damage. The 14 CFR Part 91 personal pleasure flight, which departed Crosby, North Dakota, about 0830 central daylight time, was operating in visual meteorological conditions. No flight plan had been filed, and there was no report of an ELT activation. According to the pilot, who was landing in gusty, turbulent, variable winds, just as the aircraft was touching down, it was hit by a strong crosswind that caused it to veer to the left. While the pilot was attempting to correct for the sudden change in direction, the aircraft veered quickly back to the right and then back to the left again. During this second excursion to the left, the aircraft departed the left side of the runway and impacted a nearby fence. The investigation revealed no evidence of control system malfunction or anomaly. The pilot was landing in gusty, turbulent, variable winds. Just as the aircraft was touching down, it was hit by a strong crosswind, which caused it to veer to the left. While the pilot was making control inputs in order to keep the aircraft on the runway, it veered quickly back to the right, and then back to the left again. Upon veering to the left this second time, it departed the runway and impacted a nearby fence. The investigation revealed no evidence of control system malfunction or anomaly. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_1999_SEA00LA002.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.