Our New Name

After 18 months of our airport’s name change sitting ignored on the desks of various FAA employees, we were surprised by a set of FDC NOTAMs released on Friday, October 13 for each of our instrument approaches, like this one:

!FDC 7/2843 FNL IAP FORT COLLINS-LOVELAND MUNI,
Fort Collins/Loveland, CO.
VOR/DME-A, AMDT 7 ...
CHART NOTE: DME REQUIRED.
CHANGE AIRPORT NAME FROM FT COLLINS-LOVELAND MUNI TO NORTHERN
COLORADO REGIONAL AIRPORT.
THIS IS VOR-A, AMDT 7A 1710121321-PERM

Jason Licon sent out an email to each badge holder on our airport, notifying us that our name change is effective immediately.  Denver Approach and Denver Center frequencies are now calling KFNL Northern Colorado Regional Airport.

I recommend using the phrase “Northern Colorado Regional Traffic” on CTAF.  We’ve discussed shortening our callsign to NoCo Traffic, but this designation will be unknown to Approach, Center, and transients, so I recommend we table that for awhile until everybody gets used to our new name on the air.

Be alert out there; our airport will now have a new list of almost-correct references on CTAF in addition to the current list of almost-correct references.  You may hear us called any of these (and more):

  • Northern Colorado Regional
  • Northern Colorado
  • NoCo
  • NoCo Regional
  • NorCo
  • NorCo Regional
  • Northern Regional
  • Colorado Regional
  • Fort Collins  Loveland
  • Loveland
  • Fort Collins
  • Fort Love
  • Longmont (yes, I’ve heard this on 122.7)

Let’s try to standardize on Northern Colorado Regional Traffic to be precisely correct and to avoid confusing our many transient pilots during this changeover.  Thanks all!


UPDATE (October 16, 2017): FNL Pilots Association will be holding a round table discussion on Wednesday, October 25, at 7pm in the jetCenter hangar for our local pilot population to come to consensus on our radio call convention.  If you can’t make the meeting, send your preference(s) to Steve Wolf at president@fnlpilots.org.


UPDATE 2 (October 17, 2017): FAA rescinded the NOTAMS, and promises to change our name on December 7.


 

UPDATE 3 (October 25, 2017): EAA Chapter 515 held a CTAF round table at their meeting last Tuesday, and FNL Pilots Association held another this evening, for our pilot population to discuss what radio call to use in the FNL pattern once FAA decides to make FNL’s name change official.  The preferred choice from both groups is “NoCo Traffic“.

NOTE: For now, keep using what you’ve been using (“Fort Collins – Loveland Traffic”, “Fort Love Traffic”, and all other variants) until notified by airport staff that the name change is official.   We don’t want to create any confusion by injecting yet another variant until we’re ready to standardize on the new radio call.

Once FAA starts stamping “Northern Colorado Regional Airport” on its documents (sectionals, approach charts, chart supplement, etc.) and airport staff notify us that the new airport name is in effect, EAA 515 and FNL Pilots Association ask all pilots to standardize on “NoCo Traffic” when giving position reports on 122.7.

Some have recommended “NorCo” rather than “NoCo”; if that’s what you want to use instead, it’s fine.  I contend that the two will sound virtually identical over our AM radios.

If our entire pilot community, including based pilots, pilots from nearby airports, flight schools, and corporate users can standardize on “NoCo Traffic”, it’s almost a slam dunk that we can talk our Remote Tower into using “NoCo Tower” when it comes on line in a couple years.  Thanks for your cooperation.

We anticipate the name change to happen on December 7, but based on recent history would not be surprised by another delay.  We’ll keep you informed about when to implement this CTAF change.

Third Class Medical Reform

Unless you’ve been living under a rock, you’re probably aware that Congress finally passed third class medical reform into law last July.  They gave the FAA one year to implement the law.

The latest FAAST Blast from the FAA includes this paragraph, entitled FAA Making Progress on New Pilot Medical Qualifications:

The FAA is working to implement Section 2307 of the FAA Extension, Safety, and Security Act of 2016 (P.L. 114-190), Medical Certification of Certain Small Aircraft Pilots. In the Act, Congress outlined an alternative medical qualification in lieu of holding an FAA medical certificate. The FAA must draft rules to meet the Congressional mandate. We have reached out to the general aviation community, including groups which have expressed a desire to partner with the FAA during the implementation. We look forward to working with them to successfully implement the provisions of Section 2307 on time.

When I run that paragraph through my personal government-ese filter, I see:

We don’t want to enact medical reform, but we have to.  AOPA and EAA keep bugging us asking about our progress.  Quit asking already!  We’re going to drag our feet and take every minute of the full year we’ve been allocated.

Their “progress” report doesn’t report any progress, except that they’ve talked with the alphabet groups (I would guess it’s actually the other way around, with the alphabet groups talking to them).  Everything else is presented in future tense.

I renewed my third class medical a couple months ago.  I realize this was probably the last FAA medical I’ll ever have, and it feels good.  No longer will I have to fear that inexplicable Sport Pilot Catch-22: If I let my medical expire, I am free to fly Sport Pilot as long as I can self-certify that I am medically fit to do so; but if I submit to and fail a third class medical exam, I can’t ever fly Sport Pilot.

AOPA and EAA have both written extensively about what they believe the medical reform will look like, including seeing our family doctor from time to time, so I won’t duplicate all that here.  Both organizations deserve a hearty pat on the back: they persistently bulldogged this through the legislative process; they consulted on the inevitable compromises; they helped keep reform on track without the bill crippling its original intent.

Appareo representative Geremy Kornreich simplifies ADS-B

Here is a summary of Geremy’s presentation to our Association on September 22.

ADS-B stands for Automatic Dependent Surveillance Broadcast and it is part of FAA’s NexGen revamping of the air traffic control system. It provides better information to the air traffic control system and pilots. The FAA mandate for ADS-B Out in Class B and C airspace is December 31, 2019 at midnight.

For example, a typical transponder, when it is interrogated by radar, says “Here I am. Here is my altitude, here’s my squawk code.”

An ADS-B Out system will automatically send out “Here I am, here is my latitude and longitude”, every second. By that the ATC system can calculate your speed and direction. It also tells the system what kind of plane you have, which tells it your performance capabilities and size. Some think ADS-B is the entry way to user fees.

There are two main data sets in ADS-B world. ADS-B Out makes you legal. ADS-B In makes you safe.

It broadcasts on two frequencies, 978 megahertz known as UAT (Universal Access Transceiver) and 1090 megahertz known as ES (Extended Squitter). ES is what you need if you are flying above 18,000 feet and/or out of the U.S.

UAT is only good in the US below 18,000 feet, and you will still need your existing transponder. The rule of thumb is that if you don’t need a transponder for the flying you currently do, you won’t need ADS-B post-2020 either.  But if you ever want to sell your plane, you will probably need ADS-B.

ADS-B In provides two services, FIS-B and TIS-B.  Your ADS-B In receiver doesn’t have to be permanently installed in the aircraft (such as the Stratus), and isn’t required for the 2020 mandate.

FIS-B stands for Flight Information Services Broadcast.  It includes textual weather (METAR and TAF), winds aloft, NEXRAD weather radar, TFRs,  AIRMETs, SIGMETs, and PIREPs, all of which can be displayed on your device (iPad, GPS, multifunction display, etc., depending on your equipment). The FIS-B data is continuously being broadcast by ADS-B towers, which are laid out in a ground-based network. There are about 600 of them around the country (usually installed on cell phone towers) with more being added to improve coverage. The closest tower to FNL is near Johnstown.

TIS-B stands for Traffic Information Services. This is not broadcast to all traffic. It is a custom report that only responds to an ADS-B out trigger.  A nearby ADS-B tower responds with all known traffic in your “hockey puck”, a chunk of airspace centered on your aircraft that is about 3,500′ tall (1,750′ below you and 1,750′ above you) and 30nm in diameter (aircraft within 15nm of you).

If you are not ADS-B Out equipped, your ADS-B In receiver can see this hockey puck data as well, but unless you are co-located with the aircraft that is generating the data (and I hope you aren’t), you can be missing out on a substantial amount of information.  For example, if you are 15nm east of an ADS-B Out aircraft, your receiver will see traffic to your west but not to your east.

ADS-B In receivers also receive direct air-to-air traffic information — UAT if they receive that band and ES if they receive that band.  Many receivers these days are dual-band.  So you can see ADS-B Out equipped traffic that is outside your hockey puck.

The more congested the area is, and the more aircraft there are with ADS-B Out, you’re probably always in someone’s hockey puck. The farther east you go from here, away from the metropolitan area, you won’t benefit much from TIS-B if you don’t have ADS-B Out.  But you will still get the FIS-B weather.

ADS-B ground stations are one of three types: low (local information), medium (regional information), and high (national information).  They are laid out in a honeycomb pattern:

ads-b-network-tower-graphic

The theory is that the higher you are (and thus the more towers you can receive), the more likely you have a more capable, faster cruising aircraft that benefits from longer range data.

All the weather is at least ten minutes old by the time it is broadcast, and usually closer to twenty minutes. So if you are using Foreflight or something to try to fly around weather, please don’t. Weather can move quickly.  Use the weather for big-picture weather trends, not to sneak through a hole between cells.

XM weather works better than ADS-B, but ADS-B is free. It’s all about the granularity.

ADS-B out will be required in 2020 where Mode C transponders are required today. In order to be compliant you will need a WAAS GPS source for your ADS-B Out device.  Some devices come with built-in WAAS GPS (at a higher cost).  ADS-B Out must be panel mounted and permanent due to the fact of the information about your plane.

If you choose to use UAT for ADS-B out, you are going to retain your existing transponder, and the UAT device must synchronize to it.  Various methods are used by different vendors, from a “head” device on your panel where you enter or verify your squawk code, to devices that clamp to your transponder’s coax, to antennas mounted near your transponder antenna.

At the moment the ES installs are leading the UAT  installs by about 3 or 4 to 1. Because of the piggy back nature, remote mounting, and old tired transponders that have to be replaced with new ones, installation costs for UAT are usually substantially more than the cost of an ES solution.

Previously in order to have a TSO piece of equipment, a manufacturer had to prove that it works on one particular aircraft (generating an STC) and then provide data to add other aircraft to the list (generating an AML). So, for example, you could install an Appareo ADS-B Transponder on a Cessna 182 but not on a Cessna 210.  In May, FAA came out with a memo with updated information stating that you don’t need an AML for a transponder, particularly an ADS-B transponder upgrade. So now there is a little paperwork that needs to be done by your installer, but any certified ADS-B device can be installed on any aircraft.

Look Out… Above

Just three short years ago the FAA-Denver TRACON (Metroplex) developed new airspace procedures to enhance safety and efficiency with the help and input of all user groups (Airline/Charter/Business-Private General Aviation) to not only benefit Denver International Airport (DEN) but all the surrounding airports and communities as well. Unfortunately, the Metroplex has now developed new arrival procedures for the benefit of DEN that will drastically affect users in the area.

What does this mean for Northern Colorado Regional Airport (FNL)? The new BRNKO arrival is being proposed to fly over or near Greeley (GXY) and FNL at 10,000′ and 9,000′ MSL respectively, then track over the Longmont (LMO) and Boulder communities on the way to Centennial Airport (KAPA). Centennial is one of the busiest general aviation airports in the country which means FNL and surrounding communities will see much more high speed traffic crossing overhead at only 4,000′ AGL. IFR operations could be impacted with the lower altitudes of this arrival. The VFR corridor between BJC and FNL is already saturated and now will be compressed even more from above.

Jason Licon, FNL’s Airport Manager, is fully aware of the challenges that this could create for all users of our airport. Jason is currently working together with the airport managers at APA, BJC, LMO, and GXY and involved with the FAA to ensure current and future growth of FNL will not be impacted with these changes. Representatives from Aircraft Owners and Pilots Association (AOPA), Colorado Aviation Business Association (CABA), and National Business Aviation Association (NBAA), along with state representatives, are also actively engaged with the proposed changes and how it will affect our communities and airports.

New Airport Name: Northern Colorado Regional Airport

Our Airport Commission voted this afternoon to rename our airport to Northern Colorado Regional Airport, effective immediately.  Over the next few months, we can expect the name change to appear on approach charts and sectional charts.  The commission will be asking the two cities for funding to change the signage around the airport.

Our radio calls will eventually change to some variation of “Northern Colorado Regional Traffic” (my recommendation is “NorCo Traffic”).  Keep doing what you’re currently doing on the radio (“Fort Collins Loveland Traffic” or “Fort Love Traffic” or whatever) until we’re directed to change.

Our airport designator will continue to live on as FNL, so we will remain FNL Pilots Association.