37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 765348 |
Time | |
Date | 200712 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : dan.airport |
State Reference | VA |
Altitude | msl single value : 4000 |
Environment | |
Flight Conditions | Marginal |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zdc.artcc tower : zzz.tower |
Make Model Name | Caravan Undifferentiated |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach |
Route In Use | arrival : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller limited radar : 6 controller non radar : 6 controller radar : 4 controller time certified in position1 : 1 controller time certified in position2 : 6 |
ASRS Report | 765348 |
Events | |
Anomaly | other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : anomaly accepted |
Supplementary | |
Problem Areas | FAA Maintenance Human Performance |
Primary Problem | FAA |
Situations | |
ATC Facility | communication equipment : zdc.artcc |
Narrative:
OJT was being conducted on south boston (SBV22) at the time and the aircraft was on frequency 124.05 at the time. Due to poor or non existent frequency coverage; the sector was also using a borrow ultra high sector frequency 134.62. Aircraft X was on a vector for the ILS runway 2 at danville (dan) municipal airport. When the aircraft reached 15 mi southeast of dan the controller tried to give the aircraft a turn and altitude clearance to intercept the localizer. The aircraft never responded to any instruction; as well as attempts to have the aircraft 'identify' if it heard the controller with no response. The controller was also experiencing numerous problems with both frequencys from other aircraft. Another aircraft was used to relay to aircraft X to vector to the ILS and place the aircraft on 134.62. This frequency was still very poor for most aircraft; and it took several xmissions to issue clrncs. These frequencys have been written up numerous times. To date there has been nothing to resolve the issues with these frequencys and if they are not resolved as they have worsened; this could result in a fatal situation.
Original NASA ASRS Text
Title: ZDC CTLR VOICED CONCERN REGARDING CONTINUING RADIO PROBLEMS AT SBV22 SECTOR.
Narrative: OJT WAS BEING CONDUCTED ON S BOSTON (SBV22) AT THE TIME AND THE ACFT WAS ON FREQ 124.05 AT THE TIME. DUE TO POOR OR NON EXISTENT FREQ COVERAGE; THE SECTOR WAS ALSO USING A BORROW ULTRA HIGH SECTOR FREQ 134.62. ACFT X WAS ON A VECTOR FOR THE ILS RWY 2 AT DANVILLE (DAN) MUNICIPAL ARPT. WHEN THE ACFT REACHED 15 MI SE OF DAN THE CTLR TRIED TO GIVE THE ACFT A TURN AND ALT CLRNC TO INTERCEPT THE LOC. THE ACFT NEVER RESPONDED TO ANY INSTRUCTION; AS WELL AS ATTEMPTS TO HAVE THE ACFT 'IDENT' IF IT HEARD THE CTLR WITH NO RESPONSE. THE CTLR WAS ALSO EXPERIENCING NUMEROUS PROBS WITH BOTH FREQS FROM OTHER ACFT. ANOTHER ACFT WAS USED TO RELAY TO ACFT X TO VECTOR TO THE ILS AND PLACE THE ACFT ON 134.62. THIS FREQ WAS STILL VERY POOR FOR MOST ACFT; AND IT TOOK SEVERAL XMISSIONS TO ISSUE CLRNCS. THESE FREQS HAVE BEEN WRITTEN UP NUMEROUS TIMES. TO DATE THERE HAS BEEN NOTHING TO RESOLVE THE ISSUES WITH THESE FREQS AND IF THEY ARE NOT RESOLVED AS THEY HAVE WORSENED; THIS COULD RESULT IN A FATAL SITUATION.
Data retrieved from NASA's ASRS site as of January 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.