37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 488081 |
Time | |
Date | 200010 |
Day | Sun |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : sju.airport |
State Reference | PR |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier general aviation : personal |
Make Model Name | B737-800 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | ground : taxi ground : preflight ground : parked |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : flight engineer |
Experience | flight time last 90 days : 220 flight time total : 12450 flight time type : 1235 |
ASRS Report | 488081 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : cfi pilot : instrument pilot : multi engine pilot : atp |
Experience | flight time last 90 days : 210 flight time total : 5900 flight time type : 850 |
ASRS Report | 488080 |
Events | |
Anomaly | non adherence : company policies non adherence : far non adherence : published procedure other anomaly other |
Independent Detector | other other : pers 5 |
Resolutory Action | none taken : detected after the fact |
Consequence | other |
Supplementary | |
Problem Areas | Flight Crew Human Performance Company |
Primary Problem | Company |
Narrative:
I arrived by crew van to sju airport with my crew. We proceeded through security and to our gate, a flight to ewr. The flight was correctly marked at the gate and was the only aircraft at any of the company gates. After the crew boarded the aircraft, I reviewed the aircraft and cabin logs and reviewed the paperwork which sju operations had delivered to the aircraft. Everything appeared in order and I signed the release and advised the operations representative on board that the fuel load was ok -- fueling commenced. I then proceeded to the cockpit to check fluid levels and set up for my preflight. We were low on oil so I told the first officer to call operations for maintenance to add oil. I also told him I would personally remind operations after I finished the walkaround. The oil was added and noted in the aircraft log. The rest of the flight to ewr was normal. After arriving home from the airport that day, I was contacted by the chief pilot's office and told that I flew the wrong aircraft to ewr. The aircraft I should have taken was XXX instead of YYY. The chief pilot asked if I saved the paperwork or remembered what aircraft I signed for on the dispatch release. I told him I honestly did not remember, but would review the paperwork the next day when I returned to sju. According to chief pilot, the caterers in ewr discovered it was the wrong aircraft and reported it to system control. On oct/mon/00 I reviewed the paperwork in sju and I had signed for aircraft XXX vice YYY. I then visited with the station manager and reviewed the previous day's events. He said there had recently been a schedule change which switched the last aircraft that arrives in sju on saturdays to leave the next day to iah vice departing to ewr. This change probably triggered the chain of events leading to the wrong aircraft at the gate the morning we departed for ewr. In the cockpit, the only problem we encountered was the FMC was trying to upload the flight to iah instead of to ewr which the first officer manually overrode. I have had problems before uploading flts from the islands. We were also having trouble with our printer, but thought it was related to the FMC upload problem. I cannot honestly remember if I checked the aircraft number during my cockpit checks or during the review of the accuload, but I do know that the flight was operated safely from sju to ewr. Recommendation: I will always verify the aircraft number with the dispatch release, aircraft logbook and during the review of the accuload. Supplemental information from acn 488080: in my opinion, this error would have been caught if the flight crew, dispatch, and the operations manager in sju had been more vigilant in doublechking the paperwork for the flight and matching that with the actual aircraft number flown.
Original NASA ASRS Text
Title: THE AIRPLANE FLOWN IS DIFFERENT FROM THE ONE DISPATCHED.
Narrative: I ARRIVED BY CREW VAN TO SJU ARPT WITH MY CREW. WE PROCEEDED THROUGH SECURITY AND TO OUR GATE, A FLT TO EWR. THE FLT WAS CORRECTLY MARKED AT THE GATE AND WAS THE ONLY ACFT AT ANY OF THE COMPANY GATES. AFTER THE CREW BOARDED THE ACFT, I REVIEWED THE ACFT AND CABIN LOGS AND REVIEWED THE PAPERWORK WHICH SJU OPS HAD DELIVERED TO THE ACFT. EVERYTHING APPEARED IN ORDER AND I SIGNED THE RELEASE AND ADVISED THE OPS REPRESENTATIVE ON BOARD THAT THE FUEL LOAD WAS OK -- FUELING COMMENCED. I THEN PROCEEDED TO THE COCKPIT TO CHK FLUID LEVELS AND SET UP FOR MY PREFLT. WE WERE LOW ON OIL SO I TOLD THE FO TO CALL OPS FOR MAINT TO ADD OIL. I ALSO TOLD HIM I WOULD PERSONALLY REMIND OPS AFTER I FINISHED THE WALKAROUND. THE OIL WAS ADDED AND NOTED IN THE ACFT LOG. THE REST OF THE FLT TO EWR WAS NORMAL. AFTER ARRIVING HOME FROM THE ARPT THAT DAY, I WAS CONTACTED BY THE CHIEF PLT'S OFFICE AND TOLD THAT I FLEW THE WRONG ACFT TO EWR. THE ACFT I SHOULD HAVE TAKEN WAS XXX INSTEAD OF YYY. THE CHIEF PLT ASKED IF I SAVED THE PAPERWORK OR REMEMBERED WHAT ACFT I SIGNED FOR ON THE DISPATCH RELEASE. I TOLD HIM I HONESTLY DID NOT REMEMBER, BUT WOULD REVIEW THE PAPERWORK THE NEXT DAY WHEN I RETURNED TO SJU. ACCORDING TO CHIEF PLT, THE CATERERS IN EWR DISCOVERED IT WAS THE WRONG ACFT AND RPTED IT TO SYS CTL. ON OCT/MON/00 I REVIEWED THE PAPERWORK IN SJU AND I HAD SIGNED FOR ACFT XXX VICE YYY. I THEN VISITED WITH THE STATION MGR AND REVIEWED THE PREVIOUS DAY'S EVENTS. HE SAID THERE HAD RECENTLY BEEN A SCHEDULE CHANGE WHICH SWITCHED THE LAST ACFT THAT ARRIVES IN SJU ON SATURDAYS TO LEAVE THE NEXT DAY TO IAH VICE DEPARTING TO EWR. THIS CHANGE PROBABLY TRIGGERED THE CHAIN OF EVENTS LEADING TO THE WRONG ACFT AT THE GATE THE MORNING WE DEPARTED FOR EWR. IN THE COCKPIT, THE ONLY PROB WE ENCOUNTERED WAS THE FMC WAS TRYING TO UPLOAD THE FLT TO IAH INSTEAD OF TO EWR WHICH THE FO MANUALLY OVERRODE. I HAVE HAD PROBS BEFORE UPLOADING FLTS FROM THE ISLANDS. WE WERE ALSO HAVING TROUBLE WITH OUR PRINTER, BUT THOUGHT IT WAS RELATED TO THE FMC UPLOAD PROB. I CANNOT HONESTLY REMEMBER IF I CHKED THE ACFT NUMBER DURING MY COCKPIT CHKS OR DURING THE REVIEW OF THE ACCULOAD, BUT I DO KNOW THAT THE FLT WAS OPERATED SAFELY FROM SJU TO EWR. RECOMMENDATION: I WILL ALWAYS VERIFY THE ACFT NUMBER WITH THE DISPATCH RELEASE, ACFT LOGBOOK AND DURING THE REVIEW OF THE ACCULOAD. SUPPLEMENTAL INFO FROM ACN 488080: IN MY OPINION, THIS ERROR WOULD HAVE BEEN CAUGHT IF THE FLC, DISPATCH, AND THE OPS MGR IN SJU HAD BEEN MORE VIGILANT IN DOUBLECHKING THE PAPERWORK FOR THE FLT AND MATCHING THAT WITH THE ACTUAL ACFT NUMBER FLOWN.
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.