 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZME controllers describe a procedural error when a developmental changed beacon codes on an aircraft within an adjacent facilities airspace resulting in the aircraft going into a coast status; the action contrary to LOA's.
| Attributes | |
| ACN | 902205 |
| Time | |
| Date | 201008 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | BNA.Airport |
| State Reference | TN |
| Aircraft 1 | |
| Make Model Name | S-70/UH-60 Blackhawk/Seahawk/Pavehawk/Knighthawk/Jayhawk/Presidential Hawk |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Qualification | Air Traffic Control Fully Certified |
| Person 2 | |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I received an automated hand off from bna approach on helicopter X at 7000 ft. The aircraft was not squawking the code showing in his flight plan. I changed the aircraft's code to the appropriate code without asking bna about 10 miles from my boundary. Bna called the supervisor and asked that we be careful not to change codes without asking. This is the first time I have seen a bad (or different) code from bna. This shouldn't and usually is no problem or normal occurrence. The supervisor advised me that the d-side in training somehow imputed a new code for the aircraft. I will be sure not to change codes in approaches airspace without prior coordination. Recommendation; constantly review loas and be sure which airspace allows code changes and who doesn't. Don't change codes in approaches airspace without prior coordination.
Original NASA ASRS Text
Title: ZME Controllers describe a procedural error when a developmental changed beacon codes on an aircraft within an adjacent facilities airspace resulting in the aircraft going into a COAST status; the action contrary to LOA's.
Narrative: I received an automated hand off from BNA Approach on Helicopter X at 7000 FT. The aircraft was not squawking the code showing in his flight plan. I changed the aircraft's code to the appropriate code without asking BNA about 10 miles from my boundary. BNA called the Supervisor and asked that we be careful not to change codes without asking. This is the first time I have seen a bad (or different) code from BNA. This shouldn't and usually is no problem or normal occurrence. The Supervisor advised me that the D-Side in training somehow imputed a new code for the aircraft. I will be sure not to change codes in approaches airspace without prior coordination. Recommendation; constantly review LOAs and be sure which airspace allows code changes and who doesn't. Don't change codes in approaches airspace without prior coordination.
Data retrieved from NASA's ASRS site as of April 2012 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.