Manage facility records in accordance with FAAO Air traffic managers are responsible only for the routine collection and reporting of basic operational information as authorized in this order or by the appropriate service unit. Collection of any data shall be considered a secondary function and shall not interfere with the accomplishment of operational duties. Air traffic managers shall not permit their facilities to participate in special studies and surveys nor agree to the use of facility personnel to tabulate, prepare, or forward to outside organizations or parties any special summaries, abstracts, reports, or aeronautical data unless approved in advance by the Service Area office. Exercise care when preparing forms to ensure neatness and accuracy. Except as in subpara c, do not erase, strikeover, or make superfluous marks or notations.
|Published (Last):||6 June 2005|
|PDF File Size:||10.61 Mb|
|ePub File Size:||5.47 Mb|
|Price:||Free* [*Free Regsitration Required]|
Section 3. Greater emphasis is being placed on screening and selective dissemination of weather data. Selective dissemination takes into account the need to alert pilots to significant weather reports in sufficient detail to assist them in making decisions pertinent to flight safety and to provide the information an ATC facility requires to promote the safe and efficient use of its airspace. Approach control facilities not located at the airport to which radar service is being provided may issue wind data received from the tower at that airport.
The wind data may be transmitted to the approach control facility by TelAutograph, data communication circuit, voice lines, etc. The facility air traffic manager of an approach control that provides radar service to an Air Force Base must identify facility requirements for wind indicators, in writing, to the local USAF Air Weather Service Commander. Guidance to facility air traffic managers concerning the operational use of the LLWAS is as follows: Prior to operational use of LLWAS facilities, a letter to airmen must be published explaining, as a minimum, the location and designation of the remote sensors, the capabilities and limitations of the system, and the availability of current LLWAS remote sensor wind information if requested by the pilot.
NOTE- Towers having the responsibility for weather observations must comply with the requirements as specified in sub-para a, Wind Instrument Sensors. Facility managers may designate the use of displayed wind information oriented to the threshold end of the runway in lieu of airport winds where LLWAS expanded network systems or LLWAS that are integrated with TDWR are installed, if deemed operationally advantageous.
It is not intended that controllers specify the remote source when issuing these winds to arriving aircraft, except when an alert occurs.
This must be explained in the letter to airmen. During periods when wind shear is likely to occur or has been reported; e. The SMO will notify air traffic of any equipment that is out of tolerance.
Establish relative priorities on the visibility information at locations with two or more RVR or RVV runways where data is required for two or more runways. Display the information so that it is readily accessible to the controller having a need for it.
Flight inspection must validate the ESV. Before authorizing simultaneous takeoff and landing or simultaneous landing operations as specified in the current LAHSO directive. Coordinate with each of the appropriate Flight Standards field offices having jurisdiction at the airport according to the type of aircraft operations involved and with user groups as required by Para , Coordination of ATC Procedures, including the appropriate military authority where units are based at the airport.
Prepare a facility directive using the information as specified in the current LAHSO directive prescribing procedures for conducting these operations. The directive must contain a diagram that depicts the airport runway configuration, identifies the configuration to be used, and specifies the Available Landing Distance ALD from the landing threshold to the Hold-Short Point. Terminal Procedures Publications. Conduct user briefings at least 45 days before implementation.
Air traffic managers must obtain concurrence from the appropriate Flight Standards field offices and conduct a preliminary environmental review before conducting LAHSO. Before authorizing LUAW operations, conduct a review of the impact that airport configuration and local conditions may have on the application of LUAW procedures. Prepare a facility directive. The directive must prescribe items a through d. Items e through i must be included if applicable. Local procedures for conducting these operations.
Methods to assist the local controller in maintaining awareness of aircraft positions on the airport, for example, annotating flight progress strips or marking the location of aircraft with color-coded chips on a magnetic diagram of the airport.
The consolidation and staffing of positions. The requirements necessary for issuing a landing clearance with an aircraft holding in position. The safety logic system must be operated in full core alert runway configuration. The reported weather must be ceiling of feet or more. The reported visibility must be 2 miles or more.
Weather conditions, time of day, for example, prevailing light conditions. Fleet mix. Traffic volume; complexity restrictions. Obstructions or limitations to visibility from controller-to-aircraft and aircraft-to-aircraft perspectives. Local control can be combined with other local control positions to include tower associate local assist or local monitor position. The tower associate local assist position or a local monitor position must be staffed to permit more than one aircraft at a time to LUAW on the same runway between sunrise and sunset.
Do not authorize LUAW operations at an intersection between sunset and sunrise unless the following is implemented: The runway is used as a departure-only runway.
Only one aircraft at a time is permitted to LUAW on the same runway. At least 90 days before planned implementation, ATMs must submit the local directive outlining this operation to the appropriate Service Area Director of Air Traffic Operations for approval. The appropriate Service Area Director of Air Traffic Operations must be notified of any proposed operational changes for example, a change to the runway or taxiway for conducting LUAW operations.
The results of this review must be sent to the Director of Operations-Headquarters. At a minimum, the LOA must include: Required equipment to conduct the operation. Clear definition of the specific runway configurations and flows for the operation. Ceiling and visibility requirements.
Missed approach instructions, where applicable. A requirement that the aircraft type and intentions be made known to all controllers providing visual separation under these procedures. Terminate the operation when not permitted due to weather conditions.
Submit an operational needs request along with an update adding tower-applied visual separation procedures to their facility directives.
These documents must be approved by the appropriate Air Traffic Services Service Area Director prior to implementation. ATMs must maintain a copy of the approval correspondence. A facility directive must include where these procedures are able to be applied.
This must only include locations where the intervening taxi route is 1, feet or less between runway centerlines. Facilities must keep a copy of the approval correspondence issued by the appropriate Service Area Director of Air Traffic Operations. The Service Area Director of Air Traffic Operations must conduct an annual audit of multiple runway crossing operations authorized in their areas. The audit should include a review of all runway incursions attributable to multiple runway crossing clearances and all necessary documentation required above.
The email should describe the construction project in detail. Create, approve, and publish appropriate changes to local procedures. Ensure training for all operational personnel is completed and documented. Weather less than 2 SM visibility - departure only runway.
When determining speed requirements, consider, at a minimum, the following: Airspace constraints.
JO 7210.714 - FAA Form 7230-10, Position Log