37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 398084 |
Time | |
Date | 199804 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : pit |
State Reference | PA |
Altitude | msl bound lower : 4000 msl bound upper : 4000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : pit tower : vgt |
Operator | common carrier : air carrier |
Make Model Name | DC-9 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Route In Use | arrival other enroute other |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B737-200 |
Operating Under FAR Part | Part 121 |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : flight engineer pilot : commercial pilot : instrument pilot : atp |
Experience | flight time last 90 days : 190 flight time total : 14600 flight time type : 8700 |
ASRS Report | 398084 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : flight engineer |
Experience | flight time last 90 days : 220 flight time total : 8000 flight time type : 3000 |
ASRS Report | 398080 |
Events | |
Anomaly | conflict : airborne less severe non adherence : clearance non adherence : published procedure non adherence : required legal separation other anomaly other other spatial deviation |
Independent Detector | other controllera other flight crewa |
Resolutory Action | flight crew : returned to intended course or assigned course |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 10400 vertical : 500 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
On a vector to intercept localizer runway 28L pit (parallel approachs were being conducted on runway 28R). The approach for runway 28L had been briefed by the first officer (PF), but when cleared to intercept the runway 28L localizer the frequency for ILS runway 28R was inadvertently selected. I (PNF) had mmj VOR/DME selected in my navigation radio. As localizer intercept was being conducted visual contact with another aircraft in the 2 O'clock position was established, the first officer immediately realized incorrect setting of ILS frequency and began turn back to runway 28L. Concurrently a TCASII TA had been received which was followed by an RA almost simultaneously with a corrective vector issued by pit approach control. A normal approach and landing was then made to runway 28L. ATC advised that a conflict had occurred and a follow-up phone call to the ATC facility after landing confirmed it. A personal preventive measure derived from this incident, and after a great deal of discussion and deliberation with the first officer, is that whenever the PF selects an approach NAVAID frequency he merely queries the other pilot concerning its accuracy. For example, PF: I have 108.9 selected, is that correct? The PNF would then be obligated to respond which would not only xchk the frequency, but the proper runway as well. One additional point of importance that could be made is that, regardless of any pilot's consistently proven abilities, mistakes can and will be made which increases the emphasis for the continuous need of an effective xchk and increased situational awareness.
Original NASA ASRS Text
Title: DC9 ACFT CLRED FOR APCH TO RWY 28L, PF, FO TUNED ILS FREQ FOR RWY 28R WHICH RESULTED IN LOSS OF SEPARATION WITH ACFT ON APCH TO RWY 28R. RPTR FO SAW OTHER ACFT AND REALIZED THE ERROR AND IMMEDIATELY TURNED BACK FOR RWY 28L WHILE SIMULTANEOUSLY APCH CTLR ALERTED THE FLC PLUS A TCASII RA.
Narrative: ON A VECTOR TO INTERCEPT LOC RWY 28L PIT (PARALLEL APCHS WERE BEING CONDUCTED ON RWY 28R). THE APCH FOR RWY 28L HAD BEEN BRIEFED BY THE FO (PF), BUT WHEN CLRED TO INTERCEPT THE RWY 28L LOC THE FREQ FOR ILS RWY 28R WAS INADVERTENTLY SELECTED. I (PNF) HAD MMJ VOR/DME SELECTED IN MY NAV RADIO. AS LOC INTERCEPT WAS BEING CONDUCTED VISUAL CONTACT WITH ANOTHER ACFT IN THE 2 O'CLOCK POS WAS ESTABLISHED, THE FO IMMEDIATELY REALIZED INCORRECT SETTING OF ILS FREQ AND BEGAN TURN BACK TO RWY 28L. CONCURRENTLY A TCASII TA HAD BEEN RECEIVED WHICH WAS FOLLOWED BY AN RA ALMOST SIMULTANEOUSLY WITH A CORRECTIVE VECTOR ISSUED BY PIT APCH CTL. A NORMAL APCH AND LNDG WAS THEN MADE TO RWY 28L. ATC ADVISED THAT A CONFLICT HAD OCCURRED AND A FOLLOW-UP PHONE CALL TO THE ATC FACILITY AFTER LNDG CONFIRMED IT. A PERSONAL PREVENTIVE MEASURE DERIVED FROM THIS INCIDENT, AND AFTER A GREAT DEAL OF DISCUSSION AND DELIBERATION WITH THE FO, IS THAT WHENEVER THE PF SELECTS AN APCH NAVAID FREQ HE MERELY QUERIES THE OTHER PLT CONCERNING ITS ACCURACY. FOR EXAMPLE, PF: I HAVE 108.9 SELECTED, IS THAT CORRECT? THE PNF WOULD THEN BE OBLIGATED TO RESPOND WHICH WOULD NOT ONLY XCHK THE FREQ, BUT THE PROPER RWY AS WELL. ONE ADDITIONAL POINT OF IMPORTANCE THAT COULD BE MADE IS THAT, REGARDLESS OF ANY PLT'S CONSISTENTLY PROVEN ABILITIES, MISTAKES CAN AND WILL BE MADE WHICH INCREASES THE EMPHASIS FOR THE CONTINUOUS NEED OF AN EFFECTIVE XCHK AND INCREASED SITUATIONAL AWARENESS.
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.