FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN18LA341 · Cirrus SR22 T

19 Aug 2018 · Granbury, TX, United States

Cirrus SR22 T · Accident: runway excursion during landing

From Granbury Regional Airport (KGDJ) to Granbury Regional Airport (KGDJ)

Report a problem

Event

NTSB case
CEN18LA341
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
0 · 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

Cirrus SR22 T

Aircraft type
Cirrus SR22
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
N1133T
Operator
Unknown
Onboard fatalities
Unknown
Route
From Granbury Regional Airport (KGDJ), Granbury, TXTo Granbury Regional Airport (KGDJ), Granbury, TX
Aircraft age
About 3 years (built 2015)
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
Landing · landing roll
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
Runway excursion
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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

  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot was practicing instrument flight rules approaches and was returning for a landing with a light crosswind during dusk visual meteorological conditions. He disengaged the autopilot using the panel autopilot button. All flight controls seemed to perform normally. The right turn to base and right turn to final were made normally. On final approach, the pilot made minimal rudder inputs. As the pilot started to flare the airplane, he started putting in more rudder inputs. However, he could not depress the left rudder pedal fully. The airplane touched down about 80 knots on the main landing gear while the pilot was holding all the left rudder he could. The airplane started to veer to the right and continued off the runway, where it impacted a ditch, fence, and tree; the airplane sustained substantial damage to a wing and the fuselage.

The pilot indicated that the yaw damper was on when he landed. However, the airplane was equipped with a recoverable data module that recorded the flight's configuration and navigation data, which indicated that the yaw damper was off about 1/4 mile before the landing runway threshold.

Given the available information, the pilot likely did not maintain directional control of the airplane during the crosswind landing.

Probable cause

The pilot’s failure to maintain directional control during a crosswind landing, which resulted in the airplane exiting the runway and impacting a ditch, tree, and fence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18LA341
Event ID
20180820X25554
Case number
CEN18LA341
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2018-08-20.
  • API snapshot SHA-256: 22007c2830ea343ff84d7e5743af69867066ecd1583ec2159495abe8f67ac18d; retrieved 2026-09-16T08:07:25.822Z.