 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 on RNAV rnp approach to apg caused concern with zan controller because of the aircraft radar position.
| Attributes | |
| ACN | 615792 |
| Time | |
| Date | 200404 |
| Day | Tue |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : apg.airport |
| State Reference | AK |
| Altitude | agl single value : 1000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | artcc : zan.artcc tower : pbi.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B737-400 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other |
| Flight Phase | descent : approach |
| Route In Use | approach : circling arrival other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| ASRS Report | 615792 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | none taken : anomaly accepted |
| Consequence | faa : reviewed incident with flight crew other |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
Narrative:
Flight had a rerte with an added leg to apg. We requested and filed the DOOZI1.lvd transition and requested the RNAV rnp runway 4 with ktn radio. We requested and were cleared the RNAV rnp runway 4 apg, maintain 7000 ft until on a published portion. While on the RNAV rnp runway 4, approximately culam at 1500 ft, while talking to jnu radio, they called and zan showed us on radar for runway 22. This call at the time did not make sense because we had the runway in sight with runway lights on. I told jnu radio we had the airport in sight, on a right base for runway 4. After landing, I called dispatch and asked him to call zan to ask what was going on. When we arrived at jnu, I again called dispatch and he said the zan controller showed on the ATC strip we were doing the RNAV rnp to runway 22 apg. Zan never requested a call from us or said anything else. This as soon as possible report is to request a follow-up if there was a miscom (as a note, had to request frequency change to go to jnu radio to make position report for approach. There was only 1 controller working several sectors ktn to anc).
Original NASA ASRS Text
Title: B737 ON RNAV RNP APCH TO APG CAUSED CONCERN WITH ZAN CTLR BECAUSE OF THE ACFT RADAR POS.
Narrative: FLT HAD A RERTE WITH AN ADDED LEG TO APG. WE REQUESTED AND FILED THE DOOZI1.LVD TRANSITION AND REQUESTED THE RNAV RNP RWY 4 WITH KTN RADIO. WE REQUESTED AND WERE CLRED THE RNAV RNP RWY 4 APG, MAINTAIN 7000 FT UNTIL ON A PUBLISHED PORTION. WHILE ON THE RNAV RNP RWY 4, APPROX CULAM AT 1500 FT, WHILE TALKING TO JNU RADIO, THEY CALLED AND ZAN SHOWED US ON RADAR FOR RWY 22. THIS CALL AT THE TIME DID NOT MAKE SENSE BECAUSE WE HAD THE RWY IN SIGHT WITH RWY LIGHTS ON. I TOLD JNU RADIO WE HAD THE ARPT IN SIGHT, ON A R BASE FOR RWY 4. AFTER LNDG, I CALLED DISPATCH AND ASKED HIM TO CALL ZAN TO ASK WHAT WAS GOING ON. WHEN WE ARRIVED AT JNU, I AGAIN CALLED DISPATCH AND HE SAID THE ZAN CTLR SHOWED ON THE ATC STRIP WE WERE DOING THE RNAV RNP TO RWY 22 APG. ZAN NEVER REQUESTED A CALL FROM US OR SAID ANYTHING ELSE. THIS ASAP RPT IS TO REQUEST A FOLLOW-UP IF THERE WAS A MISCOM (AS A NOTE, HAD TO REQUEST FREQ CHANGE TO GO TO JNU RADIO TO MAKE POS RPT FOR APCH. THERE WAS ONLY 1 CTLR WORKING SEVERAL SECTORS KTN TO ANC).
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.