 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZTL controller described IFR clearance/release confusion for multiple avl departures during non tower operations; claiming FSS procedures/performance inadequate.
| Attributes | |
| ACN | 786407 |
| Time | |
| Date | 200805 |
| Local Time Of Day | 0001 To 0600 |
| Place | |
| Locale Reference | airport : avl.airport |
| State Reference | NC |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | Marginal |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | tower : den.tower |
| Operator | common carrier : air carrier |
| Make Model Name | Regional Jet 200 ER&LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : preflight |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | artcc : ztl.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | Regional Jet 200 ER&LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : preflight |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : clearance delivery controller : radar |
| Qualification | controller : radar |
| Experience | controller radar : 18.5 |
| ASRS Report | 786407 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | FAA Flight Crew Human Performance ATC Human Performance |
| Primary Problem | FAA |
Narrative:
Raleigh durham FSS for clearance off of asheville airport. Aircraft X CRJ2/Q. I gave the clearance to FSS but the clearance was never read back and no initials were given. Approximately 2 mins later; aircraft Y called on my frequency for a clearance off of asheville airport also. I did not know if aircraft X had a clearance or not. So I called rdu FSS to verify aircraft X had a clearance. The person at rdu FSS did not know of the clearance and neither did anyone else; so I asked aircraft Y if he could talk to the aircraft X. He said the aircraft X 'was ignoring him.' I then tried rdu FSS again with no success. Then; an aircraft Z came off tri and had him try the frequency or company to find out if the aircraft X had a clearance. Aircraft X then checked on frequency climbing; off of avl airport; 10000 ft (which was not the altitude I gave through FSS).
Original NASA ASRS Text
Title: ZTL CTLR DESCRIBED IFR CLRNC/RELEASE CONFUSION FOR MULTIPLE AVL DEPS DURING NON TWR OPS; CLAIMING FSS PROCS/PERFORMANCE INADEQUATE.
Narrative: RALEIGH DURHAM FSS FOR CLRNC OFF OF ASHEVILLE ARPT. ACFT X CRJ2/Q. I GAVE THE CLRNC TO FSS BUT THE CLRNC WAS NEVER READ BACK AND NO INITIALS WERE GIVEN. APPROX 2 MINS LATER; ACFT Y CALLED ON MY FREQ FOR A CLRNC OFF OF ASHEVILLE ARPT ALSO. I DID NOT KNOW IF ACFT X HAD A CLRNC OR NOT. SO I CALLED RDU FSS TO VERIFY ACFT X HAD A CLRNC. THE PERSON AT RDU FSS DID NOT KNOW OF THE CLRNC AND NEITHER DID ANYONE ELSE; SO I ASKED ACFT Y IF HE COULD TALK TO THE ACFT X. HE SAID THE ACFT X 'WAS IGNORING HIM.' I THEN TRIED RDU FSS AGAIN WITH NO SUCCESS. THEN; AN ACFT Z CAME OFF TRI AND HAD HIM TRY THE FREQ OR COMPANY TO FIND OUT IF THE ACFT X HAD A CLRNC. ACFT X THEN CHKED ON FREQ CLBING; OFF OF AVL ARPT; 10000 FT (WHICH WAS NOT THE ALT I GAVE THROUGH FSS).
Data retrieved from NASA's ASRS site as of May 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.