I have worked airport PR for a long time. If you ignore the complaints of
the local community, regardless of who came first, the airport will lose.
There were two options available:
1) Pass the pilot's name and tail number to the FAA and let them deal with
it (this is what the FAA has asked us to do in the past). I did not choose,
nor do I like this option.
2) Handle it in house by letting the local flying community know of the
problem. My preferred solution.
The aircraft that some seem to be focused on is a U.S. Forest service
contracted aircraft that comes in here every year at this time to do survey
work. The aircraft is flying in pre-approved areas at pre-approved
altitudes and did not cause the problem.
Kino Chavez
*TAOS*Aviation
P: 575-737-9790
E: kino.chavez@xxxxxxxxxxxxxxxx
www.*TAOS*Aviation.com <http://www.TAOSAviation.com>
On Fri, Jul 8, 2022 at 9:02 AM David Chasteen <dchasteen@xxxxxxxxx> wrote:
Earlier is better than later on this stuff. Once a critical mass of people
have decided they hate the airport, it's hard to roll it back and then bad
things happen.
https://www.flyingmag.com/shorter-runway-at-ksmo-increases-risk/#:~:text=The%20FAA%20has%20authorized%20the,since%20the%20runway%20was%20shortened
.
On Fri, Jul 8, 2022, 06:27 Kino Chavez <kino.chavez@xxxxxxxxxxxxxxxx>
wrote:
Pattern Restrictions have been needed for a long time. The community is
going to demand them. I have been receiving requests for a long time.
Kino Chavez
*TAOS*Aviation
P: 575-737-9790
E: kino.chavez@xxxxxxxxxxxxxxxx
www.*TAOS*Aviation.com <http://www.TAOSAviation.com>
On Thu, Jul 7, 2022 at 4:25 PM Lynz <dmarc-noreply@xxxxxxxxxxxxx> wrote:
Obviously the offender is known to the FBO, so why not just deal with
him directly instead of suggesting flight restrictions affecting all
pilots? Then we can also all be spared the hand wringing and amateur ADS-B
CSI. Just a thought...
