Near midair collision between military-small transport and GA-small aircraft on approach to intersecting runways. Operational error.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	105447
Time
Date	198902
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : bhm airport : bam
State Reference	AL
Altitude	agl bound lower : 0 agl bound upper : 100
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : bhm
Operator	other
Make Model Name	Small Transport, Low Wing, 2 Recip Eng
Flight Phase	descent : approach landing other
Route In Use	approach : straight in approach : visual enroute : on vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	descent : approach landing other
Person 1
Affiliation	government : military
Function	flight crew : captain oversight : pic
Qualification	pilot : military pilot : atp pilot : cfi
Experience	flight time last 90 days : 100 flight time total : 9800 flight time type : 700
ASRS Report	105447
Person 2
Affiliation	government : military
Function	flight crew : first officer
Qualification	pilot : military
Events
Anomaly	conflict : nmac non adherence : far non adherence : required legal separation
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance flight crew : took evasive action
Consequence	Other
Miss Distance	horizontal : 50 vertical : 100
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Apparently bhm approach and tower were both understaffed, as we were hearing the same voice on several assigned frequencys. Traffic was not too heavy, but we were vectored extensively and put behind a single engine 60 KTS slower. We slowed down and finally got clearance for a 'visibility to 23.' after crossing the LOM (we were tracking the localizer DME 23) the approach controller handed us over to tower. The tower cleared us to land on runway 23. At about 100' AGL we saw another airplane (an small aircraft) landing long on runway 18. We leveled off and by then the small aircraft had landed on runway 18, but tower had not mentioned this traffic at all! To make matters worse, tower called as we were about to T/D (already past runway 18) and said, 'military dib, go around.' he repeated this, but we were military xxihb, so I asked if he meant us. He said, 'yeah, but it's ok now.' at an airport such as bhm, which has heavy military aircraft traffic, it behooves ATC personnel to: call out traffic and use the proper ATC call sign.

Original NASA ASRS Text

Title: NMAC BETWEEN MIL-SMT AND GA-SMA ON APCH TO INTERSECTING RWYS. OPERATIONAL ERROR.

Narrative: APPARENTLY BHM APCH AND TWR WERE BOTH UNDERSTAFFED, AS WE WERE HEARING THE SAME VOICE ON SEVERAL ASSIGNED FREQS. TFC WAS NOT TOO HEAVY, BUT WE WERE VECTORED EXTENSIVELY AND PUT BEHIND A SINGLE ENG 60 KTS SLOWER. WE SLOWED DOWN AND FINALLY GOT CLRNC FOR A 'VIS TO 23.' AFTER XING THE LOM (WE WERE TRACKING THE LOC DME 23) THE APCH CTLR HANDED US OVER TO TWR. THE TWR CLRED US TO LAND ON RWY 23. AT ABOUT 100' AGL WE SAW ANOTHER AIRPLANE (AN SMA) LNDG LONG ON RWY 18. WE LEVELED OFF AND BY THEN THE SMA HAD LANDED ON RWY 18, BUT TWR HAD NOT MENTIONED THIS TFC AT ALL! TO MAKE MATTERS WORSE, TWR CALLED AS WE WERE ABOUT TO T/D (ALREADY PAST RWY 18) AND SAID, 'MIL DIB, GO AROUND.' HE REPEATED THIS, BUT WE WERE MIL XXIHB, SO I ASKED IF HE MEANT US. HE SAID, 'YEAH, BUT IT'S OK NOW.' AT AN ARPT SUCH AS BHM, WHICH HAS HVY MIL ACFT TFC, IT BEHOOVES ATC PERSONNEL TO: CALL OUT TFC AND USE THE PROPER ATC CALL SIGN.

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.