 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A pilot recently returned to the first officer position due to company downsizing, considers himself not sufficiently proficient in his duties. A track deviation was not caught before it happened. He feels his normal backup of the captain was lacking.
| Attributes | |
| ACN | 526900 |
| Time | |
| Date | 200110 |
| Day | Fri |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | navaid : syr.vortac |
| State Reference | NY |
| Altitude | msl single value : 24000 |
| Environment | |
| Flight Conditions | IMC |
| Light | Dusk |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | Do 328 TP (Turboprop) |
| Flight Phase | cruise : level |
| Route In Use | enroute : direct |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : multi engine pilot : instrument pilot : atp pilot : cfi |
| Experience | flight time last 90 days : 150 flight time total : 3000 flight time type : 2000 |
| ASRS Report | 526900 |
| Events | |
| Anomaly | non adherence : clearance non adherence : company policies other spatial deviation |
| Resolutory Action | none taken : detected after the fact |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
Narrative:
Clearance for yul was jaydee departure V282 to bugsy then as filed. Filed flight plan was yul-nippy-syr-bfd.... After bugsy we went to syracuse, bypassing nippy. I was the one who found our error simply by accident. I saw nippy on the flight plan and did not remember it. Per company operations, it is the responsibility of whoever receives the clearance to verify the FMS flight plan. In this, as in most cases, the captain did this. He told me he checked it. I normally back the captain up, however, due to recent company layoffs, I am back in the right seat for only the second leg and am fairly well behind on first officer duties. Not an excuse, just a possible cause. This event did not cause any conflicts with other traffic.
Original NASA ASRS Text
Title: A PLT RECENTLY RETURNED TO THE FO POS DUE TO COMPANY DOWNSIZING, CONSIDERS HIMSELF NOT SUFFICIENTLY PROFICIENT IN HIS DUTIES. A TRACK DEV WAS NOT CAUGHT BEFORE IT HAPPENED. HE FEELS HIS NORMAL BACKUP OF THE CAPT WAS LACKING.
Narrative: CLRNC FOR YUL WAS JAYDEE DEP V282 TO BUGSY THEN AS FILED. FILED FLT PLAN WAS YUL-NIPPY-SYR-BFD.... AFTER BUGSY WE WENT TO SYRACUSE, BYPASSING NIPPY. I WAS THE ONE WHO FOUND OUR ERROR SIMPLY BY ACCIDENT. I SAW NIPPY ON THE FLT PLAN AND DID NOT REMEMBER IT. PER COMPANY OPS, IT IS THE RESPONSIBILITY OF WHOEVER RECEIVES THE CLRNC TO VERIFY THE FMS FLT PLAN. IN THIS, AS IN MOST CASES, THE CAPT DID THIS. HE TOLD ME HE CHKED IT. I NORMALLY BACK THE CAPT UP, HOWEVER, DUE TO RECENT COMPANY LAYOFFS, I AM BACK IN THE R SEAT FOR ONLY THE SECOND LEG AND AM FAIRLY WELL BEHIND ON FO DUTIES. NOT AN EXCUSE, JUST A POSSIBLE CAUSE. THIS EVENT DID NOT CAUSE ANY CONFLICTS WITH OTHER TFC.
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.