37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 105793 |
Time | |
Date | 198903 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : lyh |
State Reference | VA |
Altitude | msl bound lower : 6000 msl bound upper : 6000 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : roa |
Operator | common carrier : air carrier |
Make Model Name | Small Transport, Low Wing, 2 Turboprop Eng |
Flight Phase | cruise other |
Route In Use | arrival other enroute airway : roa |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
ASRS Report | 105793 |
Person 2 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Events | |
Anomaly | non adherence : published procedure other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : anomaly accepted |
Consequence | Other |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Deviation |
Narrative:
I received a briefing from the sector controller that I was relieving. During the briefing he directed my attention to an aircraft that was approaching lyh and wanted to make an ILS approach on his own west/O radar vectors. There was a squall line and heavy precipitation on the radar in the lyh area. The aircraft was in close proximity to the roa approach airspace and I asked the controller being relieved if a pointout had been given to roa approach. His answer was something like, 'a pointout has been given to roa approach.' the aircraft deviated around some of the WX and was well within roa approach airspace west/O a pointout or coordination. At the time of the briefing noise level within our facility was high as it always is at shift change time. There was a high noise level on the frequencys and at the time there was failure of the main frequencys and I switched to the back up system. Perhaps in the future items that need to be done should be stressed by not using contractions which might not be heard, such as 'has not' instead of 'hasn't,' or 'was not' instead of 'wasn't.' the aircraft did not conflict with any other traffic, but was in airspace controled by another facility west/O their knowledge.
Original NASA ASRS Text
Title: SMT ENTERED ADJACENT FAC AIRSPACE WITHOUT CLRNC.
Narrative: I RECEIVED A BRIEFING FROM THE SECTOR CTLR THAT I WAS RELIEVING. DURING THE BRIEFING HE DIRECTED MY ATTN TO AN ACFT THAT WAS APCHING LYH AND WANTED TO MAKE AN ILS APCH ON HIS OWN W/O RADAR VECTORS. THERE WAS A SQUALL LINE AND HEAVY PRECIPITATION ON THE RADAR IN THE LYH AREA. THE ACFT WAS IN CLOSE PROX TO THE ROA APCH AIRSPACE AND I ASKED THE CTLR BEING RELIEVED IF A POINTOUT HAD BEEN GIVEN TO ROA APCH. HIS ANSWER WAS SOMETHING LIKE, 'A POINTOUT HAS BEEN GIVEN TO ROA APCH.' THE ACFT DEVIATED AROUND SOME OF THE WX AND WAS WELL WITHIN ROA APCH AIRSPACE W/O A POINTOUT OR COORD. AT THE TIME OF THE BRIEFING NOISE LEVEL WITHIN OUR FAC WAS HIGH AS IT ALWAYS IS AT SHIFT CHANGE TIME. THERE WAS A HIGH NOISE LEVEL ON THE FREQS AND AT THE TIME THERE WAS FAILURE OF THE MAIN FREQS AND I SWITCHED TO THE BACK UP SYS. PERHAPS IN THE FUTURE ITEMS THAT NEED TO BE DONE SHOULD BE STRESSED BY NOT USING CONTRACTIONS WHICH MIGHT NOT BE HEARD, SUCH AS 'HAS NOT' INSTEAD OF 'HASN'T,' OR 'WAS NOT' INSTEAD OF 'WASN'T.' THE ACFT DID NOT CONFLICT WITH ANY OTHER TFC, BUT WAS IN AIRSPACE CTLED BY ANOTHER FAC W/O THEIR KNOWLEDGE.
Data retrieved from NASA's ASRS site as of August 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.