Community, Witham Airport At Odds Over Improvement

Gemini Sparkle

Key Takeaways:

  • The Martin County Commission voted to close a 460-foot section of Witham Field's runway due to local community concerns about noise and pollution, despite the FAA having approved its extension in 1998.
  • This local action creates a conflict with the FAA, potentially risking federal funding for the airport or incurring federally imposed fines for the local community.
  • While local activists advocate for the runway section's removal, airport businesses and users support maintaining the full runway length, and pilots continue to use the entire space amidst the dispute.
See a mistake? Contact us.

The Martin County Commission, influenced by community-developed noise and pollution concerns, more than six months ago voted to stop using a 460-foot section of runway at Witham Field in Stuart, Fla. Unfortunately, in 1998 the FAA approved the runway for extension. And so it is that while the FAA’s regional office in Orlando has suggested moving a fence farther from the runway and into a country club to provide a proper safety zone, Dave Shore, president of the Witham Airport Action Majority (WAAM), has suggested pulling a Richard Daley by removing the runway from service whether the FAA likes it or not. Of course, any such action could stop the flow of federal funds for the airport or even trigger a federally imposed fine for the local community. Meanwhile, the FAA — which has given the airport thousands of dollars in grants, including money to buy noise-affected homes — hasn’t spoken up and pilots are still using whatever runway space they need (or prefer). Some portion of the local population has apparently risen to protest use of the runway by picketing county commission meetings, but so too have airport businesses and users stepped forward in support of the runway’s full length.

Sign-up for newsletters & special offers!

Get the latest stories & special offers delivered directly to your inbox

SUBSCRIBE

Please support AVweb.

It looks like you’re using an ad blocker. Ads keep AVweb free and fund our reporting.
Please whitelist AVweb or continue with ads enabled.