Narrative:

I observed no evasive action on the part of the falcon's crew, although our head-on convergence and the estimated closure rate of 6 mi per min suggest I might have had as much difficulty discerning the other aircraft's flight attitude as I did detecting its presence in the first place. I suspect TCASII was not installed or was not operable onboard the falcon, as our separation was well inside the limits I know to be acceptable to aircraft equipped with that technology. As I was not in contact with any controling ATC facility at the time of the incident (nor was I required to be), I made no report until my filing with NASA of an aviation safety reporting system (ASRS) form. Here's my analysis of this near midair collision incident. Chain of events: the problem arose due to congested, high-density airspace in which a mix of aircraft types operates into and out of numerous facilities. The problem was discovered using see-and-avoid techniques. Contributing factors included the apparent absence of operable TCASII equipment and the lack of ATC radar separation. Corrective actions involved prompt identify of the traffic conflict and basic airmanship. Human performance considerations: perceptions, judgements, and decisions were fundamentally sound. Actions were appropriate. Factors affecting the quality of human performance, included primarily my desire to minimize the cost and inconvenience of systematic ATC delays by operating VFR as conditions allowed. My continuous visual scan for traffic, and that of my passenger, were what saved our bacon. As a result of this incident, I now conduct all but local flts in busy terminal areas under IFR, and I have added TCASII to the list of required equipment onboard any airplane I own in the future. I have also committed to increase the time I spend visually scanning outside the aircraft, and to enlist the assistance of any willing and able passenger in scanning for potential traffic conflicts.

Google
 

Original NASA ASRS Text

Title: BE36 NMAC WITH FALCON 50 NEAR TEB.

Narrative: I OBSERVED NO EVASIVE ACTION ON THE PART OF THE FALCON'S CREW, ALTHOUGH OUR HEAD-ON CONVERGENCE AND THE ESTIMATED CLOSURE RATE OF 6 MI PER MIN SUGGEST I MIGHT HAVE HAD AS MUCH DIFFICULTY DISCERNING THE OTHER ACFT'S FLT ATTITUDE AS I DID DETECTING ITS PRESENCE IN THE FIRST PLACE. I SUSPECT TCASII WAS NOT INSTALLED OR WAS NOT OPERABLE ONBOARD THE FALCON, AS OUR SEPARATION WAS WELL INSIDE THE LIMITS I KNOW TO BE ACCEPTABLE TO ACFT EQUIPPED WITH THAT TECHNOLOGY. AS I WAS NOT IN CONTACT WITH ANY CTLING ATC FACILITY AT THE TIME OF THE INCIDENT (NOR WAS I REQUIRED TO BE), I MADE NO RPT UNTIL MY FILING WITH NASA OF AN AVIATION SAFETY RPTING SYS (ASRS) FORM. HERE'S MY ANALYSIS OF THIS NMAC INCIDENT. CHAIN OF EVENTS: THE PROB AROSE DUE TO CONGESTED, HIGH-DENSITY AIRSPACE IN WHICH A MIX OF ACFT TYPES OPERATES INTO AND OUT OF NUMEROUS FACILITIES. THE PROB WAS DISCOVERED USING SEE-AND-AVOID TECHNIQUES. CONTRIBUTING FACTORS INCLUDED THE APPARENT ABSENCE OF OPERABLE TCASII EQUIP AND THE LACK OF ATC RADAR SEPARATION. CORRECTIVE ACTIONS INVOLVED PROMPT IDENT OF THE TFC CONFLICT AND BASIC AIRMANSHIP. HUMAN PERFORMANCE CONSIDERATIONS: PERCEPTIONS, JUDGEMENTS, AND DECISIONS WERE FUNDAMENTALLY SOUND. ACTIONS WERE APPROPRIATE. FACTORS AFFECTING THE QUALITY OF HUMAN PERFORMANCE, INCLUDED PRIMARILY MY DESIRE TO MINIMIZE THE COST AND INCONVENIENCE OF SYSTEMATIC ATC DELAYS BY OPERATING VFR AS CONDITIONS ALLOWED. MY CONTINUOUS VISUAL SCAN FOR TFC, AND THAT OF MY PAX, WERE WHAT SAVED OUR BACON. AS A RESULT OF THIS INCIDENT, I NOW CONDUCT ALL BUT LCL FLTS IN BUSY TERMINAL AREAS UNDER IFR, AND I HAVE ADDED TCASII TO THE LIST OF REQUIRED EQUIP ONBOARD ANY AIRPLANE I OWN IN THE FUTURE. I HAVE ALSO COMMITTED TO INCREASE THE TIME I SPEND VISUALLY SCANNING OUTSIDE THE ACFT, AND TO ENLIST THE ASSISTANCE OF ANY WILLING AND ABLE PAX IN SCANNING FOR POTENTIAL TFC CONFLICTS.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.