|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||0001 To 0600|
|Locale Reference||airport : mia|
|Altitude||agl bound lower : 0|
agl bound upper : 0
|Operator||common carrier : air carrier|
|Make Model Name||Medium Large Transport, Low Wing, 2 Turbojet Eng|
|Navigation In Use||Other |
|Flight Phase||climbout : takeoff|
ground : preflight
|Affiliation||company : air carrier|
|Qualification||other other : other|
|Affiliation||company : air carrier|
|Function||flight crew : captain|
oversight : pic
|Qualification||pilot : atp|
|Anomaly||non adherence : far|
other anomaly other
|Independent Detector||other other : unspecified|
|Resolutory Action||none taken : detected after the fact|
|Air Traffic Incident||other|
I was dispatcher handling mexico city arrs. Released scheduled flight mia to mex in medium large transport equipment. Nothing about release stood out -- was normal, routine. Flight was released across gulf and flight was flown with no apparent problems. Unfortunately, no one noticed until after the flight that it was not an overwater equipped medium large transport. Domestic aircraft rted on flight in error, I believe. If rted intentionally by rters, no notice was given. Only way to tell it was wrong medium large transport was to notice plane number in flight planning format. Normally, a 19XX series medium large transport this time was a 14XX series medium large transport. This routing of domestic medium large transport has happened before and I've caught it, but I missed it this time. The flight planning system is entirely computerized but unfortunately, can't differentiate between domestic and overwater aircraft. We use international flight plan format for mexico flts but no computer program to avoid this happening. A computer sophisticated enough to do all our flight planning should be able to be programmed to avoid this. This was supposed to be a day off, but I volunteered to work this midnight shift for future time off. Maybe because it was a single mid-shift in the middle of my days off, and maybe because I was up all day and only had a couple of hours of sleep before going in, maybe at am in the morning I wasn't as alert as 'normal.' I'll be watching those aircraft numbers more closely.
Original NASA ASRS Text
Title: DISPATCHER DISCOVERS ACFT SENT ACROSS GULF WAS NOT OVERWATER EQUIPPED.
Narrative: I WAS DISPATCHER HANDLING MEXICO CITY ARRS. RELEASED SCHEDULED FLT MIA TO MEX IN MLG EQUIP. NOTHING ABOUT RELEASE STOOD OUT -- WAS NORMAL, ROUTINE. FLT WAS RELEASED ACROSS GULF AND FLT WAS FLOWN WITH NO APPARENT PROBLEMS. UNFORTUNATELY, NO ONE NOTICED UNTIL AFTER THE FLT THAT IT WAS NOT AN OVERWATER EQUIPPED MLG. DOMESTIC ACFT RTED ON FLT IN ERROR, I BELIEVE. IF RTED INTENTIONALLY BY RTERS, NO NOTICE WAS GIVEN. ONLY WAY TO TELL IT WAS WRONG MLG WAS TO NOTICE PLANE NUMBER IN FLT PLANNING FORMAT. NORMALLY, A 19XX SERIES MLG THIS TIME WAS A 14XX SERIES MLG. THIS ROUTING OF DOMESTIC MLG HAS HAPPENED BEFORE AND I'VE CAUGHT IT, BUT I MISSED IT THIS TIME. THE FLT PLANNING SYS IS ENTIRELY COMPUTERIZED BUT UNFORTUNATELY, CAN'T DIFFERENTIATE BTWN DOMESTIC AND OVERWATER ACFT. WE USE INTL FLT PLAN FORMAT FOR MEXICO FLTS BUT NO COMPUTER PROGRAM TO AVOID THIS HAPPENING. A COMPUTER SOPHISTICATED ENOUGH TO DO ALL OUR FLT PLANNING SHOULD BE ABLE TO BE PROGRAMMED TO AVOID THIS. THIS WAS SUPPOSED TO BE A DAY OFF, BUT I VOLUNTEERED TO WORK THIS MIDNIGHT SHIFT FOR FUTURE TIME OFF. MAYBE BECAUSE IT WAS A SINGLE MID-SHIFT IN THE MIDDLE OF MY DAYS OFF, AND MAYBE BECAUSE I WAS UP ALL DAY AND ONLY HAD A COUPLE OF HRS OF SLEEP BEFORE GOING IN, MAYBE AT AM IN THE MORNING I WASN'T AS ALERT AS 'NORMAL.' I'LL BE WATCHING THOSE ACFT NUMBERS MORE CLOSELY.
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.