37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 568056 |
Time | |
Date | 200212 |
Day | Wed |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | navaid : esl.vortac |
State Reference | WV |
Altitude | msl bound lower : 29000 msl bound upper : 30000 |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | artcc : zdc.artcc |
Operator | common carrier : air carrier |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other other vortac |
Flight Phase | descent : intermediate altitude |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : cfi pilot : commercial pilot : instrument pilot : multi engine |
Experience | flight time last 90 days : 240 flight time total : 4500 flight time type : 2000 |
ASRS Report | 568056 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | altitude deviation : undershoot altitude deviation : crossing restriction not met other anomaly other |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | none taken : anomaly accepted |
Supplementary | |
Problem Areas | Flight Crew Human Performance Company |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We were given a crossing restr of 60 NM west of esl at 290 degrees. I built a waypoint for the captain (PF) and entered the altitude of 290 degrees. He was pulling out approach charts, while I was building the point in the flight plan. When he was back heads up, I told him what I had done. He was very clear he didn't appreciate what I had done, doesn't use VNAV, and then erased the point I built. He could have used the point as a reference without using VNAV. We missed the crossing by 1000 ft without controller comment. At 60 NM from esl, the captain reacted as though he then realized he'd missed it, so I didn't make mention of it. I wasn't watching his descent while I was preparing for the approach. I should have watched the descent more closely, especially since I was flying with a pilot that didn't use the full length of the automation, creating a somewhat nonstandard operation. I was pretty fatigued, contributing to the problem. I didn't verify with the captain that he recognized that we missed the crossing restr. This has been a good lesson with regard to the need for me to be more assertive.
Original NASA ASRS Text
Title: A320 CAPT DID NOT COMPLY WITH AN ATC ISSUED XING RESTR IN ZDC CLASS A.
Narrative: WE WERE GIVEN A XING RESTR OF 60 NM W OF ESL AT 290 DEGS. I BUILT A WAYPOINT FOR THE CAPT (PF) AND ENTERED THE ALT OF 290 DEGS. HE WAS PULLING OUT APCH CHARTS, WHILE I WAS BUILDING THE POINT IN THE FLT PLAN. WHEN HE WAS BACK HEADS UP, I TOLD HIM WHAT I HAD DONE. HE WAS VERY CLR HE DIDN'T APPRECIATE WHAT I HAD DONE, DOESN'T USE VNAV, AND THEN ERASED THE POINT I BUILT. HE COULD HAVE USED THE POINT AS A REF WITHOUT USING VNAV. WE MISSED THE XING BY 1000 FT WITHOUT CTLR COMMENT. AT 60 NM FROM ESL, THE CAPT REACTED AS THOUGH HE THEN REALIZED HE'D MISSED IT, SO I DIDN'T MAKE MENTION OF IT. I WASN'T WATCHING HIS DSCNT WHILE I WAS PREPARING FOR THE APCH. I SHOULD HAVE WATCHED THE DSCNT MORE CLOSELY, ESPECIALLY SINCE I WAS FLYING WITH A PLT THAT DIDN'T USE THE FULL LENGTH OF THE AUTOMATION, CREATING A SOMEWHAT NONSTANDARD OP. I WAS PRETTY FATIGUED, CONTRIBUTING TO THE PROB. I DIDN'T VERIFY WITH THE CAPT THAT HE RECOGNIZED THAT WE MISSED THE XING RESTR. THIS HAS BEEN A GOOD LESSON WITH REGARD TO THE NEED FOR ME TO BE MORE ASSERTIVE.
Data retrieved from NASA's ASRS site as of July 2007 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.