Back of a TAC chart

[Joe Dubner]

Is it possible to display the back (reverse side) of a TAC chart?   This question arises because I find that the Portland (OR) TAC chart is printed on the reverse of the Seattle TAC chart (now called the Seattle/Portland TAC chart). 

My Avare installation (10.1.0) on my Motorola Moto G Power running Android 11 provides a checkbox for downloading a Seattle TAC but no Portland TAC and no Seattle/Portland TAC.

73,

Joe, K7JD

APRS track

[Simon Roberts]

That's the "flyway" chart. Last on the list.

[Joe Dubner]

Thank you, Simon.  I guess I never scrolled down enough to notice "Flyway Charts."   :-)

I didn't see a "Portland Flyway" so I downloaded Seattle.  When I went back to the Map tab the screen was mostly blank

except for "Download Flyway".

Then I download every flyway chart.  Still no luck.  However, I am able to view the Seattle flyway chart when in the vicinity of SEA.  But nothing around PDX.

So I'm afraid I remain clueless and would "like to buy a vowel".

--

Joe

[Simon Roberts]

Oh poop :( Sorry to hear that--I'm out of ideas, and vowels too. Hope someone else might be able to comment.

[John W SBA]

> Seattle flyway chart when in the vicinity of SEA. But nothing around
PDX.

Avare uses only the official FAA charts and materials. SEA, SFO, LAX,
etc. are big Class B airports, and Class B are the only ones the FAA
publishes Flyway charts for. PDX is a smaller Class C like my beloved
SBA, so no Flyway but lots more friendly and fun. :)

[Joe Dubner]

Rather than argue, I'm attaching a screen capture of the Portland TAC showing flyways.  This is from skyvector.com and is presumably a true copy of the paper chart.  (I wouldn't know; I haven't seen a current paper chart in years.)

This is what I would like to appear on my tablet when I change from Sectional to TAC in the vicinity of Portland (PDX).

[Peter Gustafson]

Hey all,

Joe, just for clarity for all, what you showed is a terminal area chart (TAC), not a flyway chart.

The Portland TAC chart is new!  We didn''t have it because I didn't see the notice that a new chart is now in distribution.  I'm adding it and it will take at least until the next cycle (and Avare release, as it takes both).  You should see it soon though.

Pete

(Apps4Av chart maintenance guy)

--
You received this message because you are subscribed to the Google Groups "Apps4Av Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to apps4av-foru...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/apps4av-forum/4bb7902f-b3c2-79c8-5391-9542c0e4c77f%40gmail.com.

[Joe Dubner]

On Tuesday, March 15, 2022 at 9:05:39 AM UTC-7 pgust...@gmail.com wrote:

 

The Portland TAC chart is new!  We didn''t have it because I didn't see the notice that a new chart is now in distribution.  I'm adding it and it will take at least until the next cycle (and Avare release, as it takes both).  You should see it soon though.

 

Great answer, Pete!  Thank you for that info and all your chart maintenance work. I'll look forward to the upcoming changes.

Just for the record, I've never called it a "flyway chart".  It's the Portland TAC.  Maybe that misinformation originates from Avare itself which calls out to "Download Flyway".

Wonder how many other Class C TACs are hiding on the reverse sides of the traditional TACs?

 

[John Wiley]

Peter wrote:
> what you showed is a terminal area chart (TAC), not a flyway chart.

This is interesting to me, so I looked it up on SkyVector just now. They include the margin info with the chart title: Seattle/Portland TAC.

It seems the Portland TAC the FAA added has VFR Transition Routes rather than the Flyways shown for Class B airports. PDX is still a Class C but presumably due to the significant amount of N/S transition traffic they're making it easier on pilots and controllers by routing us over PDX, or around it via either HIO, or the VPPCP VFR Waypoint using standard VFR altitude directional separation. Speaking of which, I guess you'd need to change altitudes on that VPPCP route unless below 3k' AGL? If so, the PDX transition looks least likely to have conflicting traffic, and you'd presumably still be talking to ATC for extra safety. Maybe nobody was using the V448 airway that's functionally nearly the same route.

On the FAA raster TAC chart page this SEA/PDX TAC has the hyphenated name Seattle-Portland, and I notice there are the other hyphenated TAC names:  Anchorage-Fairbanks, Baltimore-Washington, Dallas-Ft Worth, Denver-Colorado Springs, Minneapolis-St Paul, Puerto Rico-Virgin Islands, and Tampa-Orlando. I guess some, maybe all of these TACs already covered two major airports?

[Peter A. Gustafson]

On the FAA raster TAC chart page this SEA/PDX TAC has the hyphenated name Seattle-Portland, and I notice there are the other hyphenated TAC names:  Anchorage-Fairbanks, Baltimore-Washington, Dallas-Ft Worth, Denver-Colorado Springs, Minneapolis-St Paul, Puerto Rico-Virgin Islands, and Tampa-Orlando. I guess some, maybe all of these TACs already covered two major airports?

Interesting.  Its my impression that these names just indicate combined zip files to get the two charts in one download, but with independent tif images inside the zip.  (Or three+, if a flyway chart also exists).  We're actually using a bigger zip file the FAA distributes which contains all the vfr charts. Naming of the regional zips has not crossed my mind since they began offering the big zip.

[John Wiley]

Good point.