 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An air carrier first officer questions an incomplete ATC clearance from koa because it appears to end on airway R465 at cundu intersection.
| Attributes | |
| ACN | 817990 |
| Time | |
| Date | 200812 |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : phko.airport |
| State Reference | HI |
| Altitude | agl single value : 0 |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | Widebody Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : parked |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Experience | flight time last 90 days : 161 flight time total : 14300 flight time type : 5332 |
| ASRS Report | 817900 |
| Events | |
| Anomaly | non adherence : company policies non adherence : far non adherence : published procedure |
| Independent Detector | other flight crewa |
| Resolutory Action | controller : issued new clearance flight crew : became reoriented |
| Supplementary | |
| Problem Areas | Company Flight Crew Human Performance ATC Human Performance |
| Primary Problem | Flight Crew Human Performance |
Narrative:
While verifying that the filed route from koa to ZZZ on the flight plan forecast agreed with the FMC programming; I noticed for the first time that the flight plan route filed with ATC seemed incomplete. The route over R465 showed the last fix as cundu. The flight plan route did list R465 after cundu; but no ending fix was denoted. I brought this up to the captain before we received our clearance from ATC. When we received our clearance from kona clearance delivery; it was 'V5 V11 upp; then as filed.' once airborne; we sent a message to dispatch; asking if leaving out the last fixes was appropriate. The dispatcher replied 'ATC flight plan should give ending fix&never seen one filed this way; must have something to do with our new planning system.' after some thought; I asked the captain what we would be expected to do in a lost communications scenario; with no fixes designated after cundu. Not only was the last fix along R465 omitted; but there was no follow-on fix that could serve as an IAF or feeder fix for an approach into ZZZ. We then sent a message to dispatch asking them to fix our flight plan route to reflect what we normally receive on our flight plan routing: R465 cinny ZZZ1 ZZZ. The message was sent; and dispatch modified our flight plan with ATC. I write this to bring attention to a potential programming error in our air carrier's new flight planning software. It could easily escape the attention of the pilots; as the body of the flight plan lists all the appropriate fixes along the route and would lead one to believe the filed route was complete and correct. Unfortunately; that listing was more complete; and did not comport with the incomplete route filed with ATC. Callback conversation with reporter revealed the following information: the reporter stated that the flight plan issuance problem appears to be localized to carriers using a certain flight planning system and was in effect only a short period of time.
Original NASA ASRS Text
Title: An air carrier First Officer questions an incomplete ATC clearance from KOA because it appears to end on airway R465 at CUNDU intersection.
Narrative: While verifying that the filed route from KOA to ZZZ on the flight plan forecast agreed with the FMC programming; I noticed for the first time that the Flight Plan Route filed with ATC seemed incomplete. The route over R465 showed the last fix as CUNDU. The Flight Plan Route did list R465 after CUNDU; but no ending fix was denoted. I brought this up to the Captain before we received our clearance from ATC. When we received our clearance from Kona Clearance Delivery; it was 'V5 V11 UPP; then as filed.' Once airborne; we sent a message to Dispatch; asking if leaving out the last fixes was appropriate. The Dispatcher replied 'ATC Flight Plan should give ending fix&never seen one filed this way; must have something to do with our new planning system.' After some thought; I asked the Captain what we would be expected to do in a lost communications scenario; with no fixes designated after CUNDU. Not only was the last fix along R465 omitted; but there was no follow-on fix that could serve as an IAF or feeder fix for an approach into ZZZ. We then sent a message to Dispatch asking them to fix our Flight Plan Route to reflect what we normally receive on our flight plan routing: R465 CINNY ZZZ1 ZZZ. The message was sent; and Dispatch modified our flight plan with ATC. I write this to bring attention to a potential programming error in our Air Carrier's new flight planning software. It could easily escape the attention of the pilots; as the body of the flight plan lists all the appropriate fixes along the route and would lead one to believe the filed route was complete and correct. Unfortunately; that listing was more complete; and did not comport with the incomplete route filed with ATC. Callback conversation with Reporter revealed the following information: The Reporter stated that the flight plan issuance problem appears to be localized to carriers using a certain flight planning system and was in effect only a short period of time.
Data retrieved from NASA's ASRS site as of May 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.