37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 205988 |
Time | |
Date | 199203 |
Day | Sat |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : fpo |
State Reference | FO |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Light Transport, Low Wing, 2 Turboprop Eng |
Navigation In Use | Other Other |
Flight Phase | ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 250 flight time total : 5400 flight time type : 1500 |
ASRS Report | 205988 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | incursion : runway non adherence : far |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Situations | |
ATC Facility | procedure or policy : unspecified |
Narrative:
Flight taxied out of fpo, bh. After 3 attempts to call ground control, fpo ground answered. They cleared us to taxi to runway 6. As flight taxied flight was cleared for takeoff on ground control. I, as captain, tried to confirm takeoff clearance on tower frequency, but no one answered. I then returned to ground control and stated that we were rolling for takeoff on runway 6. On the takeoff roll, I heard fpo ground say that we should have had a takeoff clearance before we departed, because there was traffic on final. We told the controller that both me and my first officer heard and responded to the takeoff clearance on ground control. There was no traffic conflict and the traffic on final did not have to go around. Apparently, there is a serious communication problem in the bahamas. I fly there frequently with company and the communication with fpo are always lacking. It seems to all the pilots that fpo just doesn't seem to care and answer the radio. This is an on-going problem that needs to be addressed.
Original NASA ASRS Text
Title: LTT CLRED FOR TKOF BY GND CTL. TRIES TO CONFIRM ON LCL FREQ WITH NO RESPONSE. DEPARTS WITH COM ON GND CTL THAT 'ROLLING FOR TKOF RWY 6.' CHASTISED BY GND CTL. FOR TKOF WITHOUT CLRNC.
Narrative: FLT TAXIED OUT OF FPO, BH. AFTER 3 ATTEMPTS TO CALL GND CTL, FPO GND ANSWERED. THEY CLRED US TO TAXI TO RWY 6. AS FLT TAXIED FLT WAS CLRED FOR TKOF ON GND CTL. I, AS CAPT, TRIED TO CONFIRM TKOF CLRNC ON TWR FREQ, BUT NO ONE ANSWERED. I THEN RETURNED TO GND CTL AND STATED THAT WE WERE ROLLING FOR TKOF ON RWY 6. ON THE TKOF ROLL, I HEARD FPO GND SAY THAT WE SHOULD HAVE HAD A TKOF CLRNC BEFORE WE DEPARTED, BECAUSE THERE WAS TFC ON FINAL. WE TOLD THE CTLR THAT BOTH ME AND MY FO HEARD AND RESPONDED TO THE TKOF CLRNC ON GND CTL. THERE WAS NO TFC CONFLICT AND THE TFC ON FINAL DID NOT HAVE TO GAR. APPARENTLY, THERE IS A SERIOUS COM PROBLEM IN THE BAHAMAS. I FLY THERE FREQUENTLY WITH COMPANY AND THE COM WITH FPO ARE ALWAYS LACKING. IT SEEMS TO ALL THE PLTS THAT FPO JUST DOESN'T SEEM TO CARE AND ANSWER THE RADIO. THIS IS AN ON-GOING PROBLEM THAT NEEDS TO BE ADDRESSED.
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.