CEN22LA171

NTSB accident investigation · Cirrus Design SR22 · Peyton, CO · April 8, 2022

Accident · No injuriesClass 4 · LimitedFinal report
Date
April 7, 2022, 19:50 local (Apr 8, 2022, 01:50 UTC)
Place
Peyton, CO
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N248GCirrus Design SR22
Defining event
Approach-VFR pattern final: Collision during takeoff/land
Weather
Visual (VMC) · Dusk
Status
Completed
Report
Approved by Office Director
Investigation class
Class 4 - Basic report with no Prelim publish
NTSB office
Central Region
Parties
Federal Aviation Administration
FAA report
20220407004559A
Case key
104929

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The pilot’s decision to not activate the runway lighting and misjudged the runway location, which resulted in a collision with a windsock.

Findings · 5

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Performance/control parameters: descent/approach/glide pathAircraft › Aircraft oper/perf/capability · Not attained/maintainedCirrus Design SR22: 14 casesAll aircraft: 809 casesProbable cause
Performance/control parameters: heading/courseAircraft › Aircraft oper/perf/capability · Not attained/maintainedCirrus Design SR22: 3 casesAll aircraft: 82 casesProbable cause
Airport facilities/design: runway lightingEnvironmental issues › Operating environment · Decision related to conditionCirrus Design SR22: 1 caseAll aircraft: 18 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot reported he intended to land after sunset and did not activate the runway lighting. During final approach, the airplane collided with the airport windsock and landed next to the runway. During the landing roll the pilot maneuvered the airplane onto the runway and stopped on a taxiway. The airplane sustained substantial damage to the left wing when it impacted the windsock. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operations and that he misjudged the runway location.

Aircraft

Registration
N248G
Reported as
Cirrus Design SR22
Category
Airplane
Serial number
1261
Built
2005
Airframe hours
1,861.2
Engine
Continental Motors IO-550-N, 310 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Registered owner
Halo LLC
Airworthiness certificate
Standard, Normal
Last inspection
Annual · February 12, 2022 · 15.3 hours before
Departed
CDC · Cedar City, UT
Destination
FLY · Peyton, CO
Airport
FLY · Meadow Lake Airport, runway 33, 6,001 × 60 ft, asphalt
Equipment
Electronic primary flight display, Stall warning system, ADS-B, Airframe parachute, Auto-pilot, Electronic flight bag or handheld device

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
53
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, With waivers/limitations
Last flight review
June 26, 2021
Seat
Left
Restraint
4-point
Flight hours
200 total · 85 in this make and model · 151 as pilot in command · 23 in the last 90 days · 13 in the last 30 days · 4 in the last 24 hours

Weather

Conditions
Visual (VMC) · Dusk
Wind
360° at 8 knots, gusting 16
Visibility
10 statute miles
Lowest ceiling
None
Temperature
37 °F, dew point 7 °F
Altimeter
30.32 inHg
Observed at
KFLY
METAR
KFLY 080155Z AUTO 36008G16KT 10SM CLR 03/M14 A3032 RMK AO2 T00301141

Docket · 4

The files NTSB released with the investigation on May 2, 2022, on NTSB’s docket system: statements, records, photos and specialists’ reports. 6.0 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.