 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Flight crew of an light transport reclarified runway assignment with approach controller and found error in initial runway assignment.
| Attributes | |
| ACN | 326250 |
| Time | |
| Date | 199601 |
| Day | Tue |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : ord |
| State Reference | IL |
| Altitude | msl bound lower : 5000 msl bound upper : 5000 |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : ord |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 135 |
| Flight Phase | descent : approach descent other |
| Route In Use | arrival other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | other other : other pilot : instrument pilot : cfi pilot : atp |
| Experience | flight time last 90 days : 270 flight time total : 2100 flight time type : 600 |
| ASRS Report | 326250 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : instrument pilot : commercial |
| Events | |
| Anomaly | other anomaly other other spatial deviation |
| Independent Detector | other flight crewa |
| Resolutory Action | controller : issued new clearance |
| Consequence | Other |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | other |
Narrative:
Approaching ord from the north we were instructed to intercept the localizer at ord, which I thought to be runway 14R. I specifically read back runway 14R, so I assumed I was correct. When looking for a fix on the approach plate 22 mi out, I couldn't find it, and immediately queried the controller for proper approach, which he said runway 14L, and gave us a vector to intercept again. I don't believe a conflict ever existed, but it could have if I didn't discover it sooner. Probable cause: when we initially checked on with approach, controller didn't tell, or we didn't understand approach assignment. When controller told us to intercept, and I read back right side, I didn't hear a response. I assumed I was right. Causes: frequency very congested, failure of pilots (us) to understand or verify approach assignment as soon as we checked on with approach. Also, failure of controller to correct us when I read back wrong approach.
Original NASA ASRS Text
Title: FLC OF AN LTT RECLARIFIED RWY ASSIGNMENT WITH APCH CTLR AND FOUND ERROR IN INITIAL RWY ASSIGNMENT.
Narrative: APCHING ORD FROM THE N WE WERE INSTRUCTED TO INTERCEPT THE LOC AT ORD, WHICH I THOUGHT TO BE RWY 14R. I SPECIFICALLY READ BACK RWY 14R, SO I ASSUMED I WAS CORRECT. WHEN LOOKING FOR A FIX ON THE APCH PLATE 22 MI OUT, I COULDN'T FIND IT, AND IMMEDIATELY QUERIED THE CTLR FOR PROPER APCH, WHICH HE SAID RWY 14L, AND GAVE US A VECTOR TO INTERCEPT AGAIN. I DON'T BELIEVE A CONFLICT EVER EXISTED, BUT IT COULD HAVE IF I DIDN'T DISCOVER IT SOONER. PROBABLE CAUSE: WHEN WE INITIALLY CHKED ON WITH APCH, CTLR DIDN'T TELL, OR WE DIDN'T UNDERSTAND APCH ASSIGNMENT. WHEN CTLR TOLD US TO INTERCEPT, AND I READ BACK R SIDE, I DIDN'T HEAR A RESPONSE. I ASSUMED I WAS RIGHT. CAUSES: FREQ VERY CONGESTED, FAILURE OF PLTS (US) TO UNDERSTAND OR VERIFY APCH ASSIGNMENT AS SOON AS WE CHKED ON WITH APCH. ALSO, FAILURE OF CTLR TO CORRECT US WHEN I READ BACK WRONG APCH.
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.