Aviation Investigation Report A12H0001
The Transportation Safety Board of Canada (TSB) investigated this occurrence for the purpose of advancing transportation safety. It is not the function of the Board to assign fault or determine civil or criminal liability.
between Beechcraft V35B, N6658R
and Piper PA-28-140, N23SC
Warrenton, Virginia, 6 nm S
28 May 2012
The Beechcraft V35B Bonanza (registration N6658R, serial number D-103232) was in a shallow climb, heading southbound, in the vicinity of Warrenton, Virginia. The aircraft was operated under visual flight rules for the purposes of a biennial flight review. The Piper PA-28-140 (registration N23SC, serial number 28-21217) was in level flight, also under visual flight rules, and was heading in a southeasterly direction. At 1604:45 Eastern Daylight Time, the aircraft collided approximately 1800 feet above sea level. The Beechcraft broke up in flight, and the pilot and flight instructor were fatally injured. There was a post-impact fire at the Beechcraft accident site. The pilot of the Piper, who was the sole occupant of the aircraft, conducted a forced landing in a pasture, approximately 6 nautical miles south of the Warrenton-Fauquier Airport. The pilot sustained injuries, which required examination at a local hospital.
The Piper was registered to a Federal Aviation Administration (FAA) employee, and the Beechcraft was registered to a National Transportation Safety Board (NTSB) employee. Given the unique circumstances surrounding the ownership and operation of the accident aircraft, the United States, as the State of Occurrence, represented by the NTSB, and Canada, represented by the Transportation Safety Board (TSB), respectively requested and accepted delegation of the accident investigation, in accordance with paragraph 5.1 of Annex 13 to the Convention on International Civil Aviation (International Civil Aviation Organization).
Ce rapport est également disponible en français.
History of the flight
The pilot of the Beechcraft V35B Bonanza arrived at Warrenton-Fauquier Airport (KHWY) at 1515 Footnote 1 to pick up an instructor in order to complete a flight review. Footnote 2 With the certified flight instructor on board, the Beechcraft departed at 1545, headed south, and climbed to 3000 feet above sea level (asl). No enroute air traffic services were requested by the pilots of the Beechcraft, nor were they required to do so in the airspace in which they were operating. The recorded radar data indicated that the Beechcraft was transmitting on transponder code 1200. Footnote 3
At 1555, the northbound Beechcraft was 13 nautical miles (nm) south of the Culpeper Regional Airport (KCJR) at 3000 feet asl. At this time, the Piper PA-28-140 departed KCJR under visual flight rules (VFR) and was climbing eastward. At 1600, the Beechcraft started a descent (Figure 1). As the Beechcraft descended, their closest point of approach was 600 feet vertical and 0.9 nm lateral.
It is not known if either pilot saw the other aircraft, or if the 2 aircraft were on the same radio frequency.
At 1601, the Piper levelled at about 2000 feet asl and was proceeding to the ANTNY intersection (Appendix A - RNAV [GPS] RWY 33 Warrenton-Fauquier). The pilot contacted the terminal radar approach control (TRACON) for the area, which is called the Potomac Consolidated TRACON (PCT) Barin sector, and requested an area navigation (RNAV) approach to Runway 33 at KHWY (Appendix B – Airspace and Airports). The PCT Barin sector controller asked the Piper pilot to standby, as the controller was coordinating with another controller regarding 2 instrument flight rules (IFR) aircraft crossing north of the Piper’s position. Radar information showed 2 VFR aircraft in the vicinity in addition to the Piper and the Beechcraft.
At 1602:18, the PCT Barin sector controller acknowledged the Piper pilot’s request and asked the pilot to enter a discrete code of 4323 on the transponder. As a result, a data block showing the aircraft registration, altitude and speed was associated with the Piper’s radar target. A controller position handover Footnote 4 was then conducted, starting at 1602:34. The relieved controller was interrupted by a call from an aircraft, and then resumed the handover briefing. Information passed to the incoming controller included a number of arrivals and departures from Washington Dulles International Airport (KIAD) and Manassas Regional Airport (KHEF), the crossing IFR traffic and the Piper’s request for an RNAV approach. The briefing was concluded at 1603:18. When the relieved controller saw that the incoming controller had control of the situation, the relieved controller left the position to go on break. The incoming controller then requested the Piper to squawk ident Footnote 5 and confirm the airport and type of approach requested. The Piper complied with the request and pressed the ident button on the transponder. At 1603:33, having missed the ident, the controller again requested that the Piper squawk ident; the controller then focused on another aircraft destined for KHEF.
At 1604:08, the audio conflict alert (CA) sounded and the visual alert appeared at the controller’s position. The incoming controller heard and observed the alert; the relieved controller had left the position and did not hear or see the alert. The audio alert for the conflict ceased after approximately 5 seconds, but the visual alert Footnote 6 continued to be displayed. When the CA sounded at 1604:08, the Beechcraft had started a slow climb and was headed southbound on a converging course with the Piper. The Beechcraft was about 500 feet below and approximately 0.9 nm east of the Piper. The controller noted the vertical spacing, assessed that there was no conflict, and returned to ensuring that separation was going to be achieved between the 2 IFR aircraft to the north on crossing tracks. In the 44 seconds from 1604:10 to 16:04:54, the controller was communicating with several IFR aircraft in the airspace. The controller issued several instructions to the pilot of 1 of the 2 IFR aircraft on crossing paths, including a level‑off altitude in 2 miles and a frequency change, with the last acknowledgement from that airplane beginning at 1604:35. At 1604:38, the controller issued a frequency change to a third IFR aircraft, and received an acknowledgement at 1604:40. At 1604:43, a pilot from another airplane (fourth IFR aircraft) checked onto the frequency; the controller issued an altitude assignment, advised this pilot that the aircraft was number 3 to land at its destination, and received acknowledgement at 1604:50. There were no CAs associated with any of the preceding aircraft.
At 1604:54, the PCT Barin sector controller, confident that separation was going to be maintained between the IFR aircraft, advised the pilot of the Piper that the aircraft had been radar identified. Footnote 7 The controller then asked the pilot to climb to 3000 feet asl, and indicated that there was traffic in the area. There was no response from the Piper as the collision had already occurred.
The Piper and the Beechcraft collided on a 45° convergent path from the Piper’s left side. The Beechcraft’s landing gear was retracted, and the flaps were set to 15°. Field-of-view analysis showed that there was a high likelihood that each aircraft was visible to the other, meaning that no aircraft structure would have obscured the view of either approaching aircraft (Appendix C – Approximate Fields of View). The Beechcraft pilot’s view may have been obscured by the instructor’s head, depending on each pilot’s seat position and posture, but the instructor’s view would have been unobstructed. There were no indications that either aircraft manoeuvred to avoid the other.
As the 2 aircraft collided, the Piper’s propeller severed the Beechcraft’s fuselage just aft of the pilots’ seats. Without the empennage and ruddervators Footnote 8 attached, the Beechcraft’s cockpit and wings entered a dive, resulting in an impact that was not survivable and a post-impact fire. The right ruddervator and aft portion of the empennage/tail cone of the Beechcraft remained embedded in the Piper’s fuselage. The Piper’s engine failed, and there was a loss of airspeed indication. The pilot then completed a successful forced landing into a pasture. During the landing, the aircraft skidded through a narrow path in a line of trees bisecting the pasture. The right wing detached during this impact. There was no post-impact fire.
The pilot of the Piper sustained injuries during the impact with the Beechcraft, as well as head injuries during the touchdown and impact with trees. These injuries required medical attention. The Piper was not equipped with a shoulder harness.
Good visual meteorological conditions were reported in the Warrenton area. The 1555 aerodrome routine meteorological report (METAR) at KHWY indicated that winds were 180° true (T) at 5 knots, visibility was 10 statute miles, sky condition was clear, temperature was 32°C, dew point was 26°C, and altimeter setting was 29.95 inches of mercury. An observation taken 10 minutes after the accident was essentially the same, except that the indicated winds were 200°T at 3 knots, and the temperature was 31°C. The elevation of the sun was 49°, with an azimuth of 258°T. The sun’s estimated bearing was 140° relative to the Piper and 093° to the Beechcraft.
Pilot and Potomac consolidated TRACON Barin sector controller qualifications and experience
Records indicate that the Beechcraft pilot and instructor, as well as the Piper pilot, were certified and qualified for flight in accordance with existing regulations. Toxicology results for all pilots involved were negative. The sleep and rest history for the pilots was such that fatigue was not considered to be a factor.
The Beechcraft pilot had over 1600 hours total flight time, and the instructor had just over 4000 hours. The Piper pilot had approximately 11 100 hours flight time.
The original and relieving controller were certified and qualified in accordance with existing policies and regulations. Their work and rest schedules were such that fatigue was not considered to be a factor. The original controller had over 30 years total experience, with the last 9 years at PCT. The relieving controller had 21 years total experience, with 4.5 years at PCT.
Records indicated that both aircraft were certified, equipped, and maintained in accordance with existing regulations and approved procedures. The Piper was a white aircraft with blue markings, while the Beechcraft was white with red markings. Nothing was found to indicate that there was any airframe failure or system malfunction prior to or during the flight. All control surfaces were accounted for, and all damage to the aircraft was attributable to the collision and impact forces. Both aircraft were equipped with functioning mode C transponders.
Investigators observed that the landing light switch in the Piper was in the on position. There were no other lights for conspicuity, such as strobes, installed on the Piper. The Beechcraft had a strobe light system installed. The post-impact fire damage sustained by the Beechcraft precluded determination of any exterior lighting switch positions.
From what could be determined, no devices limiting the field of view for flight in simulated instrument meteorological conditions were in use by the pilots or found in either wreckage.
The flight paths of both aircraft were predominantly through Class E airspace associated with KCJR and KHWY (Appendix B – Airspace and Airports). Air traffic control services are provided to IFR aircraft in Class E airspace. These services are also provided to VFR pilots if requested and if the controller is able to provide such services. Footnote 9 VFR aircraft are allowed to operate in Class E controlled airspace and do not require specific pilot certifications or equipment, and there are no specific requirements regarding arrival or through flight entry and air traffic control clearances. No separation services are provided to VFR aircraft. Footnote 10
The FAA air traffic control manual states in part that, in Class E airspace, traffic advisory service and flight following will be provided to the extent possible, depending on the controller’s higher-priority duties and other limitations (e.g., radar limitations, volume of traffic, frequency congestion, or controller workload). Radar and non-radar traffic advisories do not relieve the pilot of his or her responsibility to see and avoid other aircraft. Pilots are cautioned that there are many times when the controller is not able to give traffic advisories concerning all traffic in the aircraft’s proximity. In other words, when a pilot requests or is receiving traffic advisories, it should not be assumed that all traffic advisories will be issued.
Section 4-1-15 of the FAA Aeronautical Information Manual (AIM) states in part:
Pilots receiving this service are advised of any radar target observed on the radar display which may be in such proximity to the position of their aircraft or its intended route of flight that it warrants their attention. This service is not intended to relieve the pilot of the responsibility for continual vigilance to see and avoid other aircraft. Footnote 11
In addition, section 4-1-16 of the AIM states:
A safety alert will be issued to pilots of aircraft being controlled by ATC if the controller is aware the aircraft is at an altitude which, in the controller’s judgment, places the aircraft in unsafe proximity to terrain, obstructions or other aircraft. The provision of this service is contingent upon the capability of the controller to have an awareness of a situation involving unsafe proximity to terrain, obstructions and uncontrolled aircraft. The issuance of a safety alert cannot be mandated, but it can be expected on a reasonable, though intermittent basis. Once the alert is issued, it is solely the pilot’s prerogative to determine what course of action, if any, to take. This procedure is intended for use in time critical situations where aircraft safety is in question. Noncritical situations should be handled via the normal traffic alert procedures. Footnote 12
Conflict alert system
The primary purpose of the air traffic control (ATC) system is to prevent a collision between aircraft operating in specific airspace and to organize and expedite the flow of traffic. A conflict alert system Footnote 13 was developed to assist controllers in recognizing and preventing collisions between aircraft. The purpose of the system is to determine if aircraft are in dangerous proximity to other aircraft or are on a course that will put them in dangerous proximity to other aircraft. Each aircraft track recorded by the radar system is processed by the conflict alert system once per radar scan. Footnote 14 A primary filter reduces the number of track pairs processed by the system to a level that can be accepted by the software.
A track pair that passes the primary filter is processed by 4 conflict alert detection algorithms to determine if the track pair is in conflict. To do so, the altitude and the lateral dimensions are considered separately. For example, it may be safe for 2 tracks to be at the same lateral position and separated by 500 feet in altitude, but it is not safe for tracks to be at the same altitude and separated by 500 feet laterally.
A conflict situation is determined by first evaluating an altitude conflict interval. The time at which the 2 aircraft are predicted to first come in conflict in altitude is the beginning of this time interval. Next, a lateral conflict interval is determined. The time at which the 2 aircraft are predicted to first come in lateral conflict is the beginning of this time interval. If these 2 time intervals overlap, the greater of the 2 times is the time at which the aircraft pair will first come into altitude and lateral conflict concurrently. This is called the time of violation (TOV). If TOV is less than or equal to the look-ahead time, Footnote 15 then a conflict exists, and the controller will be alerted. As long as there is a conflict, the alert message will be displayed.
Once all specified parameters are met, an alert is issued. When this occurs, a single aural alert, which lasts for 5 seconds, is generated at the controller’s position. At the same time, the blinking characters CA (acronym for conflict alert) appear on the controller’s display, in the first line of the data blocks of each aircraft involved. There are 2 related types of alerts that can be displayed: a CA or a Mode C intruder (MCI) alert. The only difference between a CA and an MCI alert is that in an MCI alert, only 1 aircraft in the pair is assigned a specific transponder code (i.e. associated); the other aircraft is un-associated (in this case squawking 1200). In a CA, both aircraft are tagged (i.e. associated). All software processing and display output is the same, whether 1 or both aircraft are associated. A range of adaptation parameters, such as geographic filters or aircraft manoeuvring sensitivity, can also be applied to determine whether or not an alert is to be issued.
Conflict alert system at Potomac Consolidated TRACON
PCT does not have any approved exceptions for adaptation parameters of the conflict alert system that would suppress CA alerts. Currently, there are no adapted MCI inhibit regions at PCT. The area where this accident occurred was not in any locally adapted region. This means that the conflict alert processing would have been the same in any TRACON for these 2 aircraft as it was in PCT. PCT staff conduct a daily aural check per display, as well as a monthly system check. The CA aural alert was also verified after the accident, and was working in accordance with specified operational parameters. The CA aural alert is designed to sound for 5 seconds.
The MCI conflict alert (the CA) for the Piper and Beechcraft was initially displayed at 1604:08 and lasted 51 seconds. Footnote 16 An aural alert sounded at the PCT Barin sector controller’s position at the time the alert was first displayed; the aural alert continued for approximately 5 seconds, then stopped, in accordance with the system design. The CA was first displayed for at least 2 radar updates while the 2 aircraft were 500 feet apart vertically, which is the accepted minimum separation between VFR aircraft. Footnote 17 The PCT Barin sector controller saw the alert being displayed and assessed that there was no conflict. The controller then focused again on the 2 IFR aircraft to the north. No further action was taken related to the alert. The PCT Barin sector controller did not issue a safety alert, traffic advisory Footnote 18 or any other verbal message to advise the Piper that a CA was being displayed for the aircraft prior to the collision. Once the IFR traffic was dealt with, the controller focused again on the Piper, and issued a traffic advisory to the Piper pilot. The collision had already taken place.
Federal Aviation Administration air traffic control procedures - safety alerts
The FAA Order JO 7110.65U includes the following procedures for advising aircraft of potential unsafe conditions:
Issue a safety alert to an aircraft if you are aware the aircraft is in a position/altitude which, in your judgment, places it in unsafe proximity to terrain, obstructions, or other aircraft. Once the pilot informs you action is being taken to resolve the situation, you may discontinue the issuance of further alerts. Do not assume that because someone else has responsibility for the aircraft that the unsafe situation has been observed and the safety alert issued; inform the appropriate controller.
- The issuance of a safety alert is a first priority (see para 2−1−2, Duty Priority) once the controller observes and recognizes a situation of unsafe aircraft proximity to terrain, obstacles, or other aircraft. Conditions, such as workload, traffic volume, the quality/limitations of the radar system, and the available lead time to react are factors in determining whether it is reasonable for the controller to observe and recognize such situations. 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.
- Recognition of situations of unsafe proximity may result from . . .
automatic altitude readouts, Conflict/Mode C Intruder Alert, . . . or pilot reports. Footnote 19
It also states:
b. Aircraft Conflict/Mode C Intruder Alert.
Immediately issue/initiate an alert to an aircraft if you are aware of another aircraft at an altitude that you believe places them in unsafe proximity. If feasible, offer the pilot an alternate course of action. Footnote 20
Section 2-1-2 of the FAA Order JO 7110.65U states in part:
a. Give first priority to separating aircraft and issuing safety alerts as required in this order. Good judgment must be used in prioritizing all other provisions of this order based on the requirements of the situation at hand . . .
NOTE−Because there are many variables involved, it is virtually impossible to develop a standard list of duty priorities that would apply uniformly to every conceivable situation. Each set of circumstances must be evaluated on its own merit, and when more than one action is required, controllers must exercise their best judgment based on the facts and circumstances known to them. That action which is most critical from a safety standpoint is performed first. Footnote 21
Section 2-1-21 states in part:
Unless an aircraft is operating within Class A airspace or omission is requested by the pilot, issue traffic advisories to all aircraft (IFR or VFR) on your frequency when, in your judgment, their proximity may diminish to less than the applicable separation minima. Where no separation minima applies, such as for VFR aircraft outside of Class B/Class C airspace, or a TRSA [terminal radar service area], issue traffic advisories to those aircraft on your frequency when in your judgment their proximity warrants it. Footnote 22
PCT controllers receive initial training on the conflict alert system with regards to reacting to a CA. Specifically, they are trained on the appropriate phraseology to use when informing the pilots that an alert has been observed. Controllers were not trained on the parameters or thresholds that could trigger a CA, or more precisely on what aircraft trajectory conditions must be met before the system issues an alert. Back to basics briefings, annual refresher training, and a computer based instruction (CBI) module for controllers included short presentations on safety alerts. Included in the CBI module is a number of scenario-based situations for which the controller chooses the correct phraseology for the given circumstance. The CBI module covers safety alerts, traffic advisories, and merging target procedures.
National Transportation Safety Board Recommendations Related to Conflict Alert Functions
In response to 10 controlled flight into terrain (CFIT) accidents and 1 mid-air collision accident, the National Transportation Safety Board (NTSB) issued 4 safety recommendations in 2006 (A-06-44 through -47, dated 12 July 2006) related to CAs and minimum safe altitude warning (MSAW) functions. The letter containing the recommendations highlighted the following related to conflict alerts:
In each of the above accidents, the MSAW and conflict alert software performed as designed and attempted to alert controllers about the detected hazards. However, none of the warnings resulted in timely ATC intervention because controllers were either aware of the alert but failed to take action or they remained unaware of the hazardous situation despite the activation of the alerting systems. . . . The Board is concerned about the lack of effectiveness of these alerting systems, which failed to reliably capture the attention of otherwise apparently conscientious and attentive controllers.
The NTSB notes that presenting conflict alert warnings using both visual and aural methods is beneficial; the ATC task environment often requires controllers to be responsible for multiple subtasks that do not involve constantly looking at their displays. However, the current design of MSAW and conflict alert warning systems does not provide effective redundant cuing of the alert condition because the aural component of the warning automatically silences after a few seconds. The current design of these systems also does not provide any assurance that a controller has recognized and acknowledged the warning.
FAA Order 7110.65 makes no distinction between VFR and IFR operations regarding the issuance of safety alerts when hazards to flight are observed. Controllers are required to use their judgment, remain vigilant for situations in which aircraft are in danger, and issue, as a first-priority duty, a safety alert when such situations are recognized.
As a result, the NTSB made the following recommendation (A-06-44) to the FAA:
Redesign the minimum safe altitude warning (MSAW) and conflict alert systems and alerting methods such that they reliably capture and direct controller attention to potentially hazardous situations detected by the systems. Implement software changes at all air traffic control facilities providing MSAW and conflict alert services.
In response to the NTSB’s recommendation, the FAA commissioned a research paper. The paper concluded in part that:
. . . The high false-alarm rate does not appear to induce cry wolf behaviour in the context of en route ATC conflict alerts. . . . There is no need to substantially modify conflict alert algorithms, but the conflict alert system may be modified to address difficult-to-visualize conflicts. Footnote 23
The NTSB’s assessment of the FAA’s actions regarding recommendation A-06-44 resulted in an “open – acceptable” Footnote 24 classification.
Limitations of the see-and-avoid principle
When weather conditions permit, regardless of whether an operation is conducted under instrument flight rules or visual flight rules, vigilance shall be maintained by each person operating an aircraft so as to see and avoid other aircraft. Footnote 25
The see-and-avoid principle is based on active scanning, the ability to detect conflicting aircraft and to take appropriate measures to avoid such aircraft. See-and-avoid can be affected by limitations in what can be seen and other activities, such as in-flight monitoring of instruments, radio communications, flight training exercises and interactions with an instructor, as well as navigation or conduct of simulated instrument approaches. This means the crew’s full attention may be diverted from active scanning for traffic.
In 1991, a report was produced by the Australian Transport Safety Bureau Footnote 26 that provides an overview of the major factors that limit the effectiveness of the see-and-avoid principle in preventing mid-air collisions.
The report presented the following summary, which is consistent with known physiological limitations of the human eye:
Cockpit workload and other factors reduce the time that pilots spend in traffic scans. However, even when pilots are looking out, there is no guarantee that other aircraft will be sighted. Most cockpit windscreen configurations severely limit the view available to the pilot. The available view is frequently interrupted by obstructions such as window-posts which totally obscure some parts of the view and make other areas visible to only one eye. Window-posts, windscreen crazing and dirt can act as ‘focal traps’ and cause the pilot to involuntarily focus at a very short distance even when attempting to scan for traffic. Direct glare from the sun and veiling glare reflected from windscreens can effectively mask some areas of the view.
Visual scanning involves moving the eyes in order to bring successive areas of the visual field onto the small area of sharp vision in the centre of the eye. The process is frequently unsystematic and may leave large areas of the field of view unsearched. However, a thorough, systematic search is not a solution as in most cases it would take an impractical amount of time.
The physical limitations of the human eye are such that even the most careful search does not guarantee that traffic will be sighted. A significant proportion of the view may be masked by the blind spot in the eye, the eyes may focus at an inappropriate distance due to the effect of obstructions as outlined above or due to empty field myopia in which, in the absence of visual cues, the eyes focus at a resting distance of around half a metre. An object which is smaller than the eye’s acuity threshold is unlikely to be detected and even less likely to be identified as an approaching aircraft.
The pilot’s functional visual field contracts under conditions of stress or increased workload. The resulting ‘tunnel vision’ reduces the chance that an approaching aircraft will be seen in peripheral vision.
The human visual system is better at detecting moving targets than stationary targets, yet in most cases, an aircraft on a collision course appears as a stationary target in the pilot’s visual field. The contrast between an aircraft and its background can be significantly reduced by atmospheric effects, even in conditions of good visibility.
An approaching aircraft, in many cases, presents a very small visual angle until a short time before impact. In addition, complex backgrounds such as ground features or clouds hamper the identification of aircraft via a visual effect known as ‘contour interaction’. This occurs when background contours interact with the form of the aircraft, producing a less distinct image.
Even when an approaching aircraft has been sighted, there is no guarantee that evasive action will be successful. It takes a significant amount of time to recognise and respond to a collision threat and an inappropriate evasive manoeuvre may serve to increase rather than decrease the chance of a collision.
Because of its many limitations, the see-and-avoid concept should not be expected to fulfil a significant role in future air traffic systems.
Many of these issues were echoed in a research article entitled “Midair Collisions: Limitations of the See-and-Avoid Concept in Civil Aviation”. Footnote 27 The article states in part:
Finally, the see-and-avoid concept misleads pilots and controllers by encouraging overconfidence in visual scanning while neglecting its physical and behavioral limitations and mitigation strategies. While visual scanning is necessary to prevent midair collisions, especially of aircraft flying slowly in close proximity and not yet on collision courses, it is not sufficient. Potential mitigation strategies include: 1) pilot and ATC training on physical and behavioral limitations of the see-and-avoid concept; 2) ATC safety alerts and recommendations in all conflict situations; 3) reliable altitude-encoding transponders activated at all times in all aircraft; 4) standard traffic pattern entry, exit, and circuit procedures at all airports; 5) standard communications, and position announcements in the traffic pattern, at all airports; 6) standard procedures for announcing positions and headings in arrival and departure areas, corridors, scenic areas, and other high-density areas; and 7) affordable and reliable collision avoidance technologies in all general aviation aircraft.
Aircraft conspicuity must also be considered when evaluating the see-and-avoid principle. Specific paint schemes and patterns may have an advantage in certain conditions, but none has an overall advantage over another. Footnote 28 Footnote 29 Footnote 30 Anti-collision lights and strobe lights do not have a significant effect in bright daylight, Footnote 31 and landing lights are effective only when the opposing aircraft is in the direct beam. Footnote 32
Transportation Safety Board of Canada aviation investigation report A06O0206 identified that there is a high risk of mid-air collisions in congested airspace when aircraft are not alerted to the presence of other aircraft and rely solely on the see‑and-avoid principle. A technological means of alerting pilots to potential conflicts would enhance the current see-and-avoid approach to averting mid-air collisions. The report also contained a Safety Concern which stated in part:
. . . until technological solutions such as on-board collision-protection systems are mandated, a significant risk of collision between VFR aircraft will continue to exist in congested, high-density airspace areas in Canada. The Board notes that the risk of collision will increase as this traffic continues to grow, and see-and-avoid remains the primary means of defence. In addition, the Board recognizes that technological innovation is creating potential solutions that are both viable and economical.
Airborne collision avoidance systems
Neither aircraft was equipped, nor was required by regulation to be equipped, with any form of aircraft collision avoidance technology. Several forms of this technology are in use today, and their features are summarized in Appendix D– Airborne Collision Avoidance Systems.
One such system, the Traffic Information System (TIS), was analysed to determine whether a timely alert could have been produced had either aircraft been equipped with this technology. Figure 2 and Figure 3 represent images from an NTSB simulation of the TIS messages that potentially could have been sent to the Piper and the Beechcraft had they been equipped with the avionics necessary to receive and display the messages.
The simulated images are based on raw radar returns, and not the smoothed or filtered returns used by the actual FAA TIS. Nonetheless, the simulation is representative in terms of the type and timing of the alerts that potentially could have been provided to both airplanes.
It is important to note that when proximity alerts Footnote 33 are elevated to traffic alerts, Footnote 34 an aural "traffic" alert is also sounded. This would have occurred at 1604:17 for the Piper, showing the Beechcraft 500 feet below, at about the 9-10 o’clock position, and less than 1 mile. A traffic alert would have been provided to the Beechcraft at 1604:13, showing the Piper 500 feet above, at the 2‑3 o’clock position, and less than 1 nm. The collision occurred at about 1604:45, so the aural alerts could have provided about a 30-second warning.
Investigative techniques - azimuth and elevation angles of airplane structures from laser scans
For the field-of-view analysis (TSB Laboratory Report LP119-2012), the azimuth and elevation angles of the window boundaries and wings were determined, for both the Piper and the Beechcraft, based on the interior and exterior dimensions of these airplanes, as measured using the NTSB’s FARO laser scanner Footnote 35 with the assistance of NTSB investigators. The laser scanner produces a point cloud Footnote 36 generated by the reflection of laser light off objects in the laser’s path, as the scanner sweeps through 360° of azimuth and approximately 150° of elevation. The 3-dimensional coordinates of each point in the cloud are known, and the coordinates of points from multiple scans, resulting from placing the scanner in different positions, are merged by the scanner software into a common coordinate system. By placing the scanner in a sufficient number of locations, so that every part of the airplane is scanned, the complete exterior and interior geometry of the airplane can be defined.
In this study, the scanner was placed in 8 locations to scan the exterior of the airplanes, and in both the pilot and co-pilot seats to scan the interior of the airplanes. The scanner software was then used, with the interior scans, to identify the points defining the outline of the cockpit windows. The exterior scans were used for the left and right wings. The coordinates of these points were exported from the scanner software and imported into Microsoft Excel. In Excel, the coordinates were transformed into the airplane’s body axis system and, ultimately, into azimuth and elevations angles from the pilot’s eye position.
Memorandum of understanding between the National Transportation Safety Board and the Transportation Safety Board of Canada
The TSB was designated to conduct an investigation into this accident in order to make findings as to the causes and contributing factors and identify safety deficiencies under a memorandum of understanding (MOU) signed with the NTSB.
The MOU identified that the respective agencies would be bound by the standards included in Annex 13 to the Convention on International Civil Aviation – Aircraft Accident and Incident Investigation concerning accident and serious incident investigations. Additionally, the MOU provided that the investigation was to be conducted in accordance with the Canadian Transportation Accident Investigation and Safety Board Act, as well as TSB standard operating policies and practices.
An NTSB investigator was appointed as the accredited representative for the United States to the TSB investigation, under Chapter 5 of Annex 13 to the Convention on International Civil Aviation. The accredited representative was to be the sole point of contact between the NTSB and the TSB for the purposes of the investigation. Other NTSB personnel and NTSB board members were not to be involved in any aspect of the investigation other than providing information requested by the TSB investigator-in-charge through the accredited representative.
Transportation Safety Board Laboratory reports
The following TSB Laboratory report was completed:
- LP119-2012 – Field-of-View Analysis
Given the events leading up to the mid-air collision, this analysis will focus on why the 2 aircraft, operating under visual flight rules (VFR), were unable to avoid one another on the basis of the see-and-avoid principle and why, although the controller had received a conflict alert, no safety alert was issued prior to the collision.
Separation of VFR aircraft is predicated on the principle that pilots will see and avoid other aircraft. However, the limitations of the see-and-avoid concept do not always permit pilots to do so. The 2 aircraft were on a constant collision course for approximately 37 seconds, during which there would have been no relative angular movement to aid in detection by the pilots’ peripheral vision. The pilots’ activities in both aircraft created a workload that would have reduced the time devoted to scanning for traffic. The Piper pilot was preparing for a simulated instrument approach; the Beechcraft pilot was completing various exercises during a flight check. The relative position of each aircraft was such that the approaching aircraft were not in the forward view of either pilot. Had either pilot looked in the general direction of the approaching aircraft, the relatively large area of view masked by the natural blind spot of the eye could have easily obscured the small target that was the aircraft. Due to the converging courses, there would have been little to no relative movement of either aircraft and as such, the human visual system would have had difficulty detecting the aircraft. From the Piper pilot’s perspective, the Beechcraft was approaching from below, and the ground features would have presented a complex background, which would make detecting the aircraft more difficult. The investigation could not determine to what extent the pilots were actively scanning for other aircraft. The inadequacies of the see-and-avoid concept are further compounded when aircraft are operated in congested, high-density airspace, as was the case in this accident.
Air traffic control (ATC) has technology that controllers can use to alert pilots of potential conflicts with other aircraft. In this accident, when the conflict alert (CA) was triggered, the 2 aircraft were 500 feet apart vertically, which is the accepted minimum spacing between 2 VFR aircraft. At first, there was no indication that either aircraft was climbing or descending. The initial CA, and the first update for the 2 aircraft targets 5 seconds later, showed the aircraft maintaining a vertical spacing of 500 feet. The controller assessed that there was no conflict between the 2 VFR aircraft and therefore did not issue an immediate safety alert.
The controller would have had to monitor the aircraft for 10 to 15 seconds to determine that a risk of collision existed. In this case, a CA was triggered when the aircraft were less than 600 feet apart vertically, and the software algorithm determined that the 2 aircraft were on a converging course if they continued to proceed at their current speed and heading. If a controller determines, through observation, that there is no immediate threat to the safety of the 2 aircraft, no action is required.
The controller also perceived that the separation between the 2 crossing IFR aircraft was not assured, which required detailed monitoring. The controller’s attention was therefore directed to these 2 aircraft, and not to the 2 VFR aircraft, neither of which had been radar identified prior to the collision, and neither of which was being provided ATC services at that time. The controller was busy communicating with several other IFR aircraft, which precluded further monitoring of the 2 VFR aircraft.
Controllers are required to make a judgment whether or not the CA is valid and to make a decision on the appropriate course of action (for example, issuing a safety alert). Alerts are not mandatory for every CA, but depend on a controller’s judgment based on the data displayed for a particular aircraft pair. At the time of the initial CA and of the first update of the 2 aircraft targets 5 seconds later, the radar display showed the aircraft maintaining a vertical spacing of 500 feet.
In this occurrence, the defences available to avert a mid-air collision failed. These defences were the see-and-avoid principle and ATC services in the form of radar surveillance and collision alerting. Current aircraft-based collision avoidance systems vary in cost, complexity, and functionality. However, had 1 or both of these aircraft been equipped with some form of the technology, the risk of collision would have been reduced.
Findings as to causes and contributing factors
- Neither pilot saw the other aircraft in time to avert a mid-air collision, likely due to the inherent limitations of the see-and-avoid principle.
- Following the receipt of a conflict alert, the controller assessed that there was no conflict between the 2 visual flight rules (VFR) aircraft and therefore did not issue an immediate safety alert. Subsequently, the controller was busy communicating with several instrument flight rules (IFR) aircraft, which precluded further monitoring of the 2 VFR aircraft.
Findings as to risk
- In the absence of a means of alerting visual flight rules (VFR) pilots to potential conflicts to enhance the current see-and-avoid technique, the risk for mid-air collisions remains.
- The lack of a shoulder harness in the Piper contributed to the pilot’s injuries during the forced landing.
Safety action taken
The Federal Aviation Administration (FAA) has since modified the air traffic controller training, and on 07 June 2012, issued a memorandum regarding conflict alert training, which stated:
This memo is to advise that in addition to the documented Refresher Training and classroom instruction, the training of new Academy Graduates (AG’s) and Certified Professional Controllers in Training (CPCIT’s) also includes activation of Conflict Alert while in Enhanced Target Generator (ETG) simulation training. During the course of simulation training, CA is activated due to the trainee not recognizing created or built in conflicts of aircraft tracks. Instructors teach the trainees their responsibilities and how to react to these “Conflict Alerts”. ETD45G Scenarios are fabricated with built in conflictions that teach the trainee to recognize confliction points and how to react to the Conflict Alert activation. Students are taught Traffic Alert responsibilities and priority of duty requirements.
This accident has demonstrated yet again that relying solely on the see-and-avoid principle to avoid collisions between aircraft operating under visual flight rules (VFR) in congested airspace is inadequate.
A number of international studies have addressed the overall issue of the effectiveness of the see-and-avoid principle, as well as the risks of collision associated with this principle. All acknowledged the underlying physiological limitations at play and that, when mid-air collisions occur, "failure to see-and-avoid is due almost entirely to the failure to see." Footnote 37 One study stated that "our data suggest that the relatively low (though unacceptable) rate of mid-air collisions in general aviation aircraft not equipped with TCAS [traffic alert and collision avoidance system] is as much a function of the ‘big sky’ as it is of effective visual scanning." Footnote 38 A British Royal Air Force study into mid-air collisions, which were deemed to be random, found that the probability of conflict is proportional to the square of the traffic density, and recommended avoiding altitude restrictions that concentrate traffic. Footnote 39 Measures such as improving aircraft conspicuity, pilot scanning techniques, and pilot traffic awareness can reduce risks, but they do not overcome the underlying physiological limitations that create the residual risk associated with a see-and-avoid method without alerts.
As VFR traffic increases, additional lines of defence should be considered to reduce the risk of a mid-air collision. These lines of defence could include: changes in airspace classification, increased air traffic control (ATC) intervention, as well as ground-based and on-board technology.
Changes in airspace classification can be implemented to increase the provision of dedicated ATC services, including separation and traffic advisories, to VFR aircraft operating in congested airspace. In such cases, ATC sectorization and controller workload must also be carefully reviewed to ensure that controllers have the appropriate resources to effectively manage air traffic under their jurisdiction.
Controllers can use ATC-based technology to alert pilots of potential conflicts with other aircraft. However, the effectiveness of such systems also depends on controller judgment and workload. The National Transportation Safety Board (NTSB) has previously expressed concern and made recommendations to improve the effectiveness of such conflict warning systems.
A meaningful improvement to the ability to see and avoid other VFR aircraft may require on-board technology capable of directly alerting pilots of the proximity of conflicting traffic. As outlined in this report, a number of viable and economical on-board alerting systems exist or are under development. These technologies also offer the potential to reduce the risk of mid-air collisions.
Appendix A – RNAV (GPS) RWY 33 Warrenton-Fauquier
Appendix B – Airspace and airports
Appendix C – Approximate fields of view
Appendix D – Airborne collision avoidance systems
Traffic alert and collision avoidance system (TCAS) I
- Intended for general aviation and regional airlines.
- Issues traffic advisories (TA) that assist pilots to visually acquire target aircraft.
- Active system consisting of a transmitter, receiver, directional antennas, computer and cockpit displays.
- Transmits a signal (interrogation) that will be received by a transponder equipped (Mode C) aircraft. This aircraft will respond to the interrogation and reply. The system will interpret the reply and calculate the distance and direction of the responding aircraft.
- Able to determine the responding aircraft’s relative altitude and whether it is climbing or descending.
- Issues a traffic advisory (visually and aurally) if a potential conflict is determined.
- The FAA mandated that TCAS I be installed on aircraft with 10 to 30 seats.
- Provides a basic level of surveillance to flight crews.
- Requires that conflicting aircraft be equipped with a transponder.
- Only transmits on 1030/1090 MHz frequencies - As the density of TCAS equipped aircraft increases, there is a corresponding increase in interrogations of transponders.
- Provides advisory alerts only; the crew is still required to assess the situation and determine a resolution.
Cost in 2012: Approximately $22 000 USD (Other units range from $28 000 to $74 000)
Traffic alert and collision avoidance system (TCAS) II
- Uses Mode S transponders.
- Issues traffic advisories (TA) that assist pilots in visually acquiring target aircraft.
- Analyzes the projected flight path of approaching aircraft and will issue resolution advisories (RA) to the crew in order to resolve potential conflicts. The RA will advise the pilot to climb or descend in order to resolve the conflict. Some models may also advise the pilot not to manoeuvre.
- Required internationally in aircraft with more than 30 seats or weighing more than 15 000 kg.
- When resolving conflicts with TCAS II-equipped aircraft, the TCAS II units will co-ordinate RA in order to avoid mirroring their manoeuvres.
- Conflicting aircraft are required to be equipped with transponders.
- Restricted to provide commands for vertical manoeuvring, and not for turns.
- If not communicated to ATC in a timely manner, RA manoeuvring may cause the controller to issue avoidance instructions that may conflict with RA.
Cost in 2012: $150 000 to $230 000 USD
Traffic advisory system
- Interrogates other Mode A, C and S transponder systems and listens for a target reply, and then calculates as much of distance, relative bearing, altitude and vertical trend as possible.
- Issues a traffic alert (TA) if the system calculates a collision course.
- Works on the ground and will work with any aircraft with an installed and functioning transponder.
- Lower cost evolution of TCAS.
- Installations are significant; include heavy and large remote processors and complex antenna work.
Cost in 2012: $10 000 to $20 000 USD
Portable collision alert system (PCAS)
- Passive system that listens for a 1090 MHz transponder transmission.
- Can be temporarily mounted on the dash or permanently panel mounted.
- Certain units can provide directional and altitude information from transponder-equipped aircraft (altitude information can only be provided from aircraft equipped with transponders with altitude-encoding capability).
- The maximum range is approximately 6 nm.
- The parent unit will interpret the target’s coded data and provide a relative position and altitude.
- Relatively inexpensive, with a minimal investment in installation.
- Can be readily utilized.
- When coupled with GPS mapping equipment, the relative position of target aircraft can be better appreciated.
- Requires target aircraft to be transponder-equipped, and that the target aircraft be interrogated by an ATC ground station (or from airborne TCAS-equipped aircraft) resulting in the transponder replying to that interrogation.
- Depending on where the unit is located, there is a potential for shadowing by the parent aircraft’s structure.
- Units have also been reported to alert bogus targets. It has been suggested that this may be due to the unit reading the parent aircraft’s transponder signal.
Cost in 2012: $550 to $1500 USD
Traffic information system (TIS)
- Ground-based service that utilizes the Mode S datalink to communicate collision avoidance information to the aircraft.
- The system can show location, direction, altitude and climb/descent trends of other transponder-equipped aircraft within 5 nm and 1200 feet of your aircraft.
- Threat traffic information can be displayed on the Mode S transponder or a variety of cockpit units including many popular multi-function displays.
- No distinct advantage.
- Requires aircraft to be Mode S transponder equipped.
- May not be available in all areas.
- Ground-based; aircraft can fly out of range.
- Needs a multi- function cockpit display.
Cost in 2012: $5000 USD (not installed)
Automatic dependent surveillance – broadcast (ADS-B)
- System being implemented by the FAA; ADS-B (Out) implemented by 2020.
- Each aircraft is responsible for its own navigation and separation.
- ADS-B aircraft transmit their identification, speed and vertical and horizontal positions to a global navigation satellite system (GNSS). This information would be rebroadcast by the GNSS to other ADS-B-equipped aircraft and ground stations (ATC). Information will be broadcast on 1090 MHz or 978MHz.
- The system is not radar dependent, therefore distance from a radar site and terrain will not interfere with the transmission/reception of data. The system will provide pilots and air traffic controllers with real-time precise aircraft position information.
- Not many aircraft are equipped with this equipment, so there will be a reliance on traditional radar until such time as the program has been implemented.
Cost in 2012: $8000 USD (not installed)
- Obtains its position from an internal GPS and a barometric sensor and then broadcasts this with forecast data about the future 3D flight track. Its receiver listens for other FLARM devices within typically 3-5 kilometres and processes the information received. Motion-prediction algorithms predict potential conflicts for up to 50 other signals and warn the pilot using sound and visual means.
- Can store information about static aerial obstacles, such as cables, in a database.
- The system’s serial data protocol is public, while the prediction engine of the FLARM radio-protocol is proprietary and licensed to manufacturers. The prediction engine itself is patented by Onera (France).
- Small size.
- Simple installation.
- Low power consumption.
- Provides visual and acoustic warnings for aircraft and fixed obstacle.
- Optimised for the specific needs of small aircraft such as gliders, not for long-range communication or ATC interaction.
- Requires other aircraft to be equipped with FLARM.
Cost in 2012: $900 USD (not installed)
This report concludes the Transportation Safety Board's investigation into this occurrence. Consequently, the Board authorized the release of this report on 17 April 2013. It was officially released on 21 June 2013.
- Footnote 1
All times are Eastern Daylight Time (Coordinated Universal Time minus 4 hours).
- Footnote 2
Under section 61.56 of the Federal Aviation Regulations, the Beechcraft pilot was required to complete a flight review with an authorized instructor prior to 01 June 2012 in order to continue to act as a pilot-in-command of an aircraft.
- Footnote 3
The 1200 transponder code is a generic code used for aircraft under visual flight rules that have not been assigned a discrete code by air traffic services.
- Footnote 4
Potomac TRACON Standard Operating Procedure 3-1-4, “Transfer of Position Responsibility and Use of Checklist”.
- Footnote 5
To squawk ident refers to the request for a pilot to activate the aircraft transponder identification feature so the aircraft target will illuminate on the radar screen.
- Footnote 6
A visual conflict alert consists in a red CA flashing at the bottom of the radar display and a flashing aircraft target.
- Footnote 7
Before controllers can provide radar service, they must establish and maintain radar identification of the involved aircraft.
- Footnote 8
A V-tail (sometimes called a butterfly tail) is an unconventional arrangement of the tail control surfaces. This arrangement replaces the traditional fin and horizontal surfaces with 2 surfaces set in a V-shaped configuration when viewed from the front or rear of the aircraft. The rear of each surface is hinged, and these movable sections, referred to as ruddervators, combine the tasks of the elevators and rudder.
- Footnote 9
“Many factors, such as limitations of the radar, volume of traffic, controller workload and communications frequency congestion, could prevent the controller from providing this service. Controllers possess complete discretion for determining whether they are able to provide or continue to provide this service in a specific case. The controller's reason against providing or continuing to provide the service in a particular case is not subject to question nor need it be communicated to the pilot. In other words, the provision of this service is entirely dependent upon whether controllers believe they are in a position to provide it.”Federal Aviation Administration, Aeronautical Information Manual (February 9, 2012), 4.1.15.b.1.
- Footnote 10
Ibid., 3-2-6. f.
- Footnote 11
Ibid., 4-1-15, “Radar Traffic Information Service”.
- Footnote 12
Ibid., 4-1-16, “Safety Alert”.
- Footnote 13
Federal Aviation Administration, Common ARTS Computer Program Functional Specification (CPFS) Conflict Alert, NAS-MD-632, A6.05/A2.09.
- Footnote 14
Short-range radar scan intervals are approximately 4.5 seconds, and long-range radar scan intervals are 12 seconds.
- Footnote 15
The look-ahead time is 40 seconds.
- Footnote 16
Because the Piper’s transponder was still functioning after the collision, the CA continued.
- Footnote 17
The alert was declared by the proximity conflict (PROCON) algorithm (1 of the 4 CA algorithms), which is triggered when aircraft are less than 0.75 nm apart laterally, and 375 feet apart vertically, or less than 600 feet apart vertically, and converging laterally at a specific rate (based on NAS-MD-632, paragraph 3.3).
- Footnote 18
Advisories issued to alert pilots of other known or observed air traffic which may be in such proximity to the position or intended route of flight of their aircraft to warrant their attention.
- Footnote 19
Federal Aviation Administration, Order JO 7110.65U, Air Traffic Control (9 February 2012), Section 2−1−6, “Safety Alert”.
- Footnote 20
- Footnote 21
bid., SIection 2−1−2, “Duty Priority”.
- Footnote 22
Ibid., Section 2-1-21, “Traffic Advisories”.
- Footnote 23
C.D. Wickens, S. Rice, D. Keller, S. Hutchins, J. Hughes, and K. Clayton, “False Alerts in Air Traffic Control Conflict Alerting System: Is there a “Cry Wolf” Effect?” Human Factors,Vol. 51, No. 4, pp. 446-462 (August 2009).
- Footnote 24
An “open - acceptable” assessment indicates that the planned action would comply with the safety recommendation when completed.
- Footnote 25
Federal Aviation Administration, Code of Federal Regulations, 91.113. (See also: Federal Aviation Administration, Aeronautical Information Manual [February 9, 2012], 5-5-8.)
- Footnote 26
Australian Transport Safety Bureau, Limitations of the See-and-Avoid Principle (April 1991, ISBN 0 642 16089 9).
- Footnote 27
C. Craig Morris, “Midair Collisions: Limitations of the See-and-Avoid Concept in Civil Aviation,” Aviation, Space, and Environmental Medicine, 76 (4), pp 357-65 (April 2005).
- Footnote 28
J.W. Chappelow and A.J. Belyavin, A Trial to Assess Aids to Conspicuity, Royal Air Force Institute of Aviation Medicine Report 723 (July 1992).
- Footnote 29
J.W. Chappelow, A.J. Belyavin, and P.R. Smith, Aircraft Conspicuity and Paint Schemes: A Further Trial, Royal Air Force Institute of Aviation Medicine Report 747 (May 1993).
- Footnote 30
J.W. Chappelow, L.H. Tate, and M. Woodward, Training Helicopter Conspicuity, QinetiQ Report CHS/CAP/CR020032 (January 2002).
- Footnote 31
W. Graham, See and Avoid/Cockpit Visibility, FAA Report DOT/FAA/CT-TN89/18 (October 1989).
- Footnote 32
J.W. Chappelow and A.J. Belyavin, Random Mid-Air Collisions in the Low Flying System, Royal Air Force Institute of Aviation Medicine Report 702 (April 1991).
- Footnote 33
Proximity alerts are displayed as open white diamond symbols.
- Footnote 34
Traffic alerts are displayed as solid yellow circles.
- Footnote 35
Specifically, the FARO “Focus 3D” scanner (see www.faro.com/focus/us)
- Footnote 36
A series of points in 3D space, defined in X, Y, Z format, which collectively describe the geometry of a physical object.
- Footnote 37
W. Graham, See and Avoid/Cockpit Visibility, FAA Report DOT/FAA/CT-TN89/18 (October 1989).
- Footnote 38
K.W. Colvin, R.M. Dodhia, and R.K. Dismukes, "Is Pilots' Visual Scanning Adequate to Avoid Mid-air Collisions?" Proceedings of the 13th International Symposium on Aviation Psychology, Oklahoma City, pp. 104-109 (2005).
- Footnote 39
J.W. Chappelow and A.J. Belyavin, Random Mid-Air Collisions in the Low Flying System, Royal Air Force Institute of Aviation Medicine Report 702 (April 1991).
- Date modified: