 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A300 flight crew departing atl on the CADIT9 departure and approaching ronii; is admonished by ATC for an early shallow banked turn to bedrk. Vectors are issued and the crew explains that the FMC was following its programing; although the early turns normally occur only at higher altitudes and airspeeds.
| Attributes | |
| ACN | 1246424 |
| Time | |
| Date | 201503 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ATL.Airport |
| State Reference | GA |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | A300 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Route In Use | Direct Vectors SID CADIT Nine |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | First Officer Pilot Flying |
| Person 2 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
On departure from atl; we were filed; cleared and flying the CADIT9 RNAV departure. Climbing through approximately 4000 feet and after checking on with atl departure control; we were advised radar contact and delete the speed at rbeka (normally the departure requires maintain 250 KT until rbeka). We acknowledged and deleted the 250 KT speed restriction at rbeka in the FMC. Approximately one minute later and climbing through 6000/250 knots; ATC queried us regarding our direction of flight. We replied we were in the turn to bedrk from ronii. The aircraft was in navigation and as it appeared to us; navigating properly with ronii the active waypoint. However; we did notice the FMC generated route displayed a considerable turn leading ronii to bedrk. ATC advised our turn was too early and ronii was still 4 nm ahead. We were then given instructions to fly an assigned heading before eventually given direct cadit. We complied and continued the flight uneventfully. I believe the deletion of the speed restriction at rbeka in the FMC may have caused the FMC to over compensate and excessively lead the turn to bedrk; anticipating an acceleration to 320 kts; although the aircraft was still at 250 kts; as desired.
Original NASA ASRS Text
Title: A300 flight crew departing ATL on the CADIT9 Departure and approaching RONII; is admonished by ATC for an early shallow banked turn to BEDRK. Vectors are issued and the crew explains that the FMC was following its programing; although the early turns normally occur only at higher altitudes and airspeeds.
Narrative: On departure from ATL; we were filed; cleared and flying the CADIT9 RNAV Departure. Climbing through approximately 4000 feet and after checking on with ATL Departure Control; we were advised radar contact and delete the speed at RBEKA (normally the departure requires MAINTAIN 250 KT until RBEKA). We acknowledged and deleted the 250 KT speed restriction at RBEKA in the FMC. Approximately one minute later and climbing through 6000/250 knots; ATC queried us regarding our direction of flight. We replied we were in the turn to BEDRK from RONII. The aircraft was in NAV and as it appeared to us; navigating properly with RONII the active waypoint. However; we did notice the FMC generated route displayed a considerable turn leading RONII to BEDRK. ATC advised our turn was too early and RONII was still 4 nm ahead. We were then given instructions to fly an assigned heading before eventually given direct CADIT. We complied and continued the flight uneventfully. I believe the deletion of the speed restriction at RBEKA in the FMC may have caused the FMC to over compensate and excessively lead the turn to BEDRK; anticipating an acceleration to 320 kts; although the aircraft was still at 250 kts; as desired.
Data retrieved from NASA's ASRS site 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.