Near midair collision between air carrier-widebody transport and mlt.

Attributes
ACN	98159
Time
Date	198810
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : mia
State Reference	FL
Altitude	msl bound lower : 16500 msl bound upper : 16800
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Widebody, Low Wing, 2 Turbojet Eng
Navigation In Use	Other Other
Flight Phase	descent other
Route In Use	arrival other enroute airway : v157
Flight Plan	IFR
Aircraft 2
Operator	other
Make Model Name	Military Transport
Navigation In Use	Other
Flight Phase	descent other
Route In Use	approach : visual arrival other
Flight Plan	VFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
ASRS Report	98159
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	conflict : nmac
Independent Detector	other flight crewa
Resolutory Action	none taken : insufficient time
Consequence	faa : reviewed incident with flight crew faa : investigated
Miss Distance	horizontal : 0 vertical : 300
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I was working the scheduled air carrier widebody transport flight inbound to mia on V157. Air carrier widebody transport was cleared to descend to 16000'. The other aircraft, mlt Y, was VFR and under normal circumstances would be talking to either customs or ATC for advisories. The mlt Y was rtb to opf descending VFR from 17500' when he spotted widebody transport 300' right below him. When mlt Y landed he called up and filed a near midair. When asked why he did not ask for VFR flight following, the pilot said he was on a 'sensitive' mission. I, as the controller, never saw the VFR squawk on my rdp, but I was told that it was displayed. However, that does not relieve the mlt Y pilot to 'see and be seen.' also, mlt Y would have to talk to ATC before he landed whether it was tower, approach control, or center--I don't care how 'sensitive' a mission he was on. One last remark on this incident: I worked another mlt Z 1 hour before mlt Y that was going opp direction VFR with flight following. I suspect that this mlt Z and mlt Y were one in the same, but I can't prove it.

Original NASA ASRS Text

Title: NMAC BETWEEN ACR-WDB AND MLT.

Narrative: I WAS WORKING THE SCHEDULED ACR WDB FLT INBND TO MIA ON V157. ACR WDB WAS CLRED TO DSND TO 16000'. THE OTHER ACFT, MLT Y, WAS VFR AND UNDER NORMAL CIRCUMSTANCES WOULD BE TALKING TO EITHER CUSTOMS OR ATC FOR ADVISORIES. THE MLT Y WAS RTB TO OPF DSNDING VFR FROM 17500' WHEN HE SPOTTED WDB 300' RIGHT BELOW HIM. WHEN MLT Y LANDED HE CALLED UP AND FILED A NEAR MIDAIR. WHEN ASKED WHY HE DID NOT ASK FOR VFR FLT FOLLOWING, THE PLT SAID HE WAS ON A 'SENSITIVE' MISSION. I, AS THE CTLR, NEVER SAW THE VFR SQUAWK ON MY RDP, BUT I WAS TOLD THAT IT WAS DISPLAYED. HOWEVER, THAT DOES NOT RELIEVE THE MLT Y PLT TO 'SEE AND BE SEEN.' ALSO, MLT Y WOULD HAVE TO TALK TO ATC BEFORE HE LANDED WHETHER IT WAS TWR, APCH CTL, OR CENTER--I DON'T CARE HOW 'SENSITIVE' A MISSION HE WAS ON. ONE LAST REMARK ON THIS INCIDENT: I WORKED ANOTHER MLT Z 1 HR BEFORE MLT Y THAT WAS GOING OPP DIRECTION VFR WITH FLT FOLLOWING. I SUSPECT THAT THIS MLT Z AND MLT Y WERE ONE IN THE SAME, BUT I CAN'T PROVE IT.

Data retrieved from NASA's ASRS site as of August 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.