Fandom

Airfield Management Wiki

NAMO

88pages on
this wiki
Add New Page
Talk0 Share

NAMO (NCOIC, Airfield Management Operations) ==Qualifications== Military personnel (SSgt and above) must hold AFSC 1C771 and have at least 3 years experience in AM. Note: The AFM may appoint a SSgt/5-skill level that has completed all upgrade/qualification training requirements and is only awaiting time requirements outlined in AFI 36-2201, AF Training Program Volume 3 for the award of the 7-skill level.

TrainingEdit

Military personnel must complete the following training requirements (if not previously completed) prior to assuming the NAMO position. DoD Civilians are authorize up to 6 months to complete the following training requirements if not previously completed. 2.3.2.1. AM-02, NCOIC, Airfield Management Operations PCG.

2.3.2.2. Airfield Criteria, Airfield Inspection and Maintenance, Wildlife Hazard Management, Airfield Driving and AM Contingency Operations CBTs. Note: Completion of AM Contingency CBT is not applicable to DoD Civilians.

2.3.2.3. USAF ORM Application and Integration Course (Basic Principles of ORM) available for download at AF Safety Center Training Website http://afsafety.af.mil/orm/training.asp.

2.3.2.4. Local Qualification Training (AF IMT 797, Job Qualification Standard).

2.3.2.5. Completion of the following courses are highly recommended for a NAMO or civilian equivalent. See Attachment 1 for a description of each course.

2.3.2.5.1. Advanced Airfield Manager Course.

2.3.2.5.2. Airfield Management Operations School.

ResponsibilitiesEdit

2.3.3.1. Establish performance standards, procedures and work priorities for personnel working in AMOPS section.

2.3.3.2. Develop procedures to process NOTAMs in accordance to AFI 11-208.

2.3.3.2.1. Develop backup procedures such as a LOP with another base to transmit NOTAMs.

2.3.3.2.2. Maintain a file copy of DD Form 2349, NOTAM Control Log or electronic equivalent in accordance with Air Force RDS, Table 10-9, Rule 1.00.

2.3.3.3. Ensure procedures in local weather support directive include notifying AMOPS section of hazardous weather.

2.3.3.4. Ensure a Secondary Crash Net (SCN) is installed and operational. Develop primary and backup procedures for operation of the SCN. Use a SCN form or checklist (e.g., MAJCOM, locally developed or electronic equivalent) to record information (e.g., real-world/exercise) received over the Primary Crash Alarm System (PCAS) and/or relayed over the SCN.

2.3.3.5. Conduct airfield inspections and checks.

2.3.3.6. Assign two-letter operating initials to each individual for use in daily operations.

2.3.3.7. Develop a monthly schedule to ensure effective utilization of personnel working in the AMOPS section.

2.3.3.8. Develop Operating Instructions (OI), Quick Reaction Checklists (QRC), logs, etc. to perform AM activities and responsibilities listed below. OI’s may be combined into a single Airfield Management Operations OI. All AM personnel must review OI’s and QRCs at least quarterly. Use a MFR, log or electronic equivalent to document reviews of OI’s/QRCs and maintain a file copy in accordance with Air Force RDS, Table 13-06, Rule 4.00.

2.3.3.8.1. Inbound/outbound aircraft (e.g., MAJCOM/Local Flight Following Log, Flight Progress Strip or electronic equivalent).

2.3.3.8.2. Distinguished Visitors (DV) arrivals/departures.

2.3.3.8.3. Aircraft requiring special handling (e.g., Air Evacuation and Hazardous cargo).

2.3.3.8.4. Airfield restrictions (e.g., Prior Permission Required (PPR), Official Business Only (OBO), quiet hours, closures, etc.). (See Chapter 6)

2.3.3.8.5. Airfield Safety and Compliance Inspection Program. (See Chapter 2)

2.3.3.8.6. Airfield Driving Program. (See Chapter 4)

2.3.3.8.7. FLIP Management.

2.3.3.8.8. Weather Warnings, Watches and Advisories.

2.3.3.8.9. In-Flight Emergency (IFE)/Ground Emergency (GE).

2.3.3.8.10. BASH/Wildlife responses and BWC declarations/notifications.

2.3.3.8.11. Broken Arrow (if applicable).

2.3.3.8.12. On/Off-base incident.

2.3.3.8.13. Anti-Hijacking.

2.3.3.8.14. Unauthorized Aircraft Landing.

2.3.3.8.15. Overdue Aircraft.

2.3.3.8.16. Hydrazine Incident.

2.3.3.8.17. Bomb Threat.

2.3.3.8.18. Hung Ordnance and Hot Armament.

2.3.3.8.19. Runway Incursion/Controlled Movement Area Violation (CMAV) events.

2.3.3.8.20. Pyramid Alert/Recall procedures.

2.3.3.8.21. Flight Safety and Local NOTAM procedures.

2.3.3.8.22. Corrective action/coordination for airfield discrepancies or outages.

2.3.3.8.23. Customs/Agriculture/Immigration. Publish response agency, time and required notification action in the FLIP.

2.3.3.8.24. Facility/Building Evacuations. Include procedures to review and update the Evacuation/ Relocation Kit at least quarterly.

2.3.3.8.25. Mishap Notification/Response. (See AFI 13-204)

2.3.3.8.26. Emergency Locator Transmitter (ELT).

2.3.3.8.27. Civil/Foreign Aircraft inbounds.

2.3.3.8.28. Training Program. (See Chapter 7)

2.3.3.9. Develop a shift-briefing checklist or electronic equivalent. The shift-briefing checklist must include as a minimum:

2.3.3.9.1. Airfield Status (e.g., Active Runway, Runway Surface Condition/Runway Condition Reading, current NOTAMs, Bird Watch Condition, Arresting Gear, etc.).

2.3.3.9.2. Airfield Construction.

2.3.3.9.3. Navigational Aids status.

2.3.3.9.4. Aircraft Rescue and Fire Fighting capability.

2.3.3.9.5. Equipment status (e.g., phones, UHF/VHF radios, vehicle, etc.).

2.3.3.9.6. Personnel working on the airfield (e.g., grass mowers, snow and ice removal operations, contractors, etc.).

2.3.3.10. Develop procedures for using the AF IMT 3616 to record significant incidents/events during each tour of duty. Entries may be handwritten, typed or computer generated. Each AMOS will sign the AF IMT 3616 under Signature of Supervisor(s) at the end of his or her shift. Their signature certifies the entries are correct and the form contains all required entries. First entry will state name and operating initials of individuals coming on duty. Annotate all actions on the events log. Detailed documentation may be maintained on other forms or checklists. Maintain the AF IMT 3616 on file in accordance with Air Force RDS, Table 13-06, Rule 01.00.

2.3.3.10.1. When using a computer to maintain a continuous log to cover an entire day, the AMOS may sign on/off electronically (e.g., 1430 J. JONES OFF, T. SMITH ON SHIFT AS AIRFIELD MANAGEMENT OPERATION SUPERVISOR). Entering the name of the relieved AMOS serves the same purpose as signing the certification statement at the top of the form. At the end of the day, the AMOS on duty will print and sign the certification statement at the top of the AF IMT 3616. Entries may be corrected at any time before printing the hard copy, but must be coordinated with the AMOS on duty when the entry was made.

2.3.3.10.2. The AFM, DAFM and NAMO must review and initial daily logs for trends on the airfield or in AMOPS section (e.g., equipment outages, facility maintenance, etc.). Units may specify additional items requiring documentation. As a minimum, the following items must be annotated on the AF IMT 3616:

2.3.3.10.2.1. Shift changes, opening and closing AMOPS section.

2.3.3.10.2.2. Personnel working on the airfield (e.g., grass cutters, contractor construction personnel, CE repair crews etc.) and coordination.

2.3.3.10.2.3. Issue, revision and cancellation of NOTAMs.

2.3.3.10.2.4. Airfield Inspections/Checks.

2.3.3.10.2.5. RSC/RCR.

2.3.3.10.2.6. BWC declarations.

2.3.3.10.2.7. IFEs/GEs to include aircraft arresting system engagements. AFI13-213 29 JANUARY 2008 21

2.3.3.10.2.8. Runway Incursions.

2.3.3.10.2.9. PCAS/SCN tests and activations.

2.3.3.10.2.10. Active Runway changes.

2.3.3.10.2.11. Weather Warning, Watch and Advisories.

2.3.3.10.2.12. Closure of aerodrome, runways, taxiways and aprons.

2.3.3.10.2.13. NAVAID and airfield lighting outages.

2.3.3.10.2.14. Daily inspection of aircraft arresting and airfield lighting systems by CE.

2.3.3.10.2.15. Equipment malfunctions/outages (e.g., FAA flight planning system, back-up generator).

2.3.3.10.2.16. Reduced Aircraft Rescue and Fire fighting capability.

2.3.3.10.2.17. Daily flight planning room checks.

2.3.3.10.2.18. SOF calls.

2.3.3.11. Develop flight plan processing procedures for the AOI (e.g., fax, e-mail, canned or telephone). All aircraft departing Air Force installations must have a flight plan on file with the AMOPS section prior to takeoff. Exception: Civil aircraft (e.g., Scheduled Air Carrier, General Aviation, etc.) are exempt from this requirement when published in the AOI. Use a MAJCOM/ Local Flight Following Log, Flight Progress Strip or electronic equivalent to record and track aircraft arrivals and departures.

2.3.3.11.1. Use DD Form 175, Military Flight Plan, DD Form 1801, DoD International Flight Plan, or other authorized forms according to AFI 11-202 Volume 3, General Flight Rules and FLIP General Planning. Original flight plans will not be accepted via radio. Locally filed flight plans can be amended via any means provided an original flight plan is on file at the departure AMOPS section.

2.3.3.11.2. An aircraft commander on a stopover flight plan or a weather/maintenance divert may re-file or amend their flight plan with an AMOPS section via any means (radio, telephone, etc.). Note: AMOPS personnel must verify an original flight plan clearance was filed by contacting the original departure location via telephone or sending a flight movement message query. An aircraft commander (normally operating on a VFR flight plan requesting to pick up an IFR flight plan) can request to air file a flight plan with the AMOPS section if the change does not penetrate an Air Defense Identification Zone (ADIZ). AMOPS personnel must also verify an original flight plan was on file.

2.3.3.11.3. Flight plans must be filed in person and maintained on file in accordance with Air Force RDS. Table 13-07, Rule 3.00. Exception: The AFM may authorize base and tenant flying units to fax, email, or electronically file flight plans in LOA or AOI. The LOA or AOI must indicate who will maintain the original flight plan on file.

2.3.3.11.3.1. Flight plans may be processed by a MAJCOM Flight Planning Cell provided procedures (e.g., MAJCOM Concept of Operations (CONOPS), Directive or Supplement) outline the flight planning process, security requirements and AM notifications at departure and destination airfields. Note: Coordinate procedures through HQ AFFSA/A3A/ A3O prior to implementation. Flight planning cells must ensure AMOPS sections and other DoD Base Operations/Flight Planning Facilities are notified of proposed flight plans departing and/or arriving their airfield. AM personnel will not modify/change flight plans for Flight Managed Missions without approval from the flight planning cell/flight managers. (See AFI 11-255, Volume 3 Integrated Flight Management Responsibilities and Procedures) 2.3.3.11.3.2. At locations where more than one agency has the capability to file flight plans, the host wing AM function has overall responsibility for the following actions unless delineated otherwise in the AOI or LOA with the unit:

2.3.3.11.3.2.1. Flight following/tracking aircraft.

2.3.3.11.3.2.2. Search and Rescue.

2.3.3.11.3.2.3. Aircraft security and anti-hijacking.

2.3.3.11.3.2.4. Amend, Cancel, and re-filing flight plans.

2.3.3.11.3.2.5. Producing traffic count data or other manpower activity associated with the flight plan filing process that may diminish or add manpower to the primary host unit.

2.3.3.11.4. Develop procedures to receive computer generated flight plans for transient aircrews as required.

2.3.3.12. Ensure a current on-base crash grid map is available in the AMOPS section. Maintain a current off-base crash map in the AMOPS section as applicable. Obtain maps from the CE Readiness Flight. (See AFI 10-2501)

2.3.3.13. Develop a customer quality feedback questionnaire or electronic equivalent to solicit customer feedback on the quality of AM services and aircrew support. Maintain a file copy of the questionnaire in accordance with Air Force RDS, Table 33-42, Rule 04.00.

2.3.3.14. Review and initial flight plans, traffic logs, NOTAMs and other supporting flight data information for accuracy, completeness and conformance with established directives.

2.3.3.15. Develop procedures to ensure AM personnel do not release names of individuals allegedly involved in an aircraft incident or accident to agencies outside U.S. Air Force channels. All inquires from non-mishap response personnel must be directed to Public Affairs. (See AFI 13-204, AFI 91-204)

2.3.3.16. Establish the capability for transient aircrews to make long distance, commercial and Defense Switched Network (DSN) calls.

2.3.3.17. Maintain current publications, charts, forms and FLIPs necessary to support base and transient flying operations. Electronic media may be used for all items to include FLIPs. (See Attachment 1)

2.3.3.18. Include an entry in the FLIPs advising transient aircrews of the classified materials (Communication Security (COMSEC), cryptographic equipment, etc.) availability and storage restrictions.

2.3.3.19. Appoint a primary and alternate FLIP manager to accomplish the following: AFI13-213 29 JANUARY 2008 23

2.3.3.19.1. Order FLIPs and aeronautical charts for base units according to established distribution procedures. (See AFI 11-201, Flight Information Publications, AFI 14-205, Identifying Requirements for Obtaining and Using Cartographic Geodetic Products and Services, and National Geospatial-Intelligence Agency (NGA) Catalog of Maps, Charts, and Related Products)

2.3.3.19.1.1. If a new FLIP is not received by the effective date, mark material as “OUTDATED Contact AMOPS Section.”

2.3.3.19.1.2. Electronic products on the NGA website may be used as a backup if new FLIPs are not received by the effective date.

2.3.3.19.1.3. Complete and return the Quality Feedback Card for each occurrence and retain a copy for your records.

2.3.3.19.2. Review local airfield data in each new FLIP edition for accuracy and consistency with information published in other FLIPs (e.g., approach plates, enroute supplement, area planning, etc.), base publications (e.g., AOI, OPLANs) and flight planning room displays.

2.3.3.19.2.1. Use a memo for record, log or electronic equivalent to document FLIP reviews. As a minimum, include the FLIP Title, Effective Date, Review Completion Date, Discrepancies Noted, Corrective Action, Date Corrected and Name/Rank of individual performing the review.

2.3.3.19.2.2. Maintain a file copy of FLIP reviews in accordance with Air Force RDS, Table 13-06, Rule 4.00.

2.3.3.19.3. Prepare and coordinate non-procedural FLIP changes with local agencies then submit the change in accordance with General Planning, Chapter 11. Note: The AFM must approve non-procedural FLIP change requests. Ensure non-procedural FLIP changes are tracked until corrected.

2.3.3.19.4. Initiate NOTAM action for non-procedural FLIP changes, as necessary.

2.3.3.19.5. When appropriate, include the type and extent of pavement in the touchdown zone (surface one) of the runway and in the rollout or middle zone of the runway (surface two) in the "Remarks" section of the Enroute Supplement. For example: "First 1,000 feet of runway 25 and first 2,150 feet of runway 07 is concrete. Middle 5,450 feet of runway 07/25 is a porous friction surface."

2.3.3.19.6. Publish non-standard airfield systems or configurations (e.g., signs, lighting, markings, arresting gear, etc.) in the FLIP and AOI.

2.3.3.19.7. Publish accurate pavement condition index and runway weight bearing restrictions in FLIPs based on current pavement evaluation reports.

2.3.3.20. Develop procedures to check the Flight Planning Room for accuracy, currency and availability of materials (e.g., FLIPs, charts, forms, etc.) during each shift. Document each check on the AF IMT 3616.

2.3.3.21. Ensure qualified AMOPS personnel (military only) assigned to a rotating shift schedule and needed to perform airfield management duties are submitted for Basic Allowance for Subsistence (BAS) due to assigned duties and unusual work hours. Commanders will determine whether AM personnel are authorized BAS in accordance with guidance established in DOD 7000.14-R, Volume 7A, Chapter 25, DOD Financial Management Regulation—Subsistence Allowance. However, commanders retain the authority to stop this BAS if it is determined not to be in the best interest of the member and the Air Force.

2.3.3.22. Utilize the AFFSA AM Operations and Procedures CoP to access current Airfield Management guidance, quick references and messages. Air Force Portal registration and AFFSA AM Operations and Procedures CoP membership is required to access and download products.[1]

NotesEdit

  1. AFI13-213

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.

Also on Fandom

Random Wiki