37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 924568 |
Time | |
Date | 201012 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | JFK.Airport |
State Reference | NY |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | A300 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Climb |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Engineer |
Experience | Flight Crew Last 90 Days 150 Flight Crew Total 11500 Flight Crew Type 4500 |
Events | |
Anomaly | Aircraft Equipment Problem Critical Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
We loaded and verified each waypoint in our SID. I noticed a waypoint that I was not familiar with. I cross checked it with the chart and felt it was correct as it was a climb crossing that was boxed and arrowed precisely on our SID. After we took off every thing was normal until after crossing cri VOR when the aircraft started a left turn. I immediately mentioned it to my first officer and then the aircraft turned back to the right. We were showing center line on the SID when the controller asked us if we were on the SID; I told him we showed center line. ATC told us we were 1.5 miles south of course. We continued uneventfully. This SID has been taken in and out of our FMC several times; I have had to build the SID previously and never had a problem. When the SID showed back up in the FMC I thought an extra waypoint had been added. I don't know if the data base is incorrect or if we made an error inserting the waypoint. The only way to prevent this was to immediately disconnect navigation mode and turn the aircraft back more quickly; at the time I didn't think the turn to the left was that significant.
Original NASA ASRS Text
Title: An A300-600 flight crew incorrectly programmed a SID in their FMGC and suffered a track deviation on departure.
Narrative: We loaded and verified each waypoint in our SID. I noticed a waypoint that I was not familiar with. I cross checked it with the chart and felt it was correct as it was a climb crossing that was boxed and arrowed precisely on our SID. After we took off every thing was normal until after crossing CRI VOR when the aircraft started a left turn. I immediately mentioned it to my First Officer and then the aircraft turned back to the right. We were showing center line on the SID when the controller asked us if we were on the SID; I told him we showed center line. ATC told us we were 1.5 miles south of course. We continued uneventfully. This SID has been taken in and out of our FMC several times; I have had to build the SID previously and never had a problem. When the SID showed back up in the FMC I thought an extra waypoint had been added. I don't know if the data base is incorrect or if we made an error inserting the waypoint. The only way to prevent this was to immediately disconnect NAV mode and turn the aircraft back more quickly; at the time I didn't think the turn to the left was that significant.
Data retrieved from NASA's ASRS site as of April 2012 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.