ERA17CA149

NTSB accident investigation · North American T 6G · Culpepper, VA · April 8, 2017

Accident · Serious injuriesData collectionFinal report
Date
April 8, 2017, 13:40 local (17:40 UTC)
Place
Culpepper, VA
Injuries
1 serious, 1 minor
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3167GNorth American T 6G
Defining event
Landing-landing roll: Loss of control on ground
Weather
Visual (VMC) · Day
Status
Completed · report October 31, 2017
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20170408005599A
Case key
94975

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 failure to maintain airplane and directional control during the landing roll and subsequent go-around in gusting wind conditions.

Findings · 3

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.

Wind: gustsEnvironmental issues › Conditions/weather/phenomena · Effect on operationNorth American T-6G: 1 caseAll aircraft: 1,199 casesProbable cause
Performance/control parameters: directional controlAircraft › Aircraft oper/perf/capability · Not attained/maintainedNorth American T-6G: 6 casesAll aircraft: 3,958 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotNorth American T-6G: 5 casesAll aircraft: 9,295 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 stated that, after a thorough preflight inspection and passenger briefing, he started the engine and noted that there was an 80° left crosswind at 5 knots, gusting to 15 knots. He performed an engine run-up, checked the flight controls, and then departed to fly around the local area for about 20 minutes. He then returned to the departure airport, and because the airplane was only equipped with a single radio and there was traffic congestion, he did not monitor the weather or ask for a wind check. He performed a "high break" at traffic pattern altitude, and while on final approach with the flaps fully extended, he maintained a left-wing-low attitude to correct for the left crosswind. He performed a wheel landing, but as the tailwheel was lowering, the left wing raised "dramatically," and the right wingtip contacted the runway. He added power to abort the landing, but because the right wing was contacting the runway, the airplane pivoted to the right. The airplane went off the right side of the runway and nosed over. The pilot reported that there were no preimpact mechanical failures or malfunctions of the airframe or engine that would have precluded normal operation. The reported wind conditions about 5 minutes before the accident included a variable crosswind between 80° and 170° left of the selected runway heading at 8 knots, gusting to 16 knots.

Factual narrative

The pilot stated that after a thorough preflight inspection and passenger briefing, he started the engine and noted that there was an 80° left crosswind at 5 kts, with gusts to 15 kts. He performed an engine run-up and checked the flight controls, then departed to fly around the local area for about 20 minutes. He then returned to the departure airport, and because the airplane was only equipped with a single radio and traffic congestion, he did not monitor the weather or ask for a wind check. He performed a "high break" at traffic pattern altitude and while on final approach with the flaps fully extended, he maintained a left wing low attitude to correct for the left crosswind. He performed a wheel landing, but as the tailwheel was lowering, the left wing raised "dramatically" and the right wingtip contacted the runway. He added power to abort the landing, but because the right wing was contacting the runway, the airplane pivoted to the right. The airplane went off the right side of the runway and nosed over. The pilot indicated there were no preimpact mechanical failures or malfunctions of the airframe or engine that would have precluded normal operation. The reported wind conditions about 5 minutes before the accident included a crosswind that was variable between 80° and 170° left of the selected runway heading, at a velocity of 8 kts, with gusts to 16kts.

Aircraft

Registration
N3167G
Reported as
North American T 6G (G)
Category
Airplane
Serial number
49-3272
Built
1949
Airframe hours
8,875
Engine
Pratt & Whitney R-1340-AN1, 600 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · March 28, 2017 · 25 hours before
Departed
CJR · Culpeper, VA
Destination
CJR · Culpeper, VA
Airport
CJR · Culpeper Regional Airport, runway 4, 5,000 × 100 ft, asphalt
Equipment
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
56
Injuries
Minor
Certificate
Private
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 2, With waivers/limitations
Last flight review
August 24, 2016
Seat
Front
Restraint
5-point
Flight hours
1,951 total · 359 in this make and model · 1,872 as pilot in command · 72 in the last 90 days · 45 in the last 30 days · 0 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
290° at 8 knots, gusting 16
Visibility
10 statute miles
Lowest ceiling
None
Temperature
63 °F, dew point 27 °F
Altimeter
30.01 inHg
Turbulence
Light
Observed at
CJR

Docket · 4

The files NTSB released with the investigation on October 2, 2017, on NTSB’s docket system: statements, records, photos and specialists’ reports. 3.4 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.

Other investigations on N3167G · 1

Matched to the same aircraft by N-number and date.