37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 686831 |
Time | |
Date | 200602 |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : atl.airport |
State Reference | GA |
Environment | |
Flight Conditions | IMC |
Weather Elements | Rain Ice Fog Turbulence |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : a80.tracon |
Operator | common carrier : air carrier |
Make Model Name | Boeing Company Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | climbout : intermediate altitude |
Route In Use | departure sid : bravs |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : atp pilot : multi engine |
Experience | flight time last 90 days : 200 flight time total : 14000 flight time type : 5000 |
ASRS Report | 686831 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | aircraft equipment problem : critical inflight encounter : turbulence inflight encounter : weather inflight encounter other non adherence : clearance non adherence : published procedure other spatial deviation |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | controller : issued alert controller : issued new clearance flight crew : overcame equipment problem flight crew : overrode automation |
Supplementary | |
Problem Areas | Flight Crew Human Performance Chart Or Publication Aircraft Weather |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
I reviewed the dispatch release and entered the route ALTMCO1R. Next; I entered runway 9L with the lidas transition. I then checked the distance to mco. Everything was correct. While I finished reviewing and signing the paperwork and logbook; the first officer had returned from outside. He had the paperwork in his hand and was reviewing the flight plan. He then made the statement that 'the flight plan was wrong.' I looked down and noticed that instead of the company route I had entered and checked; the mcdu now had katl/kmco. I asked 'had he put that in there?' and he said 'no.' I told him re-enter the flight plan; to put the company route back in the mcdu including the runway 9L lidas transition. I rechked the mcdu and it appeared to be correct. We completed the before taxi checklist and started to taxi. Then we started the right engine. I briefed the first officer all of the required items including runway; confirming runway 9L and lidas transition was in the mcdu. I then called for the before takeoff checklist to the line. The tower asked the first officer for his departure fix. The fix he told the tower was the fix for the runway 8R bravs departure hrshl. I did not hear this conversation; but the first officer said the tower controller repeated the same fix hrshl. We were then cleared for takeoff. When we entered the clouds; we encountered moderate/severe turbulence with moderate rime ice building up on the aircraft. Almost immediately after we entered the clouds; we lost our navigation magenta line all the way to bravs intersection. I fought to keep the aircraft stable and I told the first officer to get back my navigation! The first officer looked at his SID plate and instead of lidas transition in the mcdu; he mistakenly entered hrshl in the FMS. He then said navigation was available and pushed navigation. I saw the aircraft was to the right of the course and started to correct to the left. When I looked at the TCAS and navigation display; I realized my course should not angle me to the left. I immediately started a right turn and was about to call ATC to inform them we had lost our navigation and needed vectors when I received a call from departure. They stated; 'air carrier XXX turn right to 180 degrees immediately!' we continued the turn and rolled out on 180 degrees. There was a short pause and then the controller came back with; 'air carrier X; say cleared to fix.' the first officer answered incorrectly and said hrshl; which was the fix he had accidentally placed in the FMS. The departure controller said 'hrshl; roger.' the flight then continued to mco; no one asked us to call a phone number.
Original NASA ASRS Text
Title: B717 FLT CREW HAS TRACK DEV ON BRAVS RNAV SID FROM ATL WHEN FO PROGRAMS INCORRECT INITIAL WAYPOINT FOR RWY 9L.
Narrative: I REVIEWED THE DISPATCH RELEASE AND ENTERED THE RTE ALTMCO1R. NEXT; I ENTERED RWY 9L WITH THE LIDAS TRANSITION. I THEN CHKED THE DISTANCE TO MCO. EVERYTHING WAS CORRECT. WHILE I FINISHED REVIEWING AND SIGNING THE PAPERWORK AND LOGBOOK; THE FO HAD RETURNED FROM OUTSIDE. HE HAD THE PAPERWORK IN HIS HAND AND WAS REVIEWING THE FLT PLAN. HE THEN MADE THE STATEMENT THAT 'THE FLT PLAN WAS WRONG.' I LOOKED DOWN AND NOTICED THAT INSTEAD OF THE COMPANY RTE I HAD ENTERED AND CHKED; THE MCDU NOW HAD KATL/KMCO. I ASKED 'HAD HE PUT THAT IN THERE?' AND HE SAID 'NO.' I TOLD HIM RE-ENTER THE FLT PLAN; TO PUT THE COMPANY RTE BACK IN THE MCDU INCLUDING THE RWY 9L LIDAS TRANSITION. I RECHKED THE MCDU AND IT APPEARED TO BE CORRECT. WE COMPLETED THE BEFORE TAXI CHKLIST AND STARTED TO TAXI. THEN WE STARTED THE R ENG. I BRIEFED THE FO ALL OF THE REQUIRED ITEMS INCLUDING RWY; CONFIRMING RWY 9L AND LIDAS TRANSITION WAS IN THE MCDU. I THEN CALLED FOR THE BEFORE TKOF CHKLIST TO THE LINE. THE TWR ASKED THE FO FOR HIS DEP FIX. THE FIX HE TOLD THE TWR WAS THE FIX FOR THE RWY 8R BRAVS DEP HRSHL. I DID NOT HEAR THIS CONVERSATION; BUT THE FO SAID THE TWR CTLR REPEATED THE SAME FIX HRSHL. WE WERE THEN CLRED FOR TKOF. WHEN WE ENTERED THE CLOUDS; WE ENCOUNTERED MODERATE/SEVERE TURB WITH MODERATE RIME ICE BUILDING UP ON THE ACFT. ALMOST IMMEDIATELY AFTER WE ENTERED THE CLOUDS; WE LOST OUR NAV MAGENTA LINE ALL THE WAY TO BRAVS INTXN. I FOUGHT TO KEEP THE ACFT STABLE AND I TOLD THE FO TO GET BACK MY NAV! THE FO LOOKED AT HIS SID PLATE AND INSTEAD OF LIDAS TRANSITION IN THE MCDU; HE MISTAKENLY ENTERED HRSHL IN THE FMS. HE THEN SAID NAV WAS AVAILABLE AND PUSHED NAV. I SAW THE ACFT WAS TO THE R OF THE COURSE AND STARTED TO CORRECT TO THE L. WHEN I LOOKED AT THE TCAS AND NAV DISPLAY; I REALIZED MY COURSE SHOULD NOT ANGLE ME TO THE L. I IMMEDIATELY STARTED A R TURN AND WAS ABOUT TO CALL ATC TO INFORM THEM WE HAD LOST OUR NAV AND NEEDED VECTORS WHEN I RECEIVED A CALL FROM DEP. THEY STATED; 'ACR XXX TURN R TO 180 DEGS IMMEDIATELY!' WE CONTINUED THE TURN AND ROLLED OUT ON 180 DEGS. THERE WAS A SHORT PAUSE AND THEN THE CTLR CAME BACK WITH; 'ACR X; SAY CLRED TO FIX.' THE FO ANSWERED INCORRECTLY AND SAID HRSHL; WHICH WAS THE FIX HE HAD ACCIDENTALLY PLACED IN THE FMS. THE DEP CTLR SAID 'HRSHL; ROGER.' THE FLT THEN CONTINUED TO MCO; NO ONE ASKED US TO CALL A PHONE NUMBER.
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.