My WebLink
|
Help
|
About
|
Sign Out
Home
10A Action Item 2017 0306
CityHall
>
City Clerk
>
City Council
>
Agenda Packets
>
2017
>
Packet 2017 0306
>
10A Action Item 2017 0306
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/1/2017 10:41:56 AM
Creation date
3/1/2017 10:41:46 AM
Metadata
Fields
Template:
CM City Clerk-City Council
CM City Clerk-City Council - Document Type
Agenda
Document Date (6)
3/6/2017
Retention
PERM
Document Relationships
Reso 2017-029
(Reference)
Path:
\City Clerk\City Council\Resolutions\2017
Reso 2017-030
(Reference)
Path:
\City Clerk\City Council\Resolutions\2017
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
61
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Download electronic document
View images
View plain text
Attachment A <br />Summary Table <br />Attachment - Proposals for Revising Northern California Metroplex – Alameda County/Contra Costa County <br />Page 5 <br />SFO TRUKN DP <br /> <br /> <br /> The Forum requests the FAA consider <br />TRUKN proposals in two sections <br />informally defined as – TRUKN North <br />(encompasses GRTFL and DEDHD) and <br />TRUKN East (encompasses HYPEE and <br />COSMC). <br /> <br />TRUKN North: The Forum requests that <br />the FAA restore the historical traffic <br />concentrations in the topographically <br />lower areas where it existed prior to <br />NextGen and that communities grew and <br />developed under. To accomplish this, the <br />Forum requests the FAA move the <br />current GRTFL and DEDHD tracks <br />westward of Highway 13 and East <br />Oakland to reestablish and restore <br />historical patterns of SFO departing <br />traffic in this area as the proposed <br />mitigation. The Forum also requests the <br />FAA adjust the TRUKN waypoint to <br />better restore the legacy earlier turn <br />northward over the Bay and keep the <br />lower altitude portions of the climb <br />occurring over water land instead of <br />communities in Alameda, East Oakland <br />and San Leandro if this would result in <br />less noise impact. <br /> <br />TRUKN EAST: The Forum requests the <br />FAA restore historical traffic <br />concentration where it existed prior to <br />NextGen and where communities grew <br />and developed under. To accomplish this, <br />the Forum requests the FAA consider <br />adding a track to the area of the existing <br />COSMC and HYPEE tracks. The Forum <br />additionally requests that the FAA direct <br />Air Traffic Control to vector traffic along <br />all resulting tracks in the TRUKN East <br />area to better echo and restore historical <br />concentration and dispersion of SFO <br />departing traffic. <br />TRUKN North Comments - Prior to <br />NextGen, SFO traffic in TRUKN North was <br />vectored over a wide corridor from the San <br />Francisco Bay to the Oakland Hills with the <br />dominant majority of traffic concentrated <br />over an almost due north corridor from <br />Alameda and northward over West Oakland, <br />the City of Piedmont, Berkeley and <br />northwards. The turn northward after <br />departure from SFO was further west over <br />the Bay relative to the current TRUKN <br />waypoint and kept traffic more westward <br />than the current concentrated flight paths <br />along GRTFL and DEDHD. <br /> <br />TRUKN East Comments - Prior to NextGen, <br />SFO traffic in the TRUKN East area was <br />concentrated in two distinct corridors <br />roughly corresponding to the NextGen <br />HYPEE and COSMC RNAV tracks. <br />However, there was a significant shift <br />southeastward and concentration of traffic <br />along HYPEE when it was published. This <br />shifting and further concentration of traffic <br />one mile south significantly increased noise <br />for residential areas there. <br />END <br /> <br />235
The URL can be used to link to this page
Your browser does not support the video tag.