• Skip to primary navigation
  • Skip to main content
General Aviation News

General Aviation News

Because flying is cool

  • Pictures of the Day
    • Submit Picture of the Day
  • Stories
    • News
    • Features
    • Opinion
    • Products
    • NTSB Accidents
    • ASRS Reports
  • Comments
  • Classifieds
    • Place Classified Ad
  • Events
  • Digital Archives
  • Subscribe
  • Show Search
Hide Search

Runway closure surprises pilot

By NTSB · April 8, 2014 ·

Aircraft: Piper Seneca. Injuries: None. Location: San Marcos, Texas. Aircraft damage: Substantial.

What reportedly happened: The pilot called the Flight Service Station 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.

He arrived at his destination about dusk when the control tower was closed. He listened to the automated ATIS to determine which runway was appropriate for landing. Based on the information obtained from the ATIS, he selected runway 8 for landing. The ATIS recording did not include information about runway 8 being closed. He landed on runway 8.

During the landing roll the airplane collided with construction barriers.

After the accident it was determined that a March 21, 2012, NOTAM was in effect and stated that runway 8/26 was closed due to construction. Investigators determined that 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 pilots 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 that had reflective ribbons and directional flashing lights been on the runway it, 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.

Probable cause: 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. Contributing to the accident was 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.

NTSB Identification: CEN12LA229 

This April 2012 accident report is provided by the National Transportation Safety Board. Published as an educational tool, it is intended to help pilots learn from the misfortunes of others.

About NTSB

The National Transportation Safety Board is an independent federal agency charged by Congress with investigating every civil aviation accident in the United States and significant events in the other modes of transportation, including railroad, transit, highway, marine, pipeline, and commercial space. It determines the probable causes of accidents and issues safety recommendations aimed at preventing future occurrences.

Reader Interactions

Share this story

  • Share on Twitter Share on Twitter
  • Share on Facebook Share on Facebook
  • Share on LinkedIn Share on LinkedIn
  • Share on Reddit Share on Reddit
  • Share via Email Share via Email

Become better informed pilot.

Join 110,000 readers each month and get the latest news and entertainment from the world of general aviation direct to your inbox, daily.

This field is for validation purposes and should be left unchanged.

Curious to know what fellow pilots think on random stories on the General Aviation News website? Click on our Recent Comments page to find out. Read our Comment Policy here.

Comments

  1. Dick Rubbins says

    April 10, 2014 at 1:32 pm

    Looks like San Marcos will be buying him a new Seneca!

  2. Tom says

    April 9, 2014 at 3:53 pm

    The easiest way is to ALWAYS check DUATS before every flight because the NOTAMS are there. It’s simple to use and if for some unusual reason the runway closing didn’t appear on DUATS then you have a written record that someone messed up besides the pilot. ALWAYS check DUATS. Forget about calling for a weather briefing on the phone because then you have a “he said she said” situation. DUATS locks in the responsibility.

  3. Randy Coller says

    April 9, 2014 at 9:11 am

    I inspect airports & train airport inspectors.
    I do pilot safety seminar and teach aviation.

    Two things I’ve learned:
    1. Pilots claim airport managers not issue NOTAMs.
    2. Airport manager’s claim pilots don’t read NOTAMs.

  4. Dennis Reiley says

    April 9, 2014 at 7:26 am

    “It is the responsibility of the pilot…”, is grossly overused. If the pilot requests information it is not his fault if some information is withheld.

  5. Ray says

    April 8, 2014 at 11:14 am

    This is just one giant FUBAR.

    • BlueStar says

      April 9, 2014 at 7:16 am

      you know the stock answer, it is always the same…. “it is the sole responsibility of the Pilot”
      I can see this buck being passed back and forth, nonetheless, both parties could have prevented this accident.

      • Tom says

        April 9, 2014 at 5:55 pm

        The hunters departed early,
        They longed for their prey to kill,
        Looking for the prize male animal so surly,
        Truly competitors out for a thrill.

        Suddenly they saw a large deer,
        Both fired for all they were worth,
        Each took credit for the kill we hear,
        At lunch they “passed the buck back and forth”.

        • Bluestar says

          April 9, 2014 at 6:13 pm

          William Wordsworth you’re not,
          But keep trying
          Give it all you got

© 2025 Flyer Media, Inc. All rights reserved. Privacy Policy.

  • About
  • Advertise
  • Comment Policy
  • Contact Us
  • Privacy Policy
  • Writer’s Guidelines
  • Photographer’s Guidelines