Title: NOTAM REALIGNMENT
1NOTAM REALIGNMENT
2Overall Goals
- Improve the quality of NOTAMs
- Provide meaningful information
- Enhance NOTAM interpretation
- Graphical depiction necessary
- Improve reliability and accessibility
- Digital data exchange will enhance filtering and
sorting - Provide a single source for all NOTAMs
- One collection and distribution point for all
information - Consolidate inefficient legacy systems for
improved customer service - Conform to ICAO standards
- Balance diverse customer needs
- Airlines, ATC, General Aviation, International,
Military - Complete Digital Capture and Delivery
- Enable automated fusion of published and dynamic
(NOTAM) data
3Modernization Roadmap
4Initial Policy Change
- Expanded definition of a Distant (D) NOTAM
- Adopted ICAO definition for aerodrome movement
area - Includes taxiways, ramps, aprons, lighting
- All D NOTAMs will be prefaced with a keyword
- Labeled unverified reports of hazards
- Information that meets NOTAM criteria but is
unverified will be tagged with (U) and
disseminated as D NOTAM - Applicable only where letters of agreement exist
- Labeled other information that doesnt meet ICAO
criteria - Other information that may impact aircraft
operations will be tagged with (O) and
disseminated as D NOTAM
5Effects of policy change
- Reclassified civil Local NOTAMs
- All current local civil NOTAMs become D NOTAMs
- Became effective January 2008
- Created keywords for all D NOTAMs for improved
sorting and parsing - AD AIRSPACE APRON COM
- NAV OBST (O) RAMP
- RWY SVC TWY (U)
- Enabled central distribution for all NOTAMs
- Standardized NOTAM policy and QA
6Current Examples
- Runway condition
- !MIV 05/123 MIV RWY 10/28 CLSD 0709021200-07090216
00 - Taxiway status
- !RDU 05/123 RDU TWY A CLSD BTWN A1, A2 TIL
0709011600 - Ramp status
- !MEM 05/123 MEM RAMP PAEW FEDEX CARGO EAST
- Other status information
- !LOU 05/123 LOZ (O) CONTROLLED BURN 6.5SM NORTH
TIL 0708302200
First word in the text area
7NOW IN EFFECT
8Implementation Activities
- NOTAM Realignment Working Group (NRWG)
- Stakeholder representatives from AIM, DoD, Flight
Service, and USNOF - Reviewing/modifying NOTAM Handbook
- Creating NOTICE for coordination and
dissemination - Safety Risk Management Panel
- Includes members from AFS, AOPA, ARP, ATA, AVN,
Continental Airlines, DoD, En Route Service Unit,
NBAA, Northwest Airlines, Sys Ops Service Unit,
Tech Ops Service Unit, Terminal Service Unit, US
Airways - Aeronautical Information and Flight Service
Station staff - Reviewing proposed changes to policy proposed by
NRWG - Identifying hazards and potential mitigations
- Town Hall Meetings
- User Outreach!!!!
- Domestic (including Dispatchers)
- Military
- International (IATA, Canada)
- Help from our Partners
9Digital NOTAMs
- Digital Capture
- NOTAMs Today
- Digital NOTAMs Concept of Operations
- NOTAM Origination
- NOTAM Delivery to Customers
- Convert Messages to Digital Packets
- A Common Aeronautical Model
10Digital NOTAM Concept of Operations
11(No Transcript)
12(No Transcript)
13(No Transcript)
14(No Transcript)
15(No Transcript)
16(No Transcript)
17(No Transcript)
18(No Transcript)
19(No Transcript)
20Concept of OperationsNOTAM Origination
ORIGINATORAirport Authority
EVENTNOTAM trigger (e.g., Runway damage)
- Eliminate free form text
- Pre-populated data entry screens
- Direct submission to USNS without manual
intervention - Tracking data for NOTAM
- Creator
- For more information
- Chain of Custody through data chain
21Concept of OperationsDistribution to customers
DATALINK
AI Database
Baseline Static Data
Change
VALIDATE Web
Service,Product Specs
PUBLISH Global AIM Net
Aeronautical Information Transactions
Change
Temporary Update (NOTAM)
Temporary Update (NOTAM)
- Consistent static and dynamic data
- Filter, Query and Sort
- Map and Display
22Modernization Roadmap
23Single Federal System
- Development underway for a federal system
consolidation - Joint development to compress Civil and Military
systems and database into a single baseline - Extend system capabilities
- ICAO Standardization
- Goal Single Federal system with full ICAO
implementation by Late 2009 - Multiple Views of shared data
- Based on a Common International Model
24Legacy verses ICAOComputer can create any output
from data
Common Data Model AIXM
Data
Views
25A common aeronautical data model
- AI Common Themes
- Identification and Operation What
- Period of Validity When
- Geometry Where
And Metadata
NOTAMTemporary change to aeronautical information
SNOWTAM, ASHTAMTemporary change to airspace and
surface conditions
Military AirspaceTemporary activation of
refueling and military operating areas
Route Availability / Traffic RestrictionTemporal
restriction on traffic flows and routing
AIM Aeronautical Information Management
26Summary
- NOTAM Realignment
- Policy Change went into effective January 28,
2008 - Customer Outreach
- Overall Goals
- Digital Capture
- Chain of Custody through NOTAM life cycle
- Automation
- Single Federal System in late 2009
- Digital NOTAMs
- Tower Lights
- Nav Outages
- Direct Airport Authority entry
- Legacy and ICAO
- Opportunities
- Assured Delivery to Facilities
- Runway Conditions and Military Airspace Management
27Thank You !
For more information Gary.bobik_at_faa.gov 202-493-14
07 Nfdc.faa.gov/aimnews Pilotweb.nas.faa.gov Notam
s.jcs.mil Tfr.faa.gov Naco.faa.gov
28 Airports Conference
Submitting Airport Data Changes to FAA Future
Advisory Circular
Presented by Gary Bobik, FAA April 6-8,
2008 Tulsa, Oklahoma
28
29Background of Airports AC
- Problem Description
- Airport operators may be unaware of the need to
reportairport data changes to FAA in a
consistent andtimely manner - Airport data is published in navigation
charts, databases and flight information
publications - Changes to certain airport data elements
directly impact instrument approach and
departure procedures, affecting the safety,
utilization and efficiency of the airport
30Background of Airports AC
- Solution
- Airports Division and Air Traffic Organization
workingtogether to release guidelines on how to
submit airport data changes to FAA -
- These guidelines will be contained in an
Airports Advisory Circular (AC) - Anticipated release date for AC is July 2008
31Purpose of Airports AC
- AC provides guidance on what, when and how to
submit airport data changes to the Federal
Aviation Administration (FAA)
32Who the AC affects
- Assists operators of all airports listed in
the Airport/Facility Directory (A/FD),
Supplement Alaska, and Pacific Supplement in
keeping their data up to date - Compliance with the guidelines is highly
recommended for operators of all public use
airports - Airport Improvement Program (AIP)
- Passenger Facility Charge (PFC) funds
- Operators of private use airports should
follow guidelines
33When to report data changes
- If a change has taken place, FAA needs to know
about it - Some data elements on or about the airport may
require coordination with Regional or Airports
District Office (ADO) and/or RAPT (Regional
Airspace Procedures Team) prior to change - AC will give guidelines on how/what to
coordinate
Immediately!!!
34How to report data changes now
Until AC is released http//nfdc.faa.gov
Important links
35How to report data changes now
36How to report data changes soon
When AC is released http//airports-gis.faa.gov
- FAA Airports Geographic Information System
(GIS) is the primary entry point for
requesting changes to airport data - Airports GIS is designed
- as the foundation for airport data within FAA
- to interface with other FAA systems and
processes to affect changes in those systems
or initiate airspace studies as required - AC will give guidelines on how/when to use
Airports GIS
37Questions? Contact Us
- Aeronautical Information Services (AIS) -
National Flight Data Center (NFDC) - E-mail    9-ATOR-HQ-AIS-AirportChanges_at_faa.go
v - Fax (202) 267-5322
- Phone (202) 267-8790
38Airfield Conditions Reporting
- What is the requirement?
- Code of Federal Regulations (CFR), Title 14
Aeronautics and Space, Federal Aviation
Administration, Department of Transportation - 14 CFR Part 139, Section 339, Airport condition
reporting - This section addresses the collection and
dissemination of airport condition reporting to
air carriers - To comply with this section, the CFR states that
the NOTAM system is to be used as appropriate,
along with other systems and procedures. - Indicates what information or airport conditions
are to be reported or affect the safe operations
of air carriers. - Who is responsible?
- The airport operators are responsible for
informing all applicable stakeholders - What methods are being used to disseminate this
information? - United States NOTAM System (USNS)
- Airport Web pages
- Auto updates
- Electronic direct distribution to airport
stakeholders
39Example of a commercial Airport Operations
dashboard
40Messages to Digital Packets
Message
Digital Packet
41Global change AIS to AIM
Classical AIS - publish documents
AIM System - manage data
Managing Product
Managing Data
Document content and format is described by -
ICAO Annex 15, Appendix 1 AIP Content - ICAO
Annex 15, Appendix 6 NOTAM format -
Data managed in the system is described by
models - Aeronautical Information Exchange
Model (AIXM) - AIXM Conceptual Model (AICM) -
Electronic AIP (eAIP) on-line presentation
format
- Specifications
- Content
- Quality
- Metadata
EuroControl Slide