The AirSafe.com News

↑ Grab this Headline Animator

Showing posts with label irs. Show all posts
Showing posts with label irs. Show all posts

07 April 2010

NTSB Report on the February 2010 Crash into IRS Building

Most of the investigation into February's apparently deliberate crash of a small aircraft into a building containing dozens of employees of the Internal Revenue Service isn't being treated as an aircraft accident by the NTSB, but rather investigated as a criminal act by the FBI (Federal Bureau of Investigation). This is often the case in the US when an aircraft incident appears to be part of some sort of deliberate criminal act or act of terror.

While the NTSB will be responsible for completing part of the overall investigation, they recently released a preliminary report on the aircraft-related portion of this event. While it has much of the basic information contained in the initial AirSafeNews.com report, it does have some additional information.

NTSB Identification: CEN10FA124
Type of Flight: 14 CFR Part 91: General Aviation
Date: Thursday, February 18, 2010
Location: Austin, TX
Aircraft: Piper PA-28-236
Aircraft Registration: N2889D
Deaths: 2 (the pilot and one building occupant)
Injuries: About a dozen building occupants

Narrative: On February 18, 2010, approximately 0958 Central Standard Time, N2889D, a Piper PA-28-236 single-engine airplane, was destroyed after the pilot intentionally flew it into the side of an office building in Austin, Texas. The private pilot and an employee who worked in the building were killed. The airplane was registered to and operated by the pilot (Joeseph Stack). Visual meteorological conditions prevailed and no flight plan was filed for the personal flight conducted under 14 Code of Federal Regulations Part 91. The flight originated from the Georgetown Municipal Airport (GTU), Georgetown, Texas, at 0944 (GTU is about 20 miles north of the crash site).

Preliminary review of air traffic control communications and radar data revealed that after the pilot was cleared for take off from Georgetown Airport, he proceeded southbound and climbed to an altitude of 4,800 feet. During this time, a controller approved a radio frequency change and the pilot responded, "Eight niner delta thanks for your help have a great day." No further communications were made with the pilot. At 0954, the airplane was observed on radar descending out of 4,800 feet and making a turn toward the west. At 0957, the airplane was last observed on radar at an altitude of 1,000 feet on a southwesterly heading before the data ended.

The airplane collided with the office building between the first and second floors, and exploded on impact.

Aerial view of crash site

The airplane's engine, two (of three) propeller blades, and the right wing came to rest outside of the building. The empennage came to rest on the ledge of the building and was partially hanging over the edge.


The left wing, portions of the fuselage, and a propeller blade were found inside the building on the second floor. The flaps were found in the fully retracted position. The airplane was destroyed by the impact and the post-impact fire.

The weather at Austin Bergstrom International Airport (AUS), Austin Texas (about 15 miles SSE of the crash site), at 0953, was reported as calm wind, visibility 10 miles, few clouds at 25,000 feet, temperature 9 degrees Celsius, dew point 1 degree Celsius, and a barometric pressure setting of 30.24.

Additional Information
The story of this event is much more than just a simple plane crash. The pilot of the aircraft, Joseph Stack, had an ongoing and contentious relationship with the IRS revolving around tax issues with a series of his businesses. Prior to the crash, Stack and posted a long letter on his web site site that discussed some of these issues and that made violent threats against the US government. Shortly before his last flight, Stack also set fire to his house.

Among the unresolved issues is whether Stack had done anything to the aircraft, including adding extra fuel, to enhance the effect of the crash. It is unclear if the final NTSB report will address that issue. Also not yet resolved is if this event was the act of a lone individual or that of an organized group. However, initial speculation by various law enforcement agencies was that it was the act of a lone individual. If it is addressed at all, it will be addressed by the FBI or by some other government agency assisting in this investigation.

The airport used by Joseph Stack is a general aviation airport, and like most such airports there is no permanent security provided by TSA or any other federal agency. When the control tower is closed and the gates of the airport are closed, there is a system in place to allow anyone to gain access to the airport simply by driving through an automated gate. Security is mostly in the hands of airport users, who are encouraged to report unusual security situations.

Listen to ATC clearance for Joseph Stack (Source: LiveATC.net)

Austin, Texas office building before the crash

Austin, Texas office building after the crash


Fire rages at crash site




Photo Credits: Austin American-Statesmen, Google Earth

26 February 2010

Recent Aviation Safety Events and the Role of Sound

The past few days have seen three separate aviation safety related events that all have one surprising thing in common, sound. The most recent is the only one that was not connected with a fatal airplane crash, but could have a very significant effect on airline procedures in the future.

NTSB Recommends Routine Analysis of CVR Data
As reported by the USA Today and other media sources, (see pages 47 and 59), the NTSB made a recommendation (number A-10-29) which asks that the appropriate regulations be changed to allow airline operators to routinely "download and analyze all available sources of safety information, as part of their flight operational quality assurance program, to identify deviations from established norms and procedures; (2) provide appropriate protections to ensure the confidentiality of the deidentified aggregate data; and (3) ensure that this information is used for safety-related and not punitive purposes"

In plain English, the NTSB is recommending that airlines be allowed to review information from the cockpit voice recorder (CVR) to help improve safety. At AirSafe.com, we're having a hard time understanding this recommendation. While reviewing cockpit conversations may provide crucial insights that may prevent future incidents and accidents, and such reviews have been used with very positive results in past accident investigations, doing so routinely may not be so beneficial. One big issue is logistical, and two immediately come to mind, how to choose what to review, and how to record the most useful information.

A bigger problem is technological. Currently, cockpit voice recorders in the US are required to at least the last 30 minutes of cockpit conversation. Some record up to two hours, and in 2012 all will be required to record for at least two hours. However, the average airliner may spend many more hours per day in the air. Even if recorders are reviewed at the end of every day, most recorders would likely have only the most recent flight, and only the last part of the flight. Unless the NTSB is also suggesting a radical change in voice recorder technology and procedures to include enhancing the capability to record all conversations all the time, it is hard to see how reviewing a fraction of routine cockpit recordings can be either useful.

The other two audio related aviation events involved two very different crashes of private aircraft. The first was the February 17, 2010 crash of a Cessna 310 into an East Palo Alto, CA neighborhood. Although all three on board were killed, and several houses severely damaged, no one on the ground was injured.

Fatal Crash in East Palo Alto
The city of East Palo Alto, where the crash occurred, uses an advanced audio detection system that allows police to quickly find the locations of gunshots. This ShotSpotter system recorded the sounds of the crash from two locations. According to the NTSB, these recordings will be used in their investigation, and is the first time that such a recording will be used for forensic purposes.

Recordings taken from two of the sensor locations are below. While they may be useful for the investigation, they also represent the sound of three people being killed and a neighborhood in peril. Both begin with the sound of a plane's engines, followed by the sounds of the aircraft hitting power lines, and then followed by crashing and banging sounds as parts of the aircraft hit homes and cars. In one of the recordings, you can clearly hear the screams and cries of terrified residents as the plane struck the neighborhood.


Sounds of plane crash alone
(0.11)

Sounds of plane crash plus screams of neighbors
(0.11)

Aerial Attack in Austin
The day after the crash in East Palo Alto, Joseph Stack, who apparently had serious tax issues with the IRS, allegedly flew his aircraft into a building housing several IRS offices, severely damaging the building and killing one person inside.

Less than 20 minutes before this crash, and less than an hour after allegedly setting his own house on fire, the pilot took off from a Georgetown Municipal airport, a small airport north of Austin, and had what sounded like a normal conversation with air traffic control.

Listen to ATC clearance for Joseph Stack (Source: LiveATC.net)

What Does It All Mean?
Audio happened to connect these three events, but the message here may not be about audio at all but about technology. As the two private plane crashes showed, technology is reaching into more and more areas of everyday life, and will likely play an increasingly important role in how the public experiences aviation safety events and variety and sophistication of data available to crash investigators.

In the case of the two crashes, the audio technology existed for different purposes and just happened to record part of the flight of an accident aircraft. It is no different than the way that security or traffic cameras near airports sometimes happen to catch a dramatic event like a plane crash. The decision of the NTSB may not represent a policy shift within the aviation community as much as it represents an evolution of how the aviation safety community views the ways that existing technologies can be used to enhance safety.

18 February 2010

Man Deliberately Crashes Plane into Building in Austin

A small aircraft crashed into an office building in Austin, Texas. The crash was apparently a deliberate act. The building contained offices of the US Internal Revenue Service (IRS), and the pilot involved in the crash had a long and contentious relationship with the IRS. The pilot, Joseph Stack, had set fire to his house earlier, and had left a detailed letter on his web site that implied violent threats against the US government.

Stack's house caught fire at about 9:15 a.m. According to the FAA, the plane, a single-engine Piper Cherokee PA-28-236 Dakota (N2889D), took off from the Georgetown, TX municipal airport at 9:40 a.m. The crash site was about 20 miles (32km) SSE of the airport and the crash happened at about 10 a.m. The pilot and one person in the building were killed in the crash. At least one person in the building was seriously injured and airlifted to a burn center in San Antonio. About a dozen other building occupants were injured.

Austin police chief Art Acevedo stated that the crash “appears to be an intentional act, appears to be by a sole individual, and it appears this individual was targeting federal offices inside that building.” Numerous witness accounts were also consistent with a deliberate flight into the building.

Relevant Airline Security Issues
After the attacks of 9/11, the US government added multiple security measures affecting commercial airliners and private aircraft. While private aircraft face significant restrictions in the airspace around some areas, most notably the Washington, DC area, most areas have had no significant changes in procedures.

The airport used by Joseph Stack is a general aviation airport, and like most such airports there is no permanent security provided by TSA or any other federal agency. When the control tower is closed and the gates of the airport are closed, there is a system in place to allow anyone to gain access to the airport simply by driving through an automated gate. Security is mostly in the hands of airport users, who are encouraged to report unusual security situations.

Listen to ATC clearance for Joseph Stack (Source: LiveATC.net)

Notable Crashes of Small Aircraft into Buildings
12 September 1994 - After spending an evening with his brother consuming alcohol and smoking crack cocaine, Frank Eugene Corder, who was not a licensed pilot, stole a Cessna 150 and crashed into the South Lawn of the White House complex, with some parts of the airplane hitting the White House residence and causing minimal damage. Corder was killed, and no one else was injured.

5 January 2002 - A 15-year-old boy, who was not a pilot, stole a Cessna 172 and flew it into an office building in Tampa, FL. The pilot was killed and no one else was injured.

18 April 2002 - A Rockwell Commander 112 aircraft crashed into the Pirelli Tower in Milan Italy, killing the pilot and two others in the aircraft. A suicide was suspected, but not conclusively proven.

11 October 2006 - An aircraft carrying New York Yankees pitcher Cory Lidle and his flight instructor crashed into a 50-story building located in the upper east side of Manhattan. One person on the ground sustained serious injuries, two people on the ground sustained minor injuries, and the airplane was destroyed by impact forces and post crash fire.

Austin, Texas office building before the crash

Austin, Texas office building after the crash

Aerial view of crash site

Fire rages at crash site


Video of Still Smoking Building



Photo Credits: Jeff Lake, Austin American-Statesmen, Google Earth