Similar sounding intersection navigation fix names add to confusion in readback hearback problem for ARTCC controller and large transport flight crew. The 2 navigational fixes in question, bdl VOR and brazi intersection on the bos 7 SID are in close proximity.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	167495
Time
Date	199101
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : bos
State Reference	MA
Altitude	msl bound lower : 19000 msl bound upper : 19000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zbw tower : mci
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 3 Turbojet Eng
Flight Phase	climbout : intermediate altitude
Route In Use	departure other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : cfi pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 9 flight time total : 15000 flight time type : 8000
ASRS Report	167495
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Events
Anomaly	non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	flight crew : returned to intended course or assigned course other
Consequence	Other
Supplementary
Primary Problem	Ambiguous
Air Traffic Incident	other

Narrative:

During climb out from bos to the southwest over brazi intersection we were cleared to proceed to a place that sounded like brazi. Brazi was on our flight plan and on the logan 7 departure, so it seemed like a natural place to expect to proceed. After a few mins ZBW inquired as to our heading to bdl. I stated that we were cleared to brazi. Controller wanted to know if we were RNAV equipped. We were not. He then instructed us to proceed to the bdl VOR, frequency 109.0. We proceeded as instructed and had an uneventful trip. A couple of items come to mind: first, this was a classic example of the readback/hearback problem. He said 'bradley,' I heard 'brazi,' read back 'brazi,' and the controller did not catch that what I said and what he wanted wasn't the same. Secondly, it seems poor charting practice to have such similar sounding names on navigation fixes that are colocated or in close proximity.

Original NASA ASRS Text

Title: SIMILAR SOUNDING INTXN NAVIGATION FIX NAMES ADD TO CONFUSION IN READBACK HEARBACK PROBLEM FOR ARTCC CTLR AND LGT FLT CREW. THE 2 NAVIGATIONAL FIXES IN QUESTION, BDL VOR AND BRAZI INTXN ON THE BOS 7 SID ARE IN CLOSE PROX.

Narrative: DURING CLBOUT FROM BOS TO THE SW OVER BRAZI INTXN WE WERE CLRED TO PROCEED TO A PLACE THAT SOUNDED LIKE BRAZI. BRAZI WAS ON OUR FLT PLAN AND ON THE LOGAN 7 DEP, SO IT SEEMED LIKE A NATURAL PLACE TO EXPECT TO PROCEED. AFTER A FEW MINS ZBW INQUIRED AS TO OUR HDG TO BDL. I STATED THAT WE WERE CLRED TO BRAZI. CTLR WANTED TO KNOW IF WE WERE RNAV EQUIPPED. WE WERE NOT. HE THEN INSTRUCTED US TO PROCEED TO THE BDL VOR, FREQ 109.0. WE PROCEEDED AS INSTRUCTED AND HAD AN UNEVENTFUL TRIP. A COUPLE OF ITEMS COME TO MIND: FIRST, THIS WAS A CLASSIC EXAMPLE OF THE READBACK/HEARBACK PROB. HE SAID 'BRADLEY,' I HEARD 'BRAZI,' READ BACK 'BRAZI,' AND THE CTLR DID NOT CATCH THAT WHAT I SAID AND WHAT HE WANTED WASN'T THE SAME. SECONDLY, IT SEEMS POOR CHARTING PRACTICE TO HAVE SUCH SIMILAR SOUNDING NAMES ON NAV FIXES THAT ARE COLOCATED OR IN CLOSE PROX.

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.