 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-300 captain on approach to oak at 1000 ft received call from an entity identifying themselves as oak tower when in fact it was not oak tower. Reporter called oak tower after landing to discuss.
| Attributes | |
| ACN | 739764 |
| Time | |
| Date | 200705 |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : oak.airport |
| State Reference | CA |
| Altitude | agl single value : 1000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | tower : oak.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : approach |
| Route In Use | approach : visual |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Experience | flight time last 90 days : 156 flight time type : 4500 |
| ASRS Report | 739764 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : local |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : anomaly accepted |
| Consequence | faa : reviewed incident with flight crew |
| Supplementary | |
| Problem Areas | Environmental Factor |
| Primary Problem | Ambiguous |
Narrative:
On approach to oak runway 29 at 1000 ft; we received a scratchy partially garbled radio call; 'company #; oak tower.' we responded with our callsign. Then oak tower responded; 'go ahead.' that's when we realized that the transmission we received at 1000 ft was not oak tower. We advised them on the ground after landing what had happened. I followed up with a phone to oak tower south cabin attendant and talked with the controller. He said they had been receiving information on 'interference' issues. I told him this did not seem like interference; but more like someone deliberately imitating the control tower on their frequency. I think that someone in the vicinity of the approach to runway 29 may be spoofing tower control and who knows who else. This should be investigated. The transmission was a distraction that was handled appropriately by my crew.
Original NASA ASRS Text
Title: B737-300 CAPT ON APCH TO OAK AT 1000 FT RECEIVED CALL FROM AN ENTITY IDENTIFYING THEMSELVES AS OAK TWR WHEN IN FACT IT WAS NOT OAK TWR. RPTR CALLED OAK TWR AFTER LNDG TO DISCUSS.
Narrative: ON APCH TO OAK RWY 29 AT 1000 FT; WE RECEIVED A SCRATCHY PARTIALLY GARBLED RADIO CALL; 'COMPANY #; OAK TWR.' WE RESPONDED WITH OUR CALLSIGN. THEN OAK TWR RESPONDED; 'GO AHEAD.' THAT'S WHEN WE REALIZED THAT THE TRANSMISSION WE RECEIVED AT 1000 FT WAS NOT OAK TWR. WE ADVISED THEM ON THE GND AFTER LNDG WHAT HAD HAPPENED. I FOLLOWED UP WITH A PHONE TO OAK TWR SOUTH CAB AND TALKED WITH THE CTLR. HE SAID THEY HAD BEEN RECEIVING INFORMATION ON 'INTERFERENCE' ISSUES. I TOLD HIM THIS DID NOT SEEM LIKE INTERFERENCE; BUT MORE LIKE SOMEONE DELIBERATELY IMITATING THE CTL TWR ON THEIR FREQUENCY. I THINK THAT SOMEONE IN THE VICINITY OF THE APCH TO RWY 29 MAY BE SPOOFING TWR CTL AND WHO KNOWS WHO ELSE. THIS SHOULD BE INVESTIGATED. THE TRANSMISSION WAS A DISTRACTION THAT WAS HANDLED APPROPRIATELY BY MY CREW.
Data retrieved from NASA's ASRS site as of January 2009 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.