1. Purpose and Scope:
   • Guidance and Best Practices: They offer guidance and best practices to aviation operators, manufacturers, and other stakeholders on how to comply with regulations and enhance safety.
   • Information Sharing: Circulars serve as a means for the FAA to share important safety information, including findings from safety studies, research outcomes, and lessons learned from incidents and accidents.
   • Regulatory Updates: They may also communicate changes in regulations, policies, or procedures affecting aviation safety.
2. Content:
   • Safety Management: Topics might include safety management systems (SMS), risk management, and safety assurance processes.
   • Operational Procedures: Guidance on best practices for flight operations, maintenance, air traffic control, and other operational areas.
   • Technology and Equipment: Information on the safe use of new technologies and equipment within the aviation industry.
   • Training and Education: Recommendations for training programs and educational initiatives to ensure that aviation personnel are well-prepared to manage safety risks.
3. Audience:
   • While primarily aimed at professionals within the aviation industry, including airlines, airport operators, maintenance organizations, and air traffic management, these circulars can also be relevant to regulatory bodies, safety organizations, and even the general public interested in aviation safety.
4. Impact on Safety Oversight:
   • Enhanced Compliance: By clarifying regulatory requirements and providing practical guidance, these circulars help ensure that industry stakeholders comply with safety standards.
   • Continuous Improvement: They encourage continuous improvement in safety practices by disseminating knowledge on emerging safety trends and innovative risk management strategies.
   • Safety Culture Promotion: Safety Oversight Circulars play a crucial role in promoting a positive safety culture within the aviation community by emphasizing the importance of safety and the role of each stakeholder in maintaining it.

Document Archive

List of FAA Safety Oversight Circulars a/o July 2017 [2 Pages, 1MB]

Loading...

Taking too long?

Reload document

| Open in new tab

Download [524.92 KB]

The post FAA Safety Oversight Circulars first appeared on The Black Vault.

An Aviat A-1C Husky, flown by actor Harrison Ford, was involved in an incident during landing at Orange County-John Wayne Airport, California.
The pilot had been cleared to land on runway 20L but touched down on the parallel taxiway C instead. On final approach the aircraft passed over American Airlines flight AA1456 that was taxiing on taxiway L for takeoff on a flight to Dallas, Texas.

Flight AA1456 was a Boeing 737-800, N959NN, with 110 passengers and a six crew members on board.

Flight tracking website Flightradar24 shows a calibrated altitude of 125 feet as the aircraft overflew taxiway L.

Audio Archive

• John Wayne Tower 1 (WAV, 6.5 MB) 

• John Wayne Tower 2 (WAV, 10.8 MB)

• John Wayne Recorded Line 2 (WAV, 9.9 MB)

• John Wayne Recorded Line 3 (WAV, 7.3 MB

Document Archive

 Harrison Ford Incident With Passenger Plane at California Airport, February 13, 2017 [41 Pages, 4.7MB]

Loading...

Taking too long?

Reload document

| Open in new tab

Download [4.40 MB]

The post Harrison Ford Incident With Passenger Plane at California Airport, February 13, 2017 first appeared on The Black Vault.

The FAA NAS Daily Events Log, prepared each day by the Federal Aviation Administration, provides a unique window into the odd and unusual events that occur within the National Airspace System.

 

The FAA Air Traffic Organization – office of System Operations Services prepares this document daily, comprising between five and ten pages per day, a wealth of information that include reportable events such as:

 

• Lost communications with aircraft, called NORDO ¬ no radio aircraft;
  emergency beacon code 7600;
• Displaying or requesting unusual deviations from assigned routing;
• Change of destination while on an IFR flight plan – COD;
• Security Incidents ¬ terminal evacuation, bomb threats, breach of airport
  perimeter, airport closure, airport security;
• Emergencies ¬ aircraft displaying emergency beacon code 7700 or reporting an
  emergency;
• Hijack ¬ aircraft displaying emergency beacon code 7500 or reporting a
  hijack;
• Aircraft experiencing a disturbance either on the ground or in flight;
• Special Interest Flights ¬ overflights by aircraft from certain nations;
• Special Penetration Air Defense Exercise ¬ SPADE:
• VIP movements;
• Special Speed Authorizations;
• Mechanical Problems;
• Laser Incidents;
• Intrusions into the National Capitol Region Control Center ¬ NCRCC
• And so on.

 

The number of incidents each day is large.

 

The NAS Daily Events Log covers the entire nation. Events are not separated  out geographically.

Back in 2013, I began requesting these logs, and it was not until September of 2015 that my requests began being answered.

Below, you will find the available logs, thus far.

Declassified NAS Daily Logs

 January 1, 2013 – January 31, 2013 [192 Pages, 56.2MB]

The post Federal Aviation Administration (FAA) NAS Daily Event Logs first appeared on The Black Vault.

Missile or UFO Buzzes Continental Airlines Flight

Although rarely a topic of news, the existence of UFOs is all too real to many military and civilian pilots.Hundreds, if not thousands of valuable reports of UFO encounters by pilots, and yet, according to the U.S. Military and Government, they don’t care about them.  In today’s post 9/11 world; maybe they should.

On May 29^th, 2009, a mysterious object displayed just how much of a ‘threat’ UFOs can be; alien spacecraft or not.

Continental Airlines Flight 2822 was en route to Greenville Spartanburg International Airport from Houston, when the pilot radioed in something odd was happening.  He witnessed what he said something that resembled “a missile” was flying below his aircraft, but he wasn’t seeing it on radar.

What was this mysterious object?

Shortly after the incident, I filed a Freedom of Information Act (FOIA) request to the FAA for all pertinent documents relating to the incident. Surprisingly, the request yielded some interesting results.

First, was the Daily Record of Facility Operation for the date of the incident.  The document stated that the, “object passed 200ft below and behind [aircraft]out of 13000 [feet]… No radar target displayed.”  Another reference in the document stated that it was a, “… missile passing below his aircraft by 100-200ft @13,000 [feet].”

Secondly, the FAA also supplied the air traffic controller’s communications. Sifting through the unneeded communications, and straining to hear the nearly completely inaudible audio, seven minutes and thirty seconds into the audio recording, a transmission states:

Unidentified Male #1: “About two updates ago, 2822 said something passed 200feet below him. He saw it with his eyes.”

Unidentified Male #2 (Presumably Air Traffic Controller): “Oh really??”

Unidentified Male #1: “That’s what he said.”

Unidentified Male #2 (Presumably Air Traffic Controller): “There isn’t anything out there… no primary…”

Unidentified Male #1: “Yeah, I didn’t see anything either… so…”

Unidentified Male #2 (Presumably Air Traffic Controller): “Ok thank you.”

As the recording goes on, eight minutes and fifty four seconds into the recording, the incident is discussed again:

Unidentified Male #2 (Presumably Air Traffic Controller): Inaudible.  Presumably asking for update on the mysterious object sighted.

Unidentified Male #3: “Sure.  The gentleman is now saying it looked like a missile.”

Unidentified Male #2 (Presumably Air Traffic Controller): “A Missile?”

Unidentified Male #3: “… flying in the opposite direction, rapidly below him… about 200ft below him.  I told my supervisor.”

Unidentified Male #2 (Presumably Air Traffic Controller): “Ok, and I’ll alert mine.” Inaudible.

So what was the object?  A missile? Another aircraft?  An alien spacecraft?  Subsequent investigations around the area for any launch sites for surface to air missiles yielded no results.

The remaining data on the CD-ROM given to me by the FAA also reportedly had radar data. The file was corrupt on the CD-ROM, and I am awaiting another copy.

The event still remains a mystery. But it also adds another piece of the puzzle that the military and government is ignoring.  Whatever these UFOs are; they are a threat.

The above incident was a huge threat to the twenty-six people on board Continental Flight 2822.  Luckily, this sighting was reported, and appears to have been taken somewhat seriously.

But more times than not, talk of a UFO sighting and reports of the aforementioned are simply scoffed at, ridiculed, and condemned.  It is this lack of seriousness towards the UFO topic, which roughly half of society believes has an extraterrestrial connection, that may one day get someone killed.

If it hasn’t already.

Document Archive

1. FAA Documents/Logs Relating to the Above Event [4 Pages, 1.05MB]
2. FAA Air Traffic Controller Communications [12.25 Minutes, 63MB]
3. Update: October 06, 2009 – Radar data received via a .ppb file. I am unclear how to open this, but put it here for archival purposes.  Does anyone know how to open this? DOWNLOAD THE RADAR DATA HERE [192MB]

The post UFO Buzzes Continental Airlines Flight 2822, June 3, 2009 (With Tower Recordings and Documents) first appeared on The Black Vault.