37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1047918 |
Time | |
Date | 201211 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | DTW.Airport |
State Reference | MI |
Environment | |
Flight Conditions | VMC |
Light | Dawn |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | STAR POLAR3 |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
ATC cleared us to cross munky intersection on the POLAR3 arrival into dtw at the expected; planned; and standard FL230. Our altitude was FL270. The captain and I were talking. Munky fix started flashing indicating station passage. I recorded the fuel on the dispatch release. I then realized I had not begun descending. I told the captain I had forgotten to descend and selected power idle; full spoilers; vertical speed down 3;500 FPM. As I began descending; ATC told us to change to cleveland center. We leveled at FL230 5 to 6 miles after munky fix. The threats were the crossing restriction on a quiet morning and the conversation in the flight deck to keep our minds active. My error as the flying pilot was not initiating the descent when assigned by ATC; not perceiving the snow flake or 3 degree guidance in my scan; and the captain not catching my error in his monitoring cross check. The undesired aircraft state was being 4;000 ft too high above our crossing fix.I should; as I usually do; begin descending immediately when assigned crossing fixes. I should; if planning a 3 degree descent; ask the captain to remind me if he sees me not acting at the 3 degree descent point. I should be aware that conversation; though good in keeping the mind active; also leads to distraction from flying responsibilities especially during low levels of activity; such as at cruise.
Original NASA ASRS Text
Title: Air Carrier flight crew failed to initiate descent in time to make assigned crossing restriction on the POLAR3 arrival into DTW.
Narrative: ATC cleared us to cross MUNKY Intersection on the POLAR3 arrival into DTW at the expected; planned; and standard FL230. Our altitude was FL270. The Captain and I were talking. MUNKY fix started flashing indicating station passage. I recorded the fuel on the dispatch release. I then realized I had not begun descending. I told the Captain I had forgotten to descend and selected power idle; full spoilers; vertical speed down 3;500 FPM. As I began descending; ATC told us to change to Cleveland Center. We leveled at FL230 5 to 6 miles after MUNKY fix. The threats were the crossing restriction on a quiet morning and the conversation in the flight deck to keep our minds active. My error as the flying pilot was not initiating the descent when assigned by ATC; not perceiving the snow flake or 3 degree guidance in my scan; and the Captain not catching my error in his monitoring cross check. The undesired aircraft state was being 4;000 FT too high above our crossing fix.I should; as I usually do; begin descending immediately when assigned crossing fixes. I should; if planning a 3 degree descent; ask the Captain to remind me if he sees me not acting at the 3 degree descent point. I should be aware that conversation; though good in keeping the mind active; also leads to distraction from flying responsibilities especially during low levels of activity; such as at cruise.
Data retrieved from NASA's ASRS site as of July 2013 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.