Cpr HS125 crosses the active runway when cleared to the 'xx FBO.' controller advises crew that they had missed their turn for 'xx FBO.' there were 2 FBO's of similar sounding names. Confusion created by improper name being used by the FBO.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	384298
Time
Date	199710
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : cak
State Reference	OH
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : corporate
Make Model Name	British Aerospace Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Flight Phase	ground other : taxi landing other
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : cfi
Experience	flight time last 90 days : 100 flight time total : 6000 flight time type : 1700
ASRS Report	384298
Person 2
Affiliation	Other
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	incursion : runway non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation other
Situations
Airport	other physical facility procedure or policy : unspecified

Narrative:

After landing at cak, we were asked our destination. First officer reported 'xx FBO' which is the FBO. We were cleared to taxi to FBO. The taxi route to FBO crossed 4 runways. (We landed on runway 23, our FBO is located on the northwest side of the airport.) we visually cleared the area prior to crossing the runways along our taxi route. After crossing back over our landing runway, runway 23, ground control advised us that we had 'missed our turn for FBO.' after questioning the controller, we were advised that there are 2 'xx FBO's' on this field. One is 'xx FBO' and the other is 'xxy FBO.' to make the situation more difficult, 'xx FBO' is located on the northeast side of the airport as opposed to the northwest location of 'xxy FBO.' on our initial call-up to ground control, no mention was made of 2 FBO's. Assumptions were made that the flight crew and ATC were speaking of the same destination. This type of incident could be avoided in the future by: 1) changing the name of one of the FBO's operations to avoid confusion. 2) verifying that the flight crew and ATC are certain as to the aircraft's destination.

Original NASA ASRS Text

Title: CPR HS125 CROSSES THE ACTIVE RWY WHEN CLRED TO THE 'XX FBO.' CTLR ADVISES CREW THAT THEY HAD MISSED THEIR TURN FOR 'XX FBO.' THERE WERE 2 FBO'S OF SIMILAR SOUNDING NAMES. CONFUSION CREATED BY IMPROPER NAME BEING USED BY THE FBO.

Narrative: AFTER LNDG AT CAK, WE WERE ASKED OUR DEST. FO RPTED 'XX FBO' WHICH IS THE FBO. WE WERE CLRED TO TAXI TO FBO. THE TAXI RTE TO FBO CROSSED 4 RWYS. (WE LANDED ON RWY 23, OUR FBO IS LOCATED ON THE NW SIDE OF THE ARPT.) WE VISUALLY CLRED THE AREA PRIOR TO XING THE RWYS ALONG OUR TAXI RTE. AFTER XING BACK OVER OUR LNDG RWY, RWY 23, GND CTL ADVISED US THAT WE HAD 'MISSED OUR TURN FOR FBO.' AFTER QUESTIONING THE CTLR, WE WERE ADVISED THAT THERE ARE 2 'XX FBO'S' ON THIS FIELD. ONE IS 'XX FBO' AND THE OTHER IS 'XXY FBO.' TO MAKE THE SIT MORE DIFFICULT, 'XX FBO' IS LOCATED ON THE NE SIDE OF THE ARPT AS OPPOSED TO THE NW LOCATION OF 'XXY FBO.' ON OUR INITIAL CALL-UP TO GND CTL, NO MENTION WAS MADE OF 2 FBO'S. ASSUMPTIONS WERE MADE THAT THE FLC AND ATC WERE SPEAKING OF THE SAME DEST. THIS TYPE OF INCIDENT COULD BE AVOIDED IN THE FUTURE BY: 1) CHANGING THE NAME OF ONE OF THE FBO'S OPS TO AVOID CONFUSION. 2) VERIFYING THAT THE FLC AND ATC ARE CERTAIN AS TO THE ACFT'S DEST.

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.