 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier first officer and tracon controller reported a missed crossing restriction on the DRMMM1 arrival into atl.
| Attributes | |
| ACN | 1406417 |
| Time | |
| Date | 201612 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ATL.Airport |
| State Reference | GA |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Medium Large Transport |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | STAR DRMMM1 |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 5 |
| Events | |
| Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Overshoot Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Narrative:
We planned for a descend via on the drmmm 1 for runway 8L. After being cleared to descend via the drmmm we were assigned 9R. The captain had already established a descent rate to comply with the 9000 feet hard altitude for 8L. The new hard altitude for 9R was 10;000 feet. We both identified this and set the new altitude in the altitude alerter. I set out changing the approach and verifying the new altitude restrictions; frequency changes for the precision runway monitor (prm); and minimums. After I finished I noticed we were over a crossing restriction of at or above 13;000 feet but our altitude was 11;000 feet. I brought this to the attention of the captain. We did not descend below the hard altitude. The approach continued without further incident.threats: briefing the runway before it was assigned.errors: continuing descending on same trajectory after new clearance received. Did not sufficiently monitor cross check. Missing a crossing constraint.I have to keep monitoring even when setting up for a descent and approach at the last minute and ensure the flight path is adjusted appropriately when a new clearance is received before going heads down.
Original NASA ASRS Text
Title: Air carrier First Officer and Tracon Controller reported a missed crossing restriction on the DRMMM1 arrival into ATL.
Narrative: We planned for a descend via on the DRMMM 1 for Runway 8L. After being cleared to descend via the DRMMM we were assigned 9R. The captain had already established a descent rate to comply with the 9000 feet hard altitude for 8L. The new hard altitude for 9R was 10;000 feet. We both identified this and set the new altitude in the altitude alerter. I set out changing the approach and verifying the new altitude restrictions; frequency changes for the Precision Runway Monitor (PRM); and Minimums. After I finished I noticed we were over a crossing restriction of at or above 13;000 feet but our altitude was 11;000 feet. I brought this to the attention of the captain. We did not descend below the hard altitude. The approach continued without further incident.Threats: Briefing the runway before it was assigned.Errors: Continuing descending on same trajectory after new clearance received. Did not sufficiently monitor cross check. Missing a crossing constraint.I have to keep monitoring even when setting up for a descent and approach at the last minute and ensure the flight path is adjusted appropriately when a new clearance is received before going heads down.
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.