Kenai Flight Service Station

Home Page

Public Notices

• Emergency Flight Rules/Security NOTAMs
• Other FSS Contacts

Emergency Flight Rules and Special Security NOTAMs

The events of September 11, 2001 prompted the FAA to issue several emergency flight rules and special security notices in the form of FDCNOTAMs. The emergency rules for VFR flight and IFR flight within the United States have now been cancelled. Several special security notices instructing pilots to review intercept procedures spelled out in the Aeronautical Information Manual (AIM), prohibitions on “loitering” in the vicinity of sensitive locations, and restrictions on flight near certain sporting events are still in effect, and are published in the Notice To Airmen publication.

On September 1, 2007 the Air Defense Identification Zone (ADIZ) around Washington DC was revised. All pilots planning to visit the Washington, DC area should be completely familiar with the new ADIZ prior to flying in that area. Learn about the new ADIZ.

In August, 2006 a new NOTAM was issued concerning all flights to, from or over-flying the United States. Pilots planning to cross into United States airspace from Canadian airspace must comply with these instructions whether or not they have landed in Canada.

These procedures govern the actions of all pilots flying in the United States. Remember that non-compliance may result in the suspension or revocation of your pilot privileges, and that, in extreme cases, force may be used against violators. Follow the links above to see the full text of the FDCNOTAMs.

Please be aware that security NOTAMs may change at any time. When such changes occur, Kenai FSS may re-institute “Kenai FSS Information (Alpha code)”. We have created a link from our pages to the FAA's Temporary Flight Restriction (TFR) Web site for the convenience of our customers. Nevertheless, the safest way of making sure you have all necessary information for your flight is to speak to a Preflight Briefer.

Top of Page

Flight Service Contact Numbers

For the most current information, contact Kenai FSS and speak with a briefer.

• In the Kenai/Soldotna Area: 1-907-283-7211. Toll free: 1-866-864-1737.
• Fairbanks FSS toll-free number: 1-866-248-6526
• Juneau FSS toll-free number: 1-866-297-2236
• For the remainder of the country.

Top of Page

Questions or Comments Welcome

NOTAMs, TFRs, SUAs

Please be sure to review current disclaimers and/or information limitations of these websites.

• NOTAMs
  • Oakland Domestic NOTAMs are searchable under KZOA or ZOA
  • Oakland Oceanic NOTAMs are only available under KZAK
• TFR
• SUA
• National Weather Service Oakland Center Weather Service Unit NWSZOACWSU

FAI FSS

• NOTAM Overview
• Temporary Flight Restriction (TFR) Overview
• Pilot's Guide To Airspace Restrictions(PDF)
• Graphic TFRs
• Graphic Special Use Airspace (SUA)
• NOTAM SEARCH
• NOTAM Contractions(PDF)

ATO Security

The System Operations Security Directorate mission is to:

• Protect the U.S. and its interests from threats and other major incidents involving the Air Domain
• Take appropriate action to mitigate the impact of threats, incidents, and associated security measures on the safety and efficiency of the National Air Space (NAS)
• Act as a single focal point for our security aviation partners (e.g., DOD, DHS, LE, etc) and ATO facilities to enable safe and efficient integration of security operations and initiatives into the NAS
• Translate the complex requirements of outside agencies for implementation by the ATO as part of the ATO’s Air Navigation Service Provider (ANSP)
• Facilitate, adjudicate, and manage the external release of NAS data to entities outside the FAA through its NAS Data Release Board (NDRB)

Aviation System Standards

With the public being our most important customer, Aviation System Standards, provides services to ensure the standard development, evaluation, and certification of airspace systems, procedures, and equipment for customers worldwide.

Aviation System Standards

Prepare for Technology Refresh and Upgrade Planning (p)

AMS Lifecycle Phase:In-Service Management >>> Technology Refresh Assessment (TRA)

Description

In this phase, systems are in place and operating, enhancements and/or modifications to the system are developed and tested and hardware and/or software is added or replaced. The system should be monitored for continued performance in accordance with user requirements, and needed system modifications are incorporated. The operational system needs to be periodically assessed to determine that the system is maintaining an acceptable level of security control. Operations can continue as long as the system can be effectively adapted to respond to the FAA's needs. Managing the configuration of the system and providing for a process of continuous monitoring are two key elements of information security at this phase.

Tasks

• Recertify the system as prescribed in the Information Systems Security Program Implementation Guide (SCAP) depending on the level of impact to the NAS or non-NAS systems
• Continue to monitor the configuration of the system
• Test new hardware and software for security vulnerabilities before inserting it into the operational system
• Review the system requirements to ensure they still meet the users' needs

Resources

• NIST Special Publication 800-64, Security Considerations in the Information System Development Life Cycle
• ATO — Information Systems Security Program Implementation Guide (SCAP)

FAA Information Systems Security (ISS) Engineering Process

The Information Systems Security (ISS) Engineering website is a checklist that guides you throughout the acquisition management systems (AMS) phases to perform the security related activities using the ISS engineering processes.

The ISS Engineering process tasks support the phased AMS decisions, as shown in the Acquisitions Management Systems (AMS) logo above. Each Program Office or Service Organization shall tailor its ISS Engineering activities to meet its program milestones and use its System Engineering Management Plan (SEMP) to tailor its ISS Engineering activities and process tasks.

Each phase has ISS Engineering products that support the other Systems Engineering (SE) elements, consistent with contents of the Systems Engineering Manual (SEM) section 4.8.6.3, "Information Security Engineering Process Tasks." The Information System Security Plan (ISSP) is a key ISS Engineering planning document for every FAAIT program. The ISSP provides an overview of the system, presents an approach for meeting associated security requirements, and delineates responsibilities and rules for controlling access and use of information and related assets within the system. The program ISSP is a living document, prepared early in system lifecycle and updated regularly during program/system development. Above AMS logo summarizes the ISS Engineering process task alignment with the AMS phases.

For comments or feedback contact 9-atop-hq-isse-info@faa.gov.

Begin In-Service Management (ISM) for Systems Engineering Milestones: Technology Refresh Assessment (TRA)

(Determine: To continue, update (Tech refresh, P3I) or end the Systems Development Lifecycle needs for the (ISM))

Review

• FAAFASTAMS Lifecycle Phases and Decisions guidance website:
  • In-Service Management (ISM)
• FAAFASTISS Flow Chart of the ISM section.
• The ISSP for the system assessed.
• OMB Exhibit 300, Attachment 1, 2, & 3.

Update

• ISS section of the Final Requirement Document (fPR).
• Vulnerability and risk assessment for the Security Risk Assessment (SRA).
• SCAP with your Service Unit/Service Area Certification Team Lead.
  • Verify if recertification is required.

Generate

• Technology refresh and/or upgrade of the system assessed.
  • Prepare for Technology Refresh and Upgrade Planning (p)
  • NISTSP 800-64, “Security Considerations in the Information System Development Life Cycle”
• For disposal of the system.
  1. Follow ISSP
  2. Archive information
  3. Sanitize media
  4. Dispose of hardware and software.

Obtain

• DAA signature(s) of Certification and Authorization package (SCAP).
  • Service Unit/Service Area Certification Team Lead and ISSO.
  • ATO Designated Approving Authority (DAA), Information System Security Certifier (ISSC), and Information System Security Manager (ISSM).

Deliverables

1. Updated OMB Exhibit 300, Attachment 1, 2, & 3
   • ISS section of the Final Requirement Document (fPR).
2. Updated Security vulnerability and threat assessment for the SRA.
3. Updated SCAP documents.
4. DAA signature(s) of the SCAP documents.

End ISM for Systems Engineering Milestones: TRA & AMS Phase: ISM

Obtain Security Authorization and Accreditation (o)

AMS Lifecycle Phase:Solution Implementation

Description

Security Authorization ensures that the security controls are effectively implemented through established verification techniques and procedures and gives FAA officials confidence that the appropriate safeguards and countermeasures are in place to protect the FAA's information system.

Security Accreditation provides the necessary assurance that an information system can securely process, store, or transmit information that is required. This accreditation is granted by a senior official (DAA) and is based on the verified effectiveness of security controls to some agreed upon level of assurance and an identified residual risk to FAA assets or operations.

FISMA requires periodic testing and evaluation of the security controls in an information system to ensure that the controls are effectively implemented. The comprehensive evaluation of security control effectiveness through established verification techniques and procedures (also known as security certification) is a critical activity conducted by the agency or by an independent third party on behalf of the agency to give agency officials confidence that the appropriate safeguards and countermeasures are in place to protect the agency's information system. In addition to security control effectiveness, security certification also uncovers and describes the actual vulnerabilities in the information system. The determination of security control effectiveness and information system vulnerabilities provides essential information to authorizing officials to facilitate credible, risk-based, security accreditation decisions.

OMB Circular A-130 requires the security authorization of an information system to process, store or transmit information. This authorization, granted by a senior agency official, is based on the verified effectiveness of security controls to some agreed upon level of assurance and an identified residual risk to agency assets or operations (including mission, functions, image, or reputation). The security accreditation decision is a risk-based decision that depends heavily, but not exclusively, on the security testing and evaluation results produced during the security control verification process. An authorizing official relies primarily on:

• The completed Information Systems Security Plan (ISSP)
• The Security Test Plan and Test Results Report
• The Plan of Action and Milestones (POAM) for reducing or eliminating the information system vulnerabilities

In making the security accreditation decision on whether to authorize operation of the information system and to explicitly accept the residual risk to agency assets or operations.

Tasks

• Submit the SCAP to the ISSM, ISSC, ISSCA, and the DAA for review
• Update the SCAP based on comments received from the certification officials' reviews
• Resubmit SCAP to ISSM, ISSC, ISSCA, and/or DAA for review
• After DAA approval, the system is able to go operational in the field

Resources

• NIST Special Publication 800-64, Security Considerations in the Information System Development Life Cycle
• FAA's ISS Handbook
• ATO — Information Systems Security Program Implementation Guide (SCAPs)

Begin Solution Implementation (SI) for AMS decision point: #5

(Re-baseline:OMB Exhibit 300, Attachment 1, 2 & 3 for the In-Service Decision (ISD))

Note: The symbol "*" indicates that the FAA firewall access is required to view this link.

Review

• FAAFASTAMS Lifecycle Phases and Decisions guidance website:
• Solution Implementation (SI)
• In-Service Decision (ISD)
• FAAFASTISS Flow Chart of the SI section
• OMB Exhibit 300, Attachment 1, 2, & 3.

Update

• Security information for Solicitation Information Request (SIR), Contract Statement of Work (SOW) and Contract Data Requirement List (CDRL).
• Vulnerability and risk assessment for the Security Risk Assessment (SRA).
  • This is to be performed independent of the Integrated Product Team (IPT).
  • “Update Vulnerability and Risk Assessment” (f)
• CONOPS of system.
  • “Update the CONOPS and Security Requirements” (g)
  • To include ISS section to the CONOPS depending on level of impact of the NAS system.
• ISS section for the Final Requirement Document (fPR).
  • Security Interfaces document for inclusion in Interface Requirement Document (IRD).
  • “Integrate Security Requirements with System Requirements” (h)
  • “Integrate Security Architecture and Design” (i)
• The ISSP.
  • “Update the ISSP” (j)
• SCAP to reflect actual fielded systems with your Service Unit/Service Area Certification Team Lead and ISSO. Must complete the SCAP documents before operating the system.
  • Locate the “ATOISS Implementation Guide * ” and follow the link “SCAP” for the SCAP guidance document.
  • “Create Final Security C&A Documents” (n)

Generate

• Security testing on system baseline and refine solution as needed for ISD/commissioning.
  • This is to be performed independent of the IPT.
  • “Develop Security Test Plans and Procedures” (k)
• Users guide, training plans, and contingency/disaster recovery plans.
  • “Develop User’s Guides, Training, and Contingency Plans” (l)
  • “Conduct Security Testing” (m)

Obtain

• DAA signature(s) of Certification and Authorization to connect and operate system in the NAS.
  • “Obtain Security Authorization and Accreditation” (o)
    • ATO Designated Approving Authority (DAA), Information System Security Certifier (ISSC), and Information System Security Manager (ISSM).

Deliverables

1. SCAP Implementation Guide(Reference: SCAP implementation guide - Section 4.1.1 *)
2. Baselined OMB Exhibit 300, Attachment 1:
   • ISS section of the Final Requirement Document(fPR).
     • Security Interfaces in the IRD.
3. Baselined OMB Exhibit 300, Attachment 2, & 3
4. The security information for SIR, SOW & CDRL.
5. DAA signature(s) of Certification and Authorization to connect and operate the system in the NAS.

End SI for AMS decision point: #5 & AMS Phase: SI