FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Air Angels Bell 222 accident

15 Oct 2008 · Aurora, IL, United States

Bell 222 · Accident: controlled flight into terrain/object (CFIT) en route

From Northwestern Medicine Valley West Hospital Heliport (0LL7) to Children's Memorial Hospital Heliport (40IS)

Report a problem

Event

NTSB case
CEN09MA019
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
4 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Charter & commuter
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Bell 222

Aircraft type
Bell 222
Category
Helicopter
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N992AA
Operator
Air Angels
Onboard fatalities
Unknown
Route
From Northwestern Medicine Valley West Hospital Heliport (0LL7), Sandwich, ILTo Children's Memorial Hospital Heliport (40IS), Chicago, IL
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 135: Air Taxi & Commuter
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Controlled flight into terrain/object (CFIT)
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tower/antenna (incl guy wires)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Physical environment
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The emergency medical services (EMS) helicopter was on a night cross-country flight in visual meteorological conditions and was transporting an infant patient from one hospital to another when the accident occurred. During the flight, the pilot contacted DuPage Airport’s (DPA) air traffic control (ATC) facility, reported the helicopter's position and altitude of 1,400 feet above mean sea level (about 700 feet above ground level in Aurora, Illinois) to the air traffic controller, and asked permission to pass through the airspace surrounding the airport. The controller acknowledged the transmission and cleared the helicopter through DPA’s airspace but did not give the pilot specific instructions regarding his flight route because the pilot was flying under visual flight rules and had chosen his specific route of flight on a direct course from the departure point to the destination. (During preflight planning, the pilot should have identified the obstacles along the route of flight, including the radio station tower.) Subsequently, the helicopter struck a radio station tower while flying at the same altitude that had been reported to ATC. Video and still image evidence obtained during the investigation indicated that the strobe lights attached to the radio station tower were operational at the time of the accident.

The accident helicopter was not equipped with a terrain awareness and warning system (TAWS). TAWS detects terrain or other obstructions along the flightpath and provides pilots with an alert to take corrective action. On February 7, 2006, the National Transportation Safety Board (NTSB) issued Safety Recommendation A-06-15, which asked the Federal Aviation Administration (FAA) to require EMS operators to install terrain awareness and warning systems on their aircraft and to provide adequate training to ensure that flight crews are capable of using the systems to safely conduct EMS operations. The FAA responded that, while it would work with industry to address issues related to the installation of TAWS on EMS aircraft, it would address the issue of controlled flight into terrain by emphasizing effective preflight planning. The FAA further stated that the Radio Technical Commission for Aeronautics established a committee tasked with developing helicopter TAWS (H-TAWS) standards and that, in March 2008, the commission completed the development of minimum operational performance standards for H-TAWS. On December 17, 2008, the FAA published Technical Standard Order C194, “Helicopter Terrain Awareness and Warning System,” based on the commission standards. On January 23, 2009, the NTSB indicated that the continuing delays in development of a final rule to require H-TAWS were not acceptable. Pending issuance of a final rule to mandate the installation and use of TAWS on all EMS flights, Safety Recommendation A-06-15 was classified “Open—Unacceptable Response.” On November 4, 2009, the FAA responded by indicating that it was developing a notice of proposed rulemaking (NPRM) to address this recommendation and that it planned to complete work on the NPRM in January 2010; the NPRM had not been issued as of March 2010. On November 13, 2009, the NTSB reiterated Safety Recommendation A-06-15 in its report regarding the September 27, 2008, accident involving an Aerospatiale SA365N1, N92MD, operated by the Maryland State Police, which crashed during approach to landing near District Heights, Maryland. Safety Recommendation A-06-15 is on the NTSB’s Most Wanted List of Transportation Safety Improvements.

The radio station tower was depicted on the Chicago Aeronautical Sectional Chart, the Chicago Visual Flight Rules Terminal Area Chart, the Chicago Helicopter Route Chart, and as an obstruction on the air traffic controller’s radar display. Radar data obtained during the investigation showed the helicopter at a constant altitude and on a straight course to the point of impact with the tower.

The radar information was available to the air traffic controller. Additionally, the position and height of the tower were included in training materials that were to be memorized by the controllers at the ATC facility. According to interviews conducted of the controller on duty at the time of the accident, the accident helicopter was the only aircraft traffic in the area at the time. The controller reported that he was attending to administrative duties at the time that the accident occurred. FAA Order 7110.65, “Air Traffic Control,” paragraph 2-1-2, Duty Priority, states that issuance of safety alerts to aircraft takes first priority over other duties. Further, FAA Order 7110.65, paragraph 2 1-6, Safety Alert, states that controllers should issue a safety alert to an aircraft if they are aware that the aircraft is at an altitude that places it in an unsafe proximity to terrain, obstructions, or other aircraft and notes that “while a controller cannot see immediately the development of every situation where a safety alert must be issued, the controller must remain vigilant for such situations and issue a safety alert when the situation is recognized.” Evidence such as the controller’s failure to notice when the helicopter disappeared from the radar display after striking the antenna indicates that the controller was not monitoring the aircraft’s progress sufficiently to watch for hazards and issue safety alerts as required. While the NTSB recognizes that it was the pilot’s responsibility to “see and avoid” the radio tower, the controller also had a responsibility to issue an alert as required by FAA directives. Review of recorded communications showed that no warnings were issued to the pilot before the accident.

In addition, on August 28, 2007, as a result of an accident involving a Bombardier CL 600-2B19, N431CA, that crashed during takeoff from Blue Grass Airport, Lexington, Kentucky, the NTSB issued Safety Recommendation A-07-48, which asked the FAA to revise Federal Aviation Administration Order 7110.65, “Air Traffic Control,” to indicate that controllers should refrain from performing administrative tasks when moving aircraft are in the controller’s area of responsibility. The FAA responded that it would convene an internal work group to review the safety issues identified in this recommendation as they relate to ATC responsibilities and the impact of reassigning those duties to another position. This recommendation was classified “Open—Acceptable Response” on August 22, 2008. On April 10, 2007, the NTSB issued Safety Recommendation A-07-34 also as a result of the Lexington, Kentucky, accident, which asked the FAA to require all air traffic controllers to complete instructor-led initial and recurrent training in resource management skills that will improve controller judgment, vigilance, and safety awareness. The FAA responded that it had delivered crew resource management workshops, posters, and follow-up support to some larger ATC facilities. The NTSB responded that it was encouraged by the FAA’s actions but that such training should also be provided at smaller ATC facilities. This recommendation was classified “Open—Acceptable Response” on August 28, 2007. On January 15, 2009, the FAA responded that it was conducting training for controllers at larger facilities but did not indicate how it would perform training at smaller facilities.

Vice Chairman Hart did not approve this brief and filed a dissenting statement. The statement can be found in the public docket for this accident.

Probable cause

The pilot's failure to maintain clearance from the 734-foot-tall lighted tower during the visual night flight due to inadequate preflight planning, insufficient altitude, and a flight route too low to clear the tower. Contributing to the accident was the air traffic controller's failure to issue a safety alert as required by Federal Aviation Administration Order 7110.65, “Air Traffic Control.”

Vice Chairman Hart did not approve this probable cause and filed a dissenting statement. The statement can be found in the public docket for this accident.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09MA019
Event ID
20081016X94016
Case number
CEN09MA019
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2008-10-16.
  • API snapshot SHA-256: dad5222727c262242d5472d895d42001915c346b85cf2c24bb57e6a7986b4f92; retrieved 2026-09-13T19:33:53.606Z.