Air carrier X conflict with F16 on final approach, executed a go around. See and avoid concept.

Attributes
ACN	297129
Time
Date	199502
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : fwa
State Reference	IN
Altitude	agl bound lower : 1000 agl bound upper : 1000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : fwa
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent : approach landing : go around
Flight Plan	IFR
Aircraft 2
Operator	other
Make Model Name	Fighting Falcon F16
Operating Under FAR Part	Part 91
Flight Phase	descent : approach landing other other
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 100 flight time total : 7000 flight time type : 1700
ASRS Report	297129
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Experience	flight time last 90 days : 150 flight time total : 1400 flight time type : 400
ASRS Report	297253
Events
Anomaly	conflict : airborne less severe non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	other
Consequence	Other
Miss Distance	horizontal : 5000 vertical : 0
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

During visual approach to fort wayne runway 23, an F-16 performed a 360 degree overhead break in front of us. Our closest conflict came when the F-16 pulled off downwind and cut in front of us. We were on a 2 mi final and he was coming off downwind. ATC never advised us where he was or where he was coming from. The F-16 was using UHF frequency and could not be heard. We performed an immediate go around when we felt the aircraft were in conflict. Supplemental information from acn 297253: he (the F-16) was going to be maneuvering in front of us. The distance was unrealistically close (for spacing) so we quickly executed a go around. The obvious cause for the problem was the controller's poor judgement of the distance between us and the f- 16. Additionally the F-16's pilot should not have accepted the clearance. Although there never was any actual danger, the biggest problem stems from the fact that we couldn't hear the conversations between the controller and the F-16 (as they were on a different frequency or band (UHF) so even though we were in VMC we had no way of knowing if the f- 16 was landing - low approach or had lost an engine and was trying to land.

Original NASA ASRS Text

Title: ACR X CONFLICT WITH F16 ON FINAL APCH, EXECUTED A GAR. SEE AND AVOID CONCEPT.

Narrative: DURING VISUAL APCH TO FORT WAYNE RWY 23, AN F-16 PERFORMED A 360 DEG OVERHEAD BREAK IN FRONT OF US. OUR CLOSEST CONFLICT CAME WHEN THE F-16 PULLED OFF DOWNWIND AND CUT IN FRONT OF US. WE WERE ON A 2 MI FINAL AND HE WAS COMING OFF DOWNWIND. ATC NEVER ADVISED US WHERE HE WAS OR WHERE HE WAS COMING FROM. THE F-16 WAS USING UHF FREQ AND COULD NOT BE HEARD. WE PERFORMED AN IMMEDIATE GAR WHEN WE FELT THE ACFT WERE IN CONFLICT. SUPPLEMENTAL INFO FROM ACN 297253: HE (THE F-16) WAS GOING TO BE MANEUVERING IN FRONT OF US. THE DISTANCE WAS UNREALISTICALLY CLOSE (FOR SPACING) SO WE QUICKLY EXECUTED A GAR. THE OBVIOUS CAUSE FOR THE PROB WAS THE CTLR'S POOR JUDGEMENT OF THE DISTANCE BTWN US AND THE F- 16. ADDITIONALLY THE F-16'S PLT SHOULD NOT HAVE ACCEPTED THE CLRNC. ALTHOUGH THERE NEVER WAS ANY ACTUAL DANGER, THE BIGGEST PROB STEMS FROM THE FACT THAT WE COULDN'T HEAR THE CONVERSATIONS BTWN THE CTLR AND THE F-16 (AS THEY WERE ON A DIFFERENT FREQ OR BAND (UHF) SO EVEN THOUGH WE WERE IN VMC WE HAD NO WAY OF KNOWING IF THE F- 16 WAS LNDG - LOW APCH OR HAD LOST AN ENG AND WAS TRYING TO LAND.

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.