37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 167080 |
Time | |
Date | 199101 |
Day | Wed |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : sju |
State Reference | PR |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport |
Navigation In Use | Other |
Flight Phase | ground : preflight |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : commercial |
Experience | flight time last 90 days : 180 flight time total : 15370 flight time type : 3500 |
ASRS Report | 167080 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : published procedure |
Independent Detector | other flight crewa |
Resolutory Action | none taken : anomaly accepted |
Consequence | Other |
Supplementary | |
Air Traffic Incident | other |
Narrative:
Received load closeout via ACARS showing 109 passenger. Actual count was 108 plus 2 lap children. Requested confirmation via voice from load control. Load control confirmed 3 different times that proper count was 107 plus 2 lap children. Each time, we confirmed the actual count was higher but did not disclose exact number. After the third exchange of information with load control, I suggested they notify dispatch and local security coordination of a possible problem. Finally, due to pleading by load control and in the interest of expediting a solution, I gave our actual count of 1 additional passenger. Within mins, we received response from load control that extra passenger was through passenger from grenada and load inferred it was normal not to count through passenger. (Note also that passenger had to deplane through customs in sju). I challenged the inference but accepted the information as accurate and proceeded. After takeoff I had second thoughts, called load control and requested name and seat number of through passenger. We were within radio range for at least 15 more mins but load control was unable to deliver the requested information. Later during flight I phone patched dispatch and requested they obtain passenger name and seat number. Dispatcher responded approximately 20 mins later via ACARS that passenger was ms kh in seat 23C. I had F/a check passenger in seat 23C. It was a gentleman; his name was not hood. Within the last 3 yrs, I have attended several required security training classes at the air carrier flight academy. During at least one of those classes, the very specific point was made that the carribean could be an easy entry point for terrorists to the mainland. I contend that more concern be given regarding accurate passenger counts and specifically, I suggest that all carribean flts warrant an actual passenger count and in reality this count should be required prior to takeoff.
Original NASA ASRS Text
Title: ACR PIC COMPLAINS OF INACCURATE PASSENGER COUNT FROM LOAD CONTROL PRIOR TO FLT DEP. DID NOT AGREE WITH ACTUAL ACFT COUNT.
Narrative: RECEIVED LOAD CLOSEOUT VIA ACARS SHOWING 109 PAX. ACTUAL COUNT WAS 108 PLUS 2 LAP CHILDREN. REQUESTED CONFIRMATION VIA VOICE FROM LOAD CTL. LOAD CTL CONFIRMED 3 DIFFERENT TIMES THAT PROPER COUNT WAS 107 PLUS 2 LAP CHILDREN. EACH TIME, WE CONFIRMED THE ACTUAL COUNT WAS HIGHER BUT DID NOT DISCLOSE EXACT NUMBER. AFTER THE THIRD EXCHANGE OF INFO WITH LOAD CTL, I SUGGESTED THEY NOTIFY DISPATCH AND LCL SECURITY COORD OF A POSSIBLE PROB. FINALLY, DUE TO PLEADING BY LOAD CTL AND IN THE INTEREST OF EXPEDITING A SOLUTION, I GAVE OUR ACTUAL COUNT OF 1 ADDITIONAL PAX. WITHIN MINS, WE RECEIVED RESPONSE FROM LOAD CTL THAT EXTRA PAX WAS THROUGH PAX FROM GRENADA AND LOAD INFERRED IT WAS NORMAL NOT TO COUNT THROUGH PAX. (NOTE ALSO THAT PAX HAD TO DEPLANE THROUGH CUSTOMS IN SJU). I CHALLENGED THE INFERENCE BUT ACCEPTED THE INFO AS ACCURATE AND PROCEEDED. AFTER TKOF I HAD SEC THOUGHTS, CALLED LOAD CTL AND REQUESTED NAME AND SEAT NUMBER OF THROUGH PAX. WE WERE WITHIN RADIO RANGE FOR AT LEAST 15 MORE MINS BUT LOAD CTL WAS UNABLE TO DELIVER THE REQUESTED INFO. LATER DURING FLT I PHONE PATCHED DISPATCH AND REQUESTED THEY OBTAIN PAX NAME AND SEAT NUMBER. DISPATCHER RESPONDED APPROX 20 MINS LATER VIA ACARS THAT PAX WAS MS KH IN SEAT 23C. I HAD F/A CHK PAX IN SEAT 23C. IT WAS A GENTLEMAN; HIS NAME WAS NOT HOOD. WITHIN THE LAST 3 YRS, I HAVE ATTENDED SEVERAL REQUIRED SECURITY TRNING CLASSES AT THE ACR FLT ACADEMY. DURING AT LEAST ONE OF THOSE CLASSES, THE VERY SPECIFIC POINT WAS MADE THAT THE CARRIBEAN COULD BE AN EASY ENTRY POINT FOR TERRORISTS TO THE MAINLAND. I CONTEND THAT MORE CONCERN BE GIVEN REGARDING ACCURATE PAX COUNTS AND SPECIFICALLY, I SUGGEST THAT ALL CARRIBEAN FLTS WARRANT AN ACTUAL PAX COUNT AND IN REALITY THIS COUNT SHOULD BE REQUIRED PRIOR TO TKOF.
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.