 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ARTCC radar controller gave a PA31 an IFR clearance with a block altitude while the aircraft was in another sector's airspace. Pointout and coordination was not done in a timely manner nor with approval of the sector in which the aircraft was, when the clearance was issued. Incident being investigated as an operational deviation.
| Attributes | |
| ACN | 378528 |
| Time | |
| Date | 199708 |
| Day | Mon |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | atc facility : fmg |
| State Reference | NV |
| Altitude | msl bound lower : 16000 msl bound upper : 19000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zoa |
| Operator | general aviation : corporate |
| Make Model Name | PA-31 Navajo Chieftan/Mojave/Navajo T1020 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | cruise other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller military : 4 controller radar : 2 |
| ASRS Report | 378528 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller military : 3 controller radar : 11 |
| ASRS Report | 378529 |
| Events | |
| Anomaly | non adherence : published procedure other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | other |
| Consequence | faa : investigated |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Deviation |
Narrative:
On aug/xa/97 I was working low altitude sector 45 when a data block appeared on my scope indicating 160b190. I hit flight plan readout and then slant zeroed the data block awaiting coordination. Low altitude sector 22 calls and wants to know what this aircraft is doing. I say, I don't know, I don't know anything about him, you'd have to call sector 46. Apparently the aircraft was issued an IFR clearance without prior coordination. I then received a pointout from the sector 46 controller. At this time I did not feel there was any wrong doing or violation. It is now being investigated as a deviation. Supplemental information from acn 378529: aircraft was radar idented and given IFR clearance in another controller's airspace. Coordination was not on a recorded line and is being disputed.
Original NASA ASRS Text
Title: ARTCC RADAR CTLR GAVE A PA31 AN IFR CLRNC WITH A BLOCK ALT WHILE THE ACFT WAS IN ANOTHER SECTOR'S AIRSPACE. POINTOUT AND COORD WAS NOT DONE IN A TIMELY MANNER NOR WITH APPROVAL OF THE SECTOR IN WHICH THE ACFT WAS, WHEN THE CLRNC WAS ISSUED. INCIDENT BEING INVESTIGATED AS AN OPDEV.
Narrative: ON AUG/XA/97 I WAS WORKING LOW ALT SECTOR 45 WHEN A DATA BLOCK APPEARED ON MY SCOPE INDICATING 160B190. I HIT FLT PLAN READOUT AND THEN SLANT ZEROED THE DATA BLOCK AWAITING COORD. LOW ALT SECTOR 22 CALLS AND WANTS TO KNOW WHAT THIS ACFT IS DOING. I SAY, I DON'T KNOW, I DON'T KNOW ANYTHING ABOUT HIM, YOU'D HAVE TO CALL SECTOR 46. APPARENTLY THE ACFT WAS ISSUED AN IFR CLRNC WITHOUT PRIOR COORD. I THEN RECEIVED A POINTOUT FROM THE SECTOR 46 CTLR. AT THIS TIME I DID NOT FEEL THERE WAS ANY WRONG DOING OR VIOLATION. IT IS NOW BEING INVESTIGATED AS A DEV. SUPPLEMENTAL INFO FROM ACN 378529: ACFT WAS RADAR IDENTED AND GIVEN IFR CLRNC IN ANOTHER CTLR'S AIRSPACE. COORD WAS NOT ON A RECORDED LINE AND IS BEING DISPUTED.
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.