 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Flight crew failed to follow STAR as amended by NOTAM; flying published heading rather than direct VOR as per NOTAM.
| Attributes | |
| ACN | 737328 |
| Time | |
| Date | 200705 |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : ord.airport |
| State Reference | IL |
| Altitude | msl single value : 11000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | tracon : c90.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other |
| Flight Phase | descent : approach |
| Route In Use | arrival star : royko |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Experience | flight time last 90 days : 100 flight time total : 14000 flight time type : 3000 |
| ASRS Report | 737328 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Events | |
| Anomaly | non adherence : published procedure other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | flight crew : returned to intended or assigned course |
| Supplementary | |
| Problem Areas | Airport FAA Chart Or Publication |
| Primary Problem | Ambiguous |
Narrative:
After leaving bearz inbound on the royko 1 arrival approach mentioned to us that it appeared we were on a 310 degree heading as published on the chart. Our ground track was close to the ord VOR but after reviewing the NOTAMS again the second time I discovered the no 3/18 ord rokyo 1 arrival stating from bearz we were to fly direct ord. A probable cause for this is the fact that the NOTAMS for ord; as they come off the ACARS printer; are over 6 ft long. By the time one reads through all the items it can get lost which one was read that applies to our route. If the NOTAMS are to continue to be this long; a suggestion would be to separate NOTAMS into arrival and separate departure NOTAMS. Could the route specific NOTAMS be placed in the dispatch remarks section of the computer generated flight plan? Personally; I will change the method in which I review NOTAMS. Now I will circle or cross off which ones in particular are for our route of flight and runway.
Original NASA ASRS Text
Title: FLT CREW FAILED TO FOLLOW STAR AS AMENDED BY NOTAM; FLYING PUBLISHED HDG RATHER THAN DIRECT VOR AS PER NOTAM.
Narrative: AFTER LEAVING BEARZ INBOUND ON THE ROYKO 1 ARR APCH MENTIONED TO US THAT IT APPEARED WE WERE ON A 310 DEG HDG AS PUBLISHED ON THE CHART. OUR GND TRACK WAS CLOSE TO THE ORD VOR BUT AFTER REVIEWING THE NOTAMS AGAIN THE SECOND TIME I DISCOVERED THE NO 3/18 ORD ROKYO 1 ARR STATING FROM BEARZ WE WERE TO FLY DIRECT ORD. A PROBABLE CAUSE FOR THIS IS THE FACT THAT THE NOTAMS FOR ORD; AS THEY COME OFF THE ACARS PRINTER; ARE OVER 6 FT LONG. BY THE TIME ONE READS THROUGH ALL THE ITEMS IT CAN GET LOST WHICH ONE WAS READ THAT APPLIES TO OUR RTE. IF THE NOTAMS ARE TO CONTINUE TO BE THIS LONG; A SUGGESTION WOULD BE TO SEPARATE NOTAMS INTO ARR AND SEPARATE DEP NOTAMS. COULD THE RTE SPECIFIC NOTAMS BE PLACED IN THE DISPATCH REMARKS SECTION OF THE COMPUTER GENERATED FLT PLAN? PERSONALLY; I WILL CHANGE THE METHOD IN WHICH I REVIEW NOTAMS. NOW I WILL CIRCLE OR CROSS OFF WHICH ONES IN PARTICULAR ARE FOR OUR RTE OF FLT AND RWY.
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.