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

February 25, 2019 · Cessna 172 M · CFHGQ

Bellingham, WA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
February 25, 2019
Injury Outcomes
No injuries (2 uninjured)
Location
Bellingham, WA
Aircraft
Cessna 172 M (1974)
Tail Number
CFHGQ
Injuries
None
Aircraft Damage
Substantial
NTSB Number
GAA19CA148

The pilot reported that, while taxiing to the runway for takeoff with the yoke "left and push[ed] in," a wind gust from the right lifted the right wing. The pilot was unable to maintain control and the wind continued to push the airplane to the left off the runway. The airplane subsequently nosed over. The airplane sustained substantial damage to the fuselage and empennage. The pilot reported that there were no preimpact mechanical failures or malfunctions with the airplane that would have precluded normal operation. The airport's automated surface observation system reported that, about the time of the accident, the wind was from 030° at 20 knots, gusting to 29 knots. The pilot was turning the airplane right onto runway 34. Based on this information, the calculated crosswind component while taxiing into takeoff position was about 19 knots. The airplane manufacturer reported that the maximum demonstrated crosswind component was 15 knots. The Federal Aviation Administration's Airplane Flying Handbook, FAA-H-8083-3B, "Taxiing" stated, in part, the following: When taxiing with a quartering headwind, the wing on the upwind side (the side that the wind is coming from) tends to be lifted by the wind unless the aileron control is held in that direction (upwind aileron UP). Moving the aileron into the UP position reduces the effect of the wind striking that wing, thus reducing the lifting action. This control movement also causes the downwind aileron to be placed in the DOWN position, thus a small amount of lift and drag on the downwind wing, further reducing the tendency of the upwind wing to rise.

NTSB Probable Cause

Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Crosswind correction-Not attained/maintained - C

Full Narrative

The pilot reported that, while taxiing to the runway for takeoff, the yoke was, "left and push in," a wind gust from the right lifted the right wing. The pilot was unable to maintain control and the wind continued to push the airplane to the left off the runway. The airplane subsequently nosed over. The airplane sustained substantial damaged to the fuselage and empennage. The pilot reported that there were no preimpact mechanical failures or malfunctions with the airplane that would have precluded normal operation. The automated surface observing system located on the airport reported that, about the time of the accident, the wind was from 030° at 20 knots, gusting to 29 knots. The pilot was turning the airplane right onto runway 34. The airplane manufacturer reported that the maximum demonstrated crosswind component was 15 knots. The calculated crosswind component while taxiing into takeoff position was approximately 19 knots. The Federal Aviation Administration's Airplane Flying Handbook, FAA-H-8083-3B, provides information and guidance in a section titled "Taxiing" which stated in part: When taxiing with a quartering headwind, the wing on the upwind side (the side that the wind is coming from) tends to be lifted by the wind unless the aileron control is held in that direction (upwind aileron UP). Moving the aileron into the UP position reduces the effect of the wind striking that wing, thus reducing the lifting action. This control movement also causes the downwind aileron to be placed in the DOWN position, thus a small amount of lift and drag on the downwind wing, further reducing the tendency of the upwind wing to rise.

Flight

Event TypeAccident
Event Time10:50 PST
Nearest AirportBellingham Intl (0nm NE)
Runway34
Runway Length6700 ft
Runway Width150 ft
Flight Plan FiledVFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172 M
Tail NumberCFHGQ
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O320-E2D · Reciprocating · 150
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 45 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind30° @ 20 kt, gusting 29 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point36 C / 10 C
Altimeter29.86 inHg
Observation Time18:53
Weather SourcePILO

Appendix: Source Data