Near midair collision between a C182 and a falcon jet 11 NM northeast of bdr, ct.

Attributes
ACN	543908
Time
Date	200204
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	navaid : bdr.vor
State Reference	CT
Altitude	msl single value : 2600
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tower : bdr.tower
Operator	general aviation : personal
Make Model Name	Skylane 182/RG Turbo Skylane/RG
Operating Under FAR Part	Part 91
Navigation In Use	other vortac
Flight Phase	cruise : level
Flight Plan	None
Aircraft 2
Controlling Facilities	tracon : n90.tracon
Operator	general aviation : corporate
Make Model Name	Dassault-Breguet Undifferentiated or Other Model
Operating Under FAR Part	Part 135
Flight Phase	descent : approach
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : multi engine pilot : instrument pilot : commercial pilot : cfi
Experience	flight time last 90 days : 20 flight time total : 4000 flight time type : 800
ASRS Report	543908
Person 2
Affiliation	other
Function	observation : passenger
Qualification	pilot : cfi
Events
Anomaly	non adherence : far non adherence : required legal separation other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	controller : issued new clearance none taken : insufficient time
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 0 vertical : 400
Supplementary
Problem Areas	ATC Human Performance Airspace Structure Flight Crew Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error Inter Facility Coordination Failure

Narrative:

Inbound to bdr on 056 degree radial at 2600 ft, was maintaining 2600 ft to be above hvn class D airspace. Bdr local controller said new york approach requested we descend below 2500 ft for crossing falcon. I was simulating IFR and asked the cfii to insure we were clear of hvn class D airspace before descent. We were clear, so he initiated descent to 1800 ft, which is the initial altitude for published approach. The cfii had the traffic in sight and spoke up about the closeness. I abandoned the simulated IFR to watch traffic. The falcon passed directly under us from right to left. Falcon appeared to be headed for hvn. I asked the bdr local controller about the requested descent when the falcon went under our aircraft. He indicated it was a communications breakdown between him and new york approach. After landing, he explained the communications mix-up with new york approach in more detail. If the bdr tower had the long overdue tower radar, this mix-up probably would never have happened.

Original NASA ASRS Text

Title: NMAC BTWN A C182 AND A FALCON JET 11 NM NE OF BDR, CT.

Narrative: INBOUND TO BDR ON 056 DEG RADIAL AT 2600 FT, WAS MAINTAINING 2600 FT TO BE ABOVE HVN CLASS D AIRSPACE. BDR LCL CTLR SAID NEW YORK APCH REQUESTED WE DSND BELOW 2500 FT FOR XING FALCON. I WAS SIMULATING IFR AND ASKED THE CFII TO INSURE WE WERE CLR OF HVN CLASS D AIRSPACE BEFORE DSCNT. WE WERE CLR, SO HE INITIATED DSCNT TO 1800 FT, WHICH IS THE INITIAL ALT FOR PUBLISHED APCH. THE CFII HAD THE TFC IN SIGHT AND SPOKE UP ABOUT THE CLOSENESS. I ABANDONED THE SIMULATED IFR TO WATCH TFC. THE FALCON PASSED DIRECTLY UNDER US FROM R TO L. FALCON APPEARED TO BE HEADED FOR HVN. I ASKED THE BDR LCL CTLR ABOUT THE REQUESTED DSCNT WHEN THE FALCON WENT UNDER OUR ACFT. HE INDICATED IT WAS A COMS BREAKDOWN BTWN HIM AND NEW YORK APCH. AFTER LNDG, HE EXPLAINED THE COMS MIX-UP WITH NEW YORK APCH IN MORE DETAIL. IF THE BDR TWR HAD THE LONG OVERDUE TWR RADAR, THIS MIX-UP PROBABLY WOULD NEVER HAVE HAPPENED.

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.