Laserfiche WebLink
runways and taxi ways. Ms. Wedl explained that the study was initiated in response to San <br /> Francisco Airport's efforts to build a runway in the bay. Oakland felt it prudent to begin a <br /> parallel study to see what would be involved should the need arise to create a new runway for <br /> Oakland. However, neither study was ever finished. Oakland never did final review or <br /> adoption of the drafted study for two reasons — San Francisco stopped pursuing a runway in <br /> the bay, and the events of September 11 shifted all priorities to security and other concerns. <br /> The consultant's suggestions in the Airfield Planning Study have never been finalized by the <br /> Port one way or the other. <br /> Ms. Wedl agreed to create a chronology of the airport's plans and projects, along with the <br /> status of each element and an indication of whether or not the documents will be used for <br /> future planning or development. <br /> The Committee and airport representatives discussed touch - and -go flights at the North Field. <br /> There were approximately 2,600 touch - and -go operations at the North Field in May of this <br /> year. The Committee asked if that was a lot. The reply was that there can be many more. In <br /> the past several years, September 11 aside, all traffic at the North Field has declined. <br /> Airport staff described what would happen if the LLS on runway 27R was moved to 27L, as <br /> is called for in the Settlement Agreement. They explained that presently, touch - and -go <br /> traffic can operate primarily over airport and industrial property on runway 27L, while other <br /> operations, including instrument arrivals, continue on 27R. If the ILS is moved, touch -and- <br /> go flights would shift over to 27R and likely would encroach significantly on residential <br /> areas to avoid conflicts with arriving traffic coming into 27L. <br /> Committee members asked why this was not brought out in the Settlement Agreement. The <br /> reply was that the airport was not consulted on the matter, and the attorneys working on the <br /> agreement had not thoroughly examined the impacts of the change in ILS operations before it <br /> was added to the agreement. <br /> Airport representatives advised that if the second ILS is installed by the FAA, adding one to <br /> runway 27L and leaving the existing ILS in place on 27R, there would be a redundancy of <br /> systems to allow for more flexibility in addressing noise abatement. It will provide <br /> additional safety for airport operations should one of the systems go down, and it will allow <br /> gradual instrument decent approaches for both runways, which are quieter than step -down <br /> approaches. Also, with two 1LS in place, touch - and -go flights could continue on 27L during <br /> the daytime, but at night instrument arrivals could be moved over to 27L to avoid more <br /> neighborhoods. <br /> The FAA has completed its technical study of adding an ILS to 27L. Technically it is <br /> possible to do, however the environmental study is still underway. <br /> Committee members then had questions of the FAA representatives from the Air Traffic <br /> Control Tower. Jim Matthews and Les Scott advised that having two instrument landing <br /> systems would not increase traffic at the airport. There are specific FAA regulations that <br /> determine separations required for instrument arrivals to runways that are closer than 3,000 <br /> 2 <br />