CEN12LA229

NTSB accident investigation · Piper PA-34-200T · San Marcos, TX · April 4, 2012

Accident · No injuriesLimited investigationFinal report
Date
April 3, 2012, 19:30 local (Apr 4, 2012, 00:30 UTC)
Place
San Marcos, TX
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1162XPiper PA-34-200T
Defining event
Landing: Collision during takeoff/land
Weather
Visual (VMC) · Day
Status
Completed · report August 13, 2013
Report
Approved by Office Director
NTSB office
Central Region
Parties
FAA FSDO San Antonio
FAA report
20120403006149A
Case key
83306

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 ensure that he was aware of the NOTAM describing the runway closure, which resulted in a landing on the closed runway and subsequent collision with a barrier. Contributing to the accident was the failure of air traffic control personnel to include the runway closure information on the recorded ATIS information, which the pilot had listened to prior to landing.

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.

Action: forgotten action/omissionPersonnel issues › Action/decision · PilotPiper PA-34-200T: 6 casesAll aircraft: 440 casesProbable cause
Organizational issuesOrganizational issues › Support/oversight/monitoring · ATCPiper PA-34-200T: 1 caseAll aircraft: 12 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 called the Flight Service Station (FSS) before departing on a cross-country flight to ask if there were any restrictions along his flight route that he needed to be aware of; none were mentioned. Upon arrival at his destination about dusk, the pilot listened to the Automated Terminal Information Service (ATIS); the control tower was closed at the time. The pilot then landed the airplane on runway 8, and during the landing roll, the airplane struck construction barriers on the runway, which resulted in the main landing gear shearing off and substantial damage to the left wing. The ATIS recording did not include information about runway 8 being closed. A March 21, 2012, NOTAM was in effect and stated that runway 8/26 was closed due to construction; this information was not provided or requested during the FSS briefing. The Airman’s Information Manual states that an FSS is required to advise pilots of pertinent NOTAMs if a standard briefing is requested. It further states that pilot's should remind the briefer to advise of NOTAMs if the information is not received in the brief. It is ultimately the pilot’s responsibility to ensure that he is familiar with all relevant NOTAMs. Further, FAA Order JO7210.3X states, in part, that facilities with runway construction must ensure ATIS message content is complete, accurate, and contains the proper information related to runway closures. The pilot stated postaccident that reflective ribbons and directional flashing lights, could have helped him see the barrier. He also stated that he flew into the same airport about a week after the accident and noted that the runway closure was included on the ATIS recording.

Factual narrative

On April 3, 2012, approximately 1920 central daylight time, a Piper PA-34-200T, N1162X, registered to Southwest Texas Rain Enhancement Association of Carrizo Springs, Texas, sustained substantial damage when it collided with construction barriers upon landing on closed runway 08 at the San Marcos Municipal Airport (HYI), San Marcos, Texas. The commercial pilot, who was the sole occupant, was not injured. Visual meteorological conditions prevailed and a flight plan was not filed for the positioning flight being operated under the provision of 14 Code of Federal Regulations Part 91. The flight originated at 1800 from Carrizo Springs, Texas, and San Marcos was its destination. According to FAA records, the pilot called Fort Worth Flight Service Station (FSS) at 1700 before departure from Carrizo Springs to ask if any Temporary Flight Restrictions (TFRs) were in effect between Carrizo Springs and San Marcos. After an uneventful flight, he landed the airplane on runway 08 at San Marcos. During the landing roll, the airplane struck construction barriers resulting in sheared main landing gear and substantial damage to the left wing. The San Marcos control tower had closed at 1900. A Notice to Airman (NOTAM) was published and in effect since March 21, 2012, stipulating that runway 08/26 was closed due to construction. The pilot reported that he had called the Fort Worth FSS prior to the flight and asked for TFR's along the route and asked the briefer if "there was anything else that [he] needed to be aware of." The briefer did not mention the NOTAM that was in effect for the runway 08 closure, nor did the pilot specifically ask about NOTAMs. He stated that upon arrival to San Marcos, about dusk, he listened to the Automated terminal Information Service (ATIS). He said that the ATIS recording did not include the closure of runway 08. He planned to land the airplane a bit long on the 6,600 foot runway to limit taxi time. During the landing roll, he was not able to avoid the barricade. Chapter 5, paragraph d., of the Airman's Information Manual, states in part that Flight Service stations are required to advise pilots of pertinent NOTAMs if a standard briefing is requested. It also states that pilot's should remind the briefer to advise of NOTAMs if the information was not received in the brief. Chapter 10, Section 4, paragraph d., of FAA Order JO7210.3X, dated February 9, 2012, states in part that facilities with runway construction must ensure ATIS message content is complete, accurate, and contains the proper information related to runway closures. On the submitted NTSB Form 6120, Recommendation Section, the pilot stated that reflective ribbons, directional flashing lights, could have helped him see the barrier. He also stated that the accident would have been avoided if the runway closure information was included in the ATIS. He said that he flew into San Marcos about a week after the accident, April 24, and noted that the runway closure was includedon the ATIS recording. The pilot offered that had the FSS briefer mentioned the NOTAM and/or if the NOTAM was included in the ATIS recording, the accident would not have occurred.

Aircraft

Registration
N1162X
Reported as
Piper PA-34-200T
Category
Airplane
Serial number
34-7570225
Airframe hours
2,441
Engines
Cont Motor TSIO-360 SER, 225 horsepower, reciprocatingCont Motor TSIO-360 SER, 225 horsepower, reciprocating
Damage
Substantial damage
Flight
Positioning · Part 91
Operator
Southwest Texas Rain Enhancement Assoc
Registered owner
Southwest Texas Rain Enhancement Assoc
Airworthiness certificate
Special, Restricted (Special); Standard, Normal
Last inspection
Annual · April 4, 2011
Departed
CZT · Carrizo Springs, TX
Destination
HYI · San Marcos, TX
Airport
HYI · San Marcos Municipal Airport, runway 08

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
57
Injuries
None
Certificate
Commercial
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 2, With waivers/limitations
Last flight review
October 18, 2010
Seat
Left
Flight hours
2,618 total · 567 in this make and model · 2,683 as pilot in command · 13 in the last 90 days · 8 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
340° at 4 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
79 °F, dew point 63 °F
Altimeter
29.72 inHg
Observed at
HYI

Docket · 4

The files NTSB released with the investigation on July 26, 2013, on NTSB’s docket system: statements, records, photos and specialists’ reports. 4.6 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.