• 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

Pilot mistakes ag field for runway

By NTSB · February 6, 2015 ·

The pilot of the Cessna 206 was approaching to land on a private unimproved runway near Sabinal, Texas. The field immediately adjacent to the landing area had been recently plowed.

He was landing into the direction of the rising sun, which was just coming over the horizon as he was making his approach. He mistakenly identified a plowed portion of the field for the intended landing area and proceeded to land on it.

As he touched down, he noticed the landing area was softer than it should have been, so he kept the nose wheel off the ground as long as he could.

The nosewheel finally set down in the soft dirt and dug in, resulting in the airplane flipping over on its back. Both of the airplane’s wings, vertical stabilizer, and rudder received substantial damage.

The NTSB determined the probable cause was the pilot’s failure to properly identify the airstrip, which resulted in him landing in soft soil, causing the nose over.

NTSB Identification: CEN13CA206

This February 2013 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. John says

    February 9, 2015 at 7:43 am

    It looks like two factors were at play in this accident. Communication was imperfect, and the pilot decided to forego a final pre-landing check of his intended off-airport runway. The first link i the accident chain occurred the day prior when (according to the docket) the land owner and pilot had an email conversation. During the conversation the land owner didn’t mention he had just plowed the field immediately adjacent to where the accident occurred and the pilot, who had previously landed there, failed to ask for confirmation that the field was still suitable for the landing. The second link was the pilot’s failure to overfly the field of intended landing to confirm the actual landing site, and to confirm it was suitable. Descending into the sun made it unlikely he would or could detect the freshly plowed soil where he intended to land. A good lesson for all.

    • Ron says

      February 9, 2015 at 4:22 pm

      I agree, pilots should always verify the condition of their destination airport. However, in this situation, it wouldn’t make a difference. The field was functional, the pilot just didn’t land at it.

      A third link might also include planning an arrival time requiring landing into the rising sun.

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

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