 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Fai FSS controller described a confused release event when the sequence was reversed and the wrong aircraft was released.
| Attributes | |
| ACN | 1102516 |
| Time | |
| Date | 201307 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | OME.Airport |
| State Reference | AK |
| Environment | |
| Flight Conditions | IMC |
| Aircraft 1 | |
| Make Model Name | PA-31 Navajo/Chieftan/Mojave/T1040 |
| Flight Phase | Initial Climb |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Caravan Undifferentiated |
| Flight Phase | Initial Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Flight Service |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
We were IFR with 500 ft ceiling and had a number of aircraft waiting with their IFR clearance with a hold for release. A PA31 requested an IFR clearance along with a C208. I requested the clearances from sector 3 in the order they had been requested. The PA31 followed by the C208. Based on this; the PA31 taxied out and waited for his release on the runway. Sector 3 called back with a release. I was expecting to hear the PA31 was released. The strip showed I called the PA31 off to sector 3; shortly after this sector 3 called to tell me they had released the C208 and not the PA31 and to make sure the C208 was still on the ground. The wrong aircraft had been released. This release for the C208 was something I was not expecting; based on past practices. Sector 3 would point out when the order of arrivals or departures were changed. This was not done this time. From my standpoint separation had been maintained. Point out when the order of arrivals or departures are changed. Releasing the C208 before the PA31 would have slowed traffic down because the PA31 was already on the runway while the C208 was still on the ramp. Don't expect to hear something. At times I will call an aircraft off at the same time I receive a release; I need to make sure I use the aircraft call sign as a double check that we are not both hearing what we expect to hear.
Original NASA ASRS Text
Title: FAI FSS Controller described a confused release event when the sequence was reversed and the wrong aircraft was released.
Narrative: We were IFR with 500 FT ceiling and had a number of aircraft waiting with their IFR clearance with a hold for release. A PA31 requested an IFR clearance along with a C208. I requested the clearances from Sector 3 in the order they had been requested. The PA31 followed by the C208. Based on this; the PA31 taxied out and waited for his release on the runway. Sector 3 called back with a release. I was expecting to hear the PA31 was released. The strip showed I called the PA31 off to Sector 3; shortly after this Sector 3 called to tell me they had released the C208 and not the PA31 and to make sure the C208 was still on the ground. The wrong aircraft had been released. This release for the C208 was something I was not expecting; based on past practices. Sector 3 would point out when the order of arrivals or departures were changed. This was not done this time. From my standpoint separation had been maintained. Point out when the order of arrivals or departures are changed. Releasing the C208 before the PA31 would have slowed traffic down because the PA31 was already on the runway while the C208 was still on the ramp. Don't expect to hear something. At times I will call an aircraft off at the same time I receive a release; I need to make sure I use the aircraft call sign as a double check that we are not both hearing what we expect to hear.
Data retrieved from NASA's ASRS site as of July 2013 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.