Entry Codes

NOTE (1): Non-IATA Cargo-IMP (International Air Transport Association Cargo Interchange Message Procedures) special characters > : # , & “ = * and IATA Cargo-IMP separator characters / - have been removed from the 40 character alphanumeric error message text explanation.

000      COMPLETE TRANSACTION REJECTED

            Reason:    This message indicates that the entire transaction has been rejected by Air AMS due to one or more fatal errors listed after error code 000.  This error code indicates that NONE of the manifest data received within the input message processed was accepted by Air AMS for update of an Air Waybill record.

            Note:        [Air AMS Carriers]: A Freight Error Report (FER) message referencing Shipment Identification (Air Waybill number) ‘000-yyyymmdd’ (derived from the scheduled arrival date of the flight identification) is used by Air AMS to report fatal errors found in Message Line Identifier DEP detail received via Flight Departure Message (FDM).  An FDM is not valid if received by Air AMS- prior to the GMT liftoff date and time reported in the FDM Departure Detail. Freight Status Notification (FSN) message(s) referencing complete air waybill manifest data are not transmitted by AMS until a valid flight departure data is received from the importing AMS-Air carrier, or CBP staff update the flight record with actual date and time of arrival in U.S.

001      INVALID INPUT TRANSACTION TYPE                                            {Reference: SMI}

            Reason:    Message must have a valid message type.  Fatal error.  Valid Air AMS input message types are FRI, FRC, FRX, FDM, FSN, FXI, FXC, FXX and FSQ.

            Action:      This error should be prevented by user data validation prior to transmission.

            Note:         An IATA Cargo-IMP Standard Message Identifier PDM [possible duplicate message] inserted by SITA or ARINC networks will be ignored by Air AMS processing. 

002      INVALID CARGO CONTROL LINE FORMAT                              {Reference: CCL}

            Reason:    The Cargo Control Location line cannot contain non-alpha-numeric characters or imbedded spaces and may not be less than 5 or greater than 7 characters. Ref. Error Code 018, 021, 022.  Fatal Error, Message Types FRI, FRC, FRX, FSN, FXI, FXC, FXX, FSQ.

            Action:      This error should be prevented by user data validation prior to transmission.

003      INVALID SHIPMENT ID LINE FORMAT                                       {Reference: SHP}

            Reason:   Minimum Air AMS Shipment Identification format is comprised of a 3-character Air Waybill Prefix code, a hyphen, and an 8-character numeric Air Waybill Serial Number.  If the air waybill was issued to identify a consolidation of individual shipments further identified to the House bill level, the Air Waybill Serial Number must be followed by a hyphen and the consolidation indicator ‘M’ to establish an Air AMS MASTER AWB manifest record.  A consolidated shipment is referenced by a House bill identifier of up to 12-alpha-numeric characters, with no imbedded spaces, preceded by a hyphen by the Air Waybill Prefix and Air Waybill serial number, separated by a hyphen.  Fatal Error, Message Types FRI, FRC, FRX, FSN, FXI, FXC, FXX, FSQ.

            Action:      This error should be prevented by user data validation prior to transmission.

004      INVALID ARRIVAL LINE FORMAT                                              {Reference: ARR}

            Reason:    Line identifier ARR must be followed a forward slant ‘/’ character and must include mandatory data elements. Include part-arrival shipment data when reporting actual boarded piece count and weight less than Total waybill piece count and weight reported in WBL line. Omit boarded piece count and boarded weight data elements from Arrival detail when canceling a part-arrival manifest record via FRX (or FXX if express shipment). Fatal Error, Message Types FRI, FRC, FRX, FSN, FXI, FXC, FXX.

            Action:      This error should be prevented by user data validation prior to transmission.

005      INVALID AMENDMENT REASON LINE FORMAT                      {Reference: RFA}

            Reason:    Reason For Amendment codes 1 through 9 must be reported with a leading zero. For example: ‘RFA/03’ is valid, however ‘RFA/3’ is invalid.  Fatal Error, Message Types FRC, FRX, FXC, FXX.

            Action:      This error should be prevented by user data validation prior to transmission.

006      INVALID AIRLINE STATUS LINE FORMAT                                  {Reference: ASN}

            Reason:    The Airline Status Notification code must be reported after the line identifier ‘ASN’ without a preceding forward slant ‘/’ separator character within a Freight Status Notification message sent to Air AMS.  Fatal Error, Message Type: FSN.

            Action:      This error should be prevented by user data validation prior to transmission.

007      INVALID DEPARTURE LINE FORMAT                                          {Reference: DEP}

            Reason:    Flight Departure Message line identifier ‘DEP’ did not contain the required forward slant ‘/’ separator following the line identifier ‘DEP’ preceding importing flight number, preceding scheduled date of arrival at first U.S. port; and preceding GMT Liftoff Date and Time.  Fatal Error, Message Type: FDM.

            Action:      This error should be prevented by user data validation prior to transmission.

008      ARRIVAL LINE NOT SPECIFIED                                                      {Reference: ARR}

            Reason:    Importing flight detail reported in Line Identifier ‘ARR’ is required within AMS-Air message(s) when manifest data refers to Simple (non-consolidated) and Master (consolidated) air waybill information provided by the incoming air carrier and is also required to amend House air waybill information in the event the incoming air carrier reported the shipment as arriving via more than one flight. Fatal Error, Message Types FRI, FRC, FRX, FSN, FXI, FXC, FXX.

            Action:      The arriving flight detail required for amendment of part arrival shipments identified by a house air waybill is included in the Freight Status Condition (FSC) message (following Message Line Identifier (FSC/10) sent to the Air AMS participant which provided initial house air waybill information in advance of the incoming air carrier and to the Air AMS participant indicated by the incoming air carrier as electing to provide house shipment information associated to the Master AWB.

009      UNIDENTIFIED LINE FRAGMENT REJECTED

            Reason:    A message line was not properly terminated.  This error code is also caused by the inclusion of message line termination characters other than the IATA Cargo Interline Message Procedure standard ‘Carriage Return’ and ‘Line Feed’ characters.  Please report incidence of this error code immediately to your software vendor and advise your Air AMS Client Representative.  Fatal error, ALL Air AMS Message Types.

            Action:      This error should be prevented by user data validation prior to transmission.

010      MESSAGE LINES IN INCORRECT SEQUENCE     {Reference: FRI/FXI-FRC/FXC}

            Reason:    The sequence of message lines is specific to the Air AMS Message Type. Note: Air AMS AWB Shipper or Consignee manifest data must be provided with the respective Line Identifier and three continuation lines comprising the address data elements.  Fatal error, ALL Message Types.

            Action:      This error should be prevented by user data validation prior to transmission.

011      ORIGINATOR NOT AUTH TO XMIT FOR CARRIER                   {Reference: AGT}

            Reason:    (1) Manifest data was received from other than the importing Air AMS carrier’s Air AMS originator address indicated in the Air AMS user record (importing air carrier code and a port code derived from a U.S. airport code referenced by the routing of the shipment).

                              (2) House AWB manifest data was received (with cargo control location and arriving flight detail from other than (1) and/or the Air AMS participant which provided the initial house air waybill information and/or is indicated by the incoming air carrier in Master air waybill information (Message Line Identifier AFT) as the Air AMS participant electing to provide advance house air waybill information directly to CBP.

                              (3) A Flight Departure Message was received from other than an Air AMS originator address indicated in an Air AMS user record found for the importing carrier code referenced in the Departure detail reported within the FDM message.

                              (4) A Freight Status Notification (FSN) message was received from other than the AWB originator, agent (AGT), Onward (In-Bond) Air AMS Carrier or Air AMS carrier, or deconsolidator in custody of the shipment. The Freight Status Condition (FSC) message received by the originator of an FSQ message will indicate a) manifest data on file in Air AMS that must be referenced in subsequent FRC to ensure acceptance by Air AMS, b) the originator of the FSQ has not been nominated as agent for the AWB, or c) an active AWB manifest record was not found, contact the importing Air AMS carrier to request their transmission of initial or amended Master AWB manifest data specifying the Air AMS participant code via Line Identifier AGT.  Fatal Error, Message Types FRI, FRC, FRX, FDM, FSN, FXI, FXC, FXX.

012      TIME LIMIT FOR FRI HAS EXPIRED                                        {Reference: FRI/FXI}

            Reason:    Message Type FRI (Freight Report Inbound) message cannot be used to provide initial AWB manifest data to Air AMS more than four hours from the arrival of the flight as updated by CBP at the landing port.  Fatal Error, Message Types FRI, FXI.

            Action:      Re-transmit the AWB manifest data to Air AMS via Message Type FRC instead of FRI and include a Reason For Amendment code.

Note:        Applies to Message Type FXI received from an Express Consignment Air Carrier more than four hours after arrival of the flight. Provide Express AWB manifest data via FXC and include a Reason For Amendment code.

013      REQUIRED REASON FOR AMENDMENT MISSING                    {Reference: RFA}

            Reason:    Line Identifier RFA and a valid RFA code are required components of FRC, FRX, FXC, FXX Message Types; the RFA line is not required for FRC and FXC messages that are received by CBP less than 4 hours after flight arrival.  Fatal Error, Message Types FRC, FRX, FXC, FXX.

            Action:      This error should be prevented by user data validation prior to transmission.  Re-transmit the FRC, FRX, FXC or FXX message with Line Identifier RFA and include the RFA code that corresponds with the reason for the amendment.

014      CUMULATIVE HOUSE QTYS EXCEEDS MASTER QTY

            Reason:    The cumulative total quantity of House AWB related by Master AWB number and importing flight cannot be greater than the total quantity of the Master AWB. In the case of a split MAWB (Part Shipment), the master boarded quantity may not be exceeded by the sum of its HAWB quantities.  If the house is split then the House AWB boarded quantity is used.  Fatal Error, Message Types FRI, FRC, FXI, FXC.

            Action:      Verify the total piece count reported to Air AMS for the Master AWB does not exceed the cumulative piece count of the House AWB referencing the same arriving flight as the Master AWB.  Typically, this error occurs when Master AWB piece count was reported as the number of skids or ULD (Unit Load Devices) instead of the total number of pieces the consolidation contains, or is said to contain by the shipper/forwarder indicated on the Master AWB.

015      MASTER MAY NOT BE RESET - HOUSE RECEIVED

            Reason:    An Air Waybill reported to Air AMS with the consolidation indicator ‘M’ (Master AWB) cannot be changed to a Simple AWB (a non consolidated shipment without House-level identifier) by an amendment omitting the consolidation indicator ‘M’ once a House AWB is received or the Air AMS Master AWB record was reconciled by transfer detail specifying a non-AMS destination regardless of whether any House AWB manifest data was accepted by Air AMS.  Fatal error, Message Types FRI, FRC, FXI, FXC, and FSN (reporting in-bond arrival of a Master AWB omitting the consolidation indicator).

            Action:      Master and House AWB manifest data accepted by Air AMS must be cancelled before Air AMS will accept IATA AWB manifest data as a Simple AWB without including the consolidation indicator.

016  HOUSE MAY NOT BE RESET - MASTER RECONC’ED

            Reason:    A Simple AWB manifest record that has been reconciled by a transaction indicating entry or in-bond departure data cannot be amended to a Master AWB by inclusion of the consolidation indicator ‘M’ prior to re-manifesting the shipment referencing a House bill number.  Fatal Error, Message Types FRI, FRC, FXI, FXC.

            Action:      The reconciled Simple AWB manifest record must be cancelled without inclusion of the consolidation indicator, (e.g. as a Simple AWB) prior to transmitting amendments to re-manifest the AWB as a Master AWB referencing the consolidation indicator, and to establish a House AWB record associated to the Master AWB number.  The Entry or In-Bond Departure data which previously reconciled the cancelled Simple AWB must be amended to reference the Master and House bill number and reprocessed to reconcile the new House AWB manifest record.

017      HOUSE INVALID AWB NOT DEFINED AS MASTER

            Reason:    Manifest data referencing a shipment identified to the House AWB level cannot be accepted by Air AMS in the event the incoming air carrier reported the associated AWB information to AMS as non-consolidated shipment (without the consolidation identifier), resulting in a simple AWB record.  Fatal error, Message Types FRI, FRC, FXI, FXC.

            Action:      For consolidated shipments:  the incoming air carrier must transmit to CBP the information that is applicable to a master air waybill by including the consolidation indicator.

            Note:         The Air AMS Freight Status Condition (FSC) message sent in response to an FSQ message received referencing a request for AWB routing (FSQ/01) or status (FSQ/02) will include “TXT/MASTER AWB” when the active Air AMS manifest record data references a consolidation.

018      CARGO CONTROL LINE IGNORED                                                 {Reference: CCL}

            Reason:    The Airport of First Arrival in U.S. code or Cargo Terminal Operator code were invalid or mis-formatted (error codes 020, 022, 002).  Fatal error, Message types FRI, FRC, FRX, FSN, FXI, FXC, FXX, FSQ.

019      ARRIVAL LINE IGNORED                                                                 {Reference: ARR}

            Reason:    One or more data elements comprising Arrival detail were invalid or mis-formatted (error codes 004, 021, 029, 030) Fatal error, Message types FRI, FRC, FRX, FSN, FXI, FXC, FXX.

020      INVALID ARRIVAL AIRPORT                                                           {Reference: CCL}

            Reason:    The airport of arrival code does not correspond to an Air AMS Airport code record referencing a CBP port of entry.  Fatal error, Message types FRI, FRC, FRX, FSN, FXI, FXC, FXX, FSQ.

            Action:      This error should be prevented by user data validation prior to transmission. Verify the airport code is listed in Appendix A of this document, U.S. Domestic Airports and/or the IATA Coding directory. The IATA Location Identifier must reference an airport (not a Metropolitan Area, e.g., NYC or CHI).  If the airport is located in the U.S. and within a CBP port of entry, please advise your Client Representative.

021      INVALID CARRIER CODE                                                                 {Reference: ARR}

            Reason:    The importing air carrier code reported in Arrival detail or Departure detail was not found by Air AMS in the ACS carrier database (2-character carrier code abbreviation IATA-issued Airline Designator or 3-alpha character ICAO-issued carrier code or CBP issued 3-character carrier code for air carriers which have not obtained an ICAO-approved code. Fatal Error, Message types FRI, FRC, FRX, FDM, FSN, FXI, FXC, FXX.

            Note:         To accommodate the IATA conversion from the 2-character airline designator to the approved ICAO three-letter Airline Designator air carrier code (ref. IATA Coding Directory, Section 2, 1.2.2, 1.2.3), Air AMS cannot validate Arrival detail (Line Identifier ARR) or Departure detail (Line Identifier DEP) when a 2-character airline designator ends with a number.

            Action:      This error should be prevented by user data validation prior to transmission. Verify the code with the current IATA Coding directory.

022      INVALID CARGO TERMINAL OPERATOR ID                               {Reference: CCL}

            Reason:    The code provided as Cargo Terminal Operator is other than a 2-character IATA-issued airline designator, 3-character air carrier code (see Error code 021) or bonded cargo facility (FIRMS) code (format: annn).  Fatal Error, Message Types: FRI, FRC, FRX, FXI, FXC, FXX, FSN, FSQ.

            Action:      This error should be prevented by user data validation prior to transmission.

023      INVALID AIR WAYBILL NUMBER PREFIX                                  {Reference: AWB}

            Reason:    The AWB Prefix IATA-issued Airline Prefix Code identifying the air carrier issuing the Air Waybill is invalid or was not found in the database.  Fatal Error, Message Types: FRI, FRC, FRX, FXI, FXC, FXX, FSN, FSQ.

            Action:      Verify the Airline Prefix Code with the issuer of the air waybill and/or IATA Airline Coding Directory.

024      INVALID MASTER AIR WAYBILL NUMBER                                {Reference: AWB}

            Reason:   The AWB Serial number must be 8 numeric characters.  Fatal Error, Message Types: FRI, FRC, FRX, FXI, FXC, FXX, FSN, FSQ. See Error Code 003.

            Note:         The 8^th (right-most) unweighted modulus 7 check digit (ref. IATA Cargo-IMP) is validated by Air AMS only when the 11-digit AWB Prefix and Serial number is intended by the importing air carrier for use as an In-bond Control Number in lieu of a CBP Form 7512 serial number.

            Action:      This error should be prevented by user data validation prior to transmission.

025      INVALID HOUSE BILL NUMBER                                                   {Reference: AWB}

            Reason:    The House bill number may contain only alpha-numeric characters and may not be greater than twelve characters in length. Fatal Error, Message Types: FRI, FRC, FRX, FXI, FXC, FXX, FSN, FSQ. See Error Code 003.

            Note:         The single alpha character ‘M’ is interpreted by Air AMS as the Consolidation Indicator identifying a Master AWB that is associated to consolidated shipments further identified by a valid House Bill Number.

            Action:      This error should be prevented by user data validation prior to transmission.

026      INVALID FOREIGN AIRPORT OF ORIGIN CODE                        {Reference: WBL}

            Reason:    The airport code (IATA Location Identifier) provided is invalid. Message Types: FRI, FRC, FXI, FXC.  See Error Code 111.

            Note:         All Waybill detail reported in Line Identifier WBL will be ignored (See Error code 111).  Freight Status Notification (FSN messages) related to CBP transactions referencing the shipment will not be transmitted to the Air AMS participant in custody of the shipment until valid Waybill detail is received by Air AMS.

            Action:      This error should be prevented by user data validation prior to transmission. Verify the code with the IATA Coding directory.  The IATA Location Identifier transmitted as foreign airport of origin corresponding to the airport from which a shipment began its transportation by air to the United States (for example, if a shipment began its transportation from Hong Kong (HKG), and it transits through Narita, Japan (NRT), en route to the United States, the airport of origin is HKG, not NRT)), per CBP regulations.

027      INVALID AIRPORT OF DESTINATION IN WBL LN                     {Reference: CCL}

            Reason:    The Permit-to-Proceed Destination airport code is invalid. All Waybill detail reported in Line Identifier WBL will be ignored (See Error code 111). Freight Status Notification related to transactions referencing the shipment will not be transmitted until valid Waybill detail is received by Air AMS. See Error Code 111. Message Types: FRI, FRC, FXI, FXC

            Action:      This error should be prevented by user data validation prior to transmission. Verify the airport code is listed in Appendix A of this document, CBP Domestic Airports (a U.S. airport located within a CBP port of entry.  Do not report the foreign destination airport in WBL detail as permit-to-proceed destination airport for air cargo arriving from and departing for a foreign country on the same through flight (also referred as Freight Remaining On Board (FROB) shipments), as identified via Air AMS transfer detail indicator ‘R’ (TRN/xxx-R, where ‘xxx’ is the same U.S. airport code indicated as airport of first arrival in the U.S.).

028      DESTINATION APT SAME AS ARRIVAL APT                             {Reference: WBL}

            Reason:    The Permit-to-Proceed (PTP) destination airport code reported in Line Identifier WBL was the same airport code reported as Airport of First Arrival in U.S. See Error Code 111. Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission. Verify both airport codes are different U.S. airports.

029      INVALID SCHEDULED ARRIVAL DATE                                        {Reference: ARR}

            Reason:    The scheduled arrival date must be in DDMMM format (12FEB) however it cannot be earlier than the first day of the month preceding the scheduled arrival of the shipment at the first U.S. port.  Fatal Error, Message Types: FRI, FRC, FRX, FDM, FXI, FXC, FXX, FSN. See Error Code 019.

            Action:      This error should be prevented by user data validation prior to transmission.

            Note:         Manifest data received by Air AMS later than the last day of the month following the scheduled date of arrival at first U.S. port will be rejected referencing this error code.

030      INVALID FLIGHT NUMBER                                                              {Reference: ARR}

            Reason:    Minimum flight number designation must contain 3 numeric characters include leading zeroes when necessary, e.g., ‘007’ is valid, while ‘7’ or ‘07’ are invalid. Fatal Error, Message Types: FRI, FRC, FRX, FDM, FXI, FXC, FXX, FSN. See Error code 019.

            Action:      This error should be prevented by user data validation prior to transmission.

            Note:         The input flight number format as received when the AWB manifest record is established by Air AMS processing of input manifest data will be maintained in subsequent FSN messages transmitted by Air AMS referencing the shipment identification.  The invalid flight number as received will be referenced in the Freight Error Report (FER) message referencing this error code.

031      HOUSE AWB ON FILE - MASTER AWB REQUIRED

            Reason:    Shipment identification received by Air AMS without the consolidation indicator ‘-M’ following the AWB Serial number is rejected referencing this error code when one or more active Air AMS AWB manifest records exist with shipment identification to the House AWB level associated to this Master AWB number and the arriving flight detail.  Fatal Error, Message Types: FRI, FRC, FXI, FXC.

032      MASTER AWB NOT ON FILE

            Note:         This error code is not been verified in use.

033      ORIGINATOR NOT AUTH TO TRANSMIT FDM

            Reason:    A Flight Departure Message was received by Air AMS from other than an Air AMS carrier authorized originating address.

            Note:         This error code is not currently used by Air AMS processing. An FDM received from other than an originating address authorized by the air carrier referenced in the Departure detail will be rejected by Air AMS referencing error codes 000 and 011.

034      SYSTEM ERROR OCCURRED, RESEND MESSAGE

            Reason:    Air AMS detected a database error while processing from the trade.

            Note:         Air AMS detected a database error that it assumes is temporary.  When the message is resubmitted, it should be accepted.

035      INVALID ARRIVE DATE AT APT OF DESTINATN                       {Reference: WBL}

            Reason:    The scheduled date of arrival at airport of destination (Permit-to-Proceed Destination airport) is invalid.  The scheduled Permit-to-Proceed Arrival date must be equal to or later than the scheduled arrival date at the first U.S. port (ref. Line Identifier ARR), but may not be later than seven days after arrival at the first U.S. port.

            Action:      This error should be prevented by user data validation prior to transmission.

036      AIRPORT OF DEST SENT WITH NO ARRIVE DATE                    {Reference: WBL}

            Reason:    Waybill detail reporting a Permit-to-Proceed airport code must include a scheduled date of arrival at the PTP Destination airport.

            Example:  WBL/TPEJFK/T860/L8108/CONSOL (date of arrival at JFK omitted)

            Action:      This error should be prevented by user data validation prior to transmission.

037      MASTER AWB ROUTING APPLIED TO HAWB                             {Reference: WBL}

            Note:         This error code is no longer used by Air AMS since house shipment information received from other than the incoming air carrier in advance of Master AWB information is automatically updated by either the non-split Master AWB routing information or initial House AWB routing detail required to be provided to CBP by the incoming air carrier – when the incoming air carrier elects to transport cargo covered under a single consolidated air waybill on more than one aircraft as a split shipment (19 CFR 122.48a(d)(3), additional cargo information from air carrier, split shipment).

            Action:      None.

038      PTP DESTINATION CANNOT BE CHANGED                                 {Reference: WBL}

            Reason:    WBL detail received attempted to change the PTP data in the master AWB after a house AWB level in-bond transfer has occurred.  The original port of unlading is derived from arrival airport code unless an airport of destination code is specified in MAWB WBL line.

            Note:         This error code has not been implemented.

            Action:      Correct the WBL component and retransmit.

040      BILL DATA ON FILE MUST BE AMENDED BY FRC                   {Reference: [FRI]}

            Reason:    AWB manifest data received via Message Type FRI referencing a) an active Air AMS AWB manifest record with the same arriving flight detail (Line Identifier ARR) or b) advance House shipment information provided by other than the incoming air carrier, must be amended via Message Type FRC reporting a Reason For Amendment (Line Identifier RFA) code.  Fatal Error, Message Type: FRI.

            Note:         This error code was implemented July 29, 2001.

            Action:      Retransmit the shipment information via Message Type FRC (consolidated express house shipment information including Message Line Identifier CED (CBP Entry Detail) required Message Type FXC).

043  ORIGINAL XMIT INVALID - CARRIER AUTOMATED

            Reason:    Initial AWB Manifest data received via FRC message including obsolete Reason for Amendment codes 22 or 23 will be rejected. Amendment codes 22 and 23 are obsolete under current CBP regulations and will be disabled.

044      EXPRESS SHIPMENT INVALID FOR ARRIVAL APT                   {Reference: CCL }

            Reason:    This error indicates the event the airport of first arrival in the U.S. is not defined in Air AMS Express Consignment as a Courier HUB or ECCF. Message Types: FXI, FXC.

            Note:         This error code has not been implemented.

045      WBL DEST AIRPORT INVALID FOR EXPRESS AWB

            Reason:    This error indicates the airport of PTP destination is not defined in Air AMS Express Consignment as a Courier HUB or ECCF. Message Types: FXI, FXC, FXX.

            Note:         This error code has not been implemented.

046      EXPRESS SHIPMENT INVALID TRN DEST

            Reason:    This error indicates the CBP Control Destination airport code (TRN) is not defined in an Air AMS Express Consignment as a Courier HUB or ECCF.  Message Types: FXI, FXC, FXX.

            Note:         This error code has not been implemented.

047      ORIG NOT AUTH FOR EXPRESS SHIPMENTS

            Reason:    Express courier manifest data received via Air AMS Message Types FXI, FXC, and FXX could not be validated with an Air AMS Express Consignment user record referencing the Airport of First Arrival in U.S. or Permit-to-Proceed Destination Airport (if provided in WBL detail) and incoming air carrier code indicated in the arriving flight detail.

051      INVALID LIFTOFF DATE OR TIME                                                  {Reference: DEP}

            Reason:    A Flight Departure Message failed Air AMS validation because the liftoff date or time (reported as GMT in Departure detail) had not occurred by the time (GMT) the FDM message was processed by Air AMS, or the syntax (DDMMMhhmm) is incorrect.  Fatal error.

            Notes:       1) A liftoff date value of three zeroes “000” no longer cancels previously transmitted departure detail and will be rejected by Air AMS similar to flight departure detail transmitted to Air AMS in advance of the actual GMT liftoff date and time of the flight from the foreign airport en route to the U.S.  See example:

                              FDM

                              DEP/JM015/26JAN/26JAN1350

                              Received by Air AMS on 26 JAN 134852 GMT, note that since the reported departure date and time of 26JAN1350 GMT has not elapsed, the air carrier received:

                              FER

                              JM015/26JAN

                              000-20060126-AJM0015

                              ERR/000COMPLETE TRANSACTION REJECTED

                              ERR/051INVALIDED LIFTOFF DATE OR TIME

            Notes:       2) Freight Status Notification (FSN) messages are not transmitted by Air AMS until complete AWB manifest data has been received referencing the shipment identification and either a valid FDM message has been received or CBP has updated the Air AMS flight record with the actual date and time of arrival.  19 CFR 122.48a (b) Time frame for presenting data.  (1) Nearby foreign areas.  In the case of aircraft that depart for the U.S. from any foreign port or place in North America, including locations in Mexico, Central America, South America (from north of the Equator only), the Caribbean and Bermuda, CBP must receive the required cargo information no later than the time of the departure of the aircraft for the United States (the trigger time is no later than the time that wheels are up on the aircraft, and the aircraft is en route directly to the United States).  (2) Other foreign areas.  In the case of aircraft … that depart for the United States from any foreign area other than that specified in paragraph (b)(1) of this section, CBP must received the required cargo information no later than 4 hours prior to the arrival of the aircraft in the United States.

            Action:      This error should be prevented by user data validation prior to transmission. Verify that GMT was used and that the syntax is correct.

061      AIR WAYBILL #NO IN XACTION DOES NOT EXIST                   {Reference: AWB}

            Reason:    The shipment identification received via FRX or FXX message does not reference an active AMS air waybill record (previously cancelled) or previous FER referencing Error code 000 and other fatal error codes were disregarded.  Fatal error.

            Action:      This error should be prevented by user data validation prior to transmission.  Verify an active Air AMS AWB manifest record exists via Message Type FSQ referencing FSQ option 01 (routing) or 02 (status).  The FSC status codes 00 or 01 indicate no active AMS air waybill record exists referencing the shipment identification.

062      XACTION DATA DOES NOT MATCH BILL DATA                       {Reference: ARR}

            Reason:    The Part-Shipment Reference character, A through Z, associated to an arriving flight does not match the Part-Shipment Reference character found in an active or cancelled Air AMS AWB manifest record associated to this arriving flight.  An AWB record in Pending or Eligible for General Order status FSN 1R or 1S may not be cancelled.  Fatal Error, Message Type: FRC or FRX.

            Note:         Air AMS carriers or Deconsolidators which cancel part-shipment AWB manifest data and subsequently re-manifest some portion of the part-arrival AWB referencing the same importing flight must associate the arriving flight to the SAME part-shipment reference character previously associated to this shipment and arriving flight detail.

            Action:      This error should be prevented by user data validation prior to transmission. Verify and correct.
　

071      CARGO LOCATION RECEIVD DOESN’T MATCH BILL              {Reference: CCL}

            Reason:    Manifest data received by Air AMS referencing other than the Airport of First Arrival code and Cargo Terminal Operator code accepted by Air AMS from the incoming air carrier for the Master AWB and arriving flight detail. Fatal Error, Message Types: FRC, FRX, FSN, FXC, FXX.

            Action:     Verify the initial Cargo Control Location line data accepted by Air AMS via Freight Status Query (FSQ) message referencing the shipment identification received in the Freight Error Report (FER) with Line Identifier FSQ/01 (routing). When Freight Status Condition (FSC) referencing a shipment identified to the House bill level indicates no active Air AMS manifest record exists, the initial Cargo Control Location data must match the active Master AWB referencing the arriving flight of the consolidated House level shipment..

            Note (1):   Manifest data initially provided by the importing Air AMS carrier must report the air carrier code, not CBP FIRMS code, as Cargo Terminal Operator in possession of the shipment or Master AWB consolidation upon arrival at the first U.S. port.

            Note (2):   An Air AMS participant nominated as agent by the provider of the original Master AWB manifest data may provide advance house shipment information without cargo control location and arriving flight detail (as updated by respective Master AWB and/or house shipment information required from the incoming air carrier electing to split a consolidation to arrive in the U.S. via more than one flight.  House shipment information that includes cargo control location detail other than provided by the incoming air carrier will be rejected referencing this error code. In the event house shipment information is cancelled, and is subsequently retransmitted referencing an active Master AWB record, the house shipment information must reference the Airport of First Arrival and Cargo Terminal Operator codes received by Air AMS from the incoming air carrier’s Master AWB information.

072      AIR CARRIER CODE RECVD DOESN’T MATCH BILL                {Reference: CCL}

            Reason:    If the importing air carrier code reported in arriving flight detail does not correspond to the importing air carrier in the active Air AMS AWB manifest record, the manifest data is completely rejected.  Fatal Error, Message Types: FRC, FRX, FSN, FXC, FXX.

            Action:      Verify the arriving flight detail accepted by Air AMS via Freight Status Query (FSQ) message referencing the shipment identification received in the Freight Error Report (FER) with Line Identifier FSQ/01 (routing).  When Freight Status Condition (FSC) referencing a shipment identified to the House bill level indicates no active Air AMS manifest record exists, the initial Cargo Control Location line data must match the active Master AWB manifest data initially received and accepted by Air AMS referencing the arriving flight detail of the House level shipment which the authorized Air AMS participant is providing House level manifest detail (e.g., Shipper and Consignee Name and address data to Air AMS).

073      FLIGHT NUMBER RECEIVED DOESN’T MATCH BILL              {Reference: ARR}

            Reason:    The flight number as received is other than the flight number found in either the active Air AMS Master AWB manifest record or related House AWB record(s) updated with the original Master AWB arriving flight detail.  Fatal error, Message Types: FRC, FRX, FSN, FXC, FXX.

            Action:      Verify the arriving flight detail (accepted by Air AMS) via Freight Status Query (FSQ) message referencing the shipment identification received in the Freight Error Report (FER) with Line Identifier FSQ/01 (routing).  When Freight Status Condition (FSC) message referencing a shipment identified to the House bill level indicates no active Air AMS manifest record exists, then arriving flight detail line data initially received by Air AMS referencing a House level shipment must match the active Master AWB arriving flight detail which the authorized Air AMS participant is providing House level manifest detail (e.g., Shipper and Consignee Name and address data to Air AMS).

074      SCHD ARR DATE RECEIVED DOESN’T MATCH BILL               {Reference: ARR}

            Reason:    The scheduled arrival date at first U.S. port as received is other than the scheduled arrival date found in the active Air AMS Master AWB manifest record or related House AWB record(s) updated with the original Master AWB arriving flight detail. Fatal error, Message Types: FRC, FRX, FSN, FXC, FXX.

            Action:      Verify the arriving flight detail accepted by Air AMS via Freight Status Query (FSQ) message referencing the shipment identification received in the Freight Error Report (FER) with Line Identifier FSQ/01 (routing).  When Freight Status Condition (FSC) message referencing a shipment identified to the House bill level indicates no active Air AMS manifest record exists, then arriving flight detail line data initially received by Air AMS referencing a House level shipment must match the active Master AWB arriving flight detail which the authorized Air AMS participant is providing House level manifest detail (e.g., Shipper and Consignee Name and address data to Air AMS).

075      INVALID FSQ STATUS REQUEST                                                     {Reference: FSQ}

            Reason:    The FSQ code provided in Line Identifier FSQ does not correspond to a defined FSQ option.

            Action:      This error should be prevented by user data validation prior to transmission.

081      INVALID AIRLINE STATUS NOTIFICATION CODE                     {Reference: ASN}

            Reason:    The ASN code received by Air AMS via Message Type FSN was other than 3, 4, 6, or 7.  Other codes are obsolete or are yet to be defined.

            Action:      This error should be prevented by user data validation prior to transmission.

084      AIRLINE STATUS NOTIFICATION LINE MISSING                     {Reference: ASN}

            Reason:    An FSN message was transmitted to Air AMS without mandatory Line Identifier ASN and a valid code (see G.O. Status Codes of this appendix).

            Action:      This error should be prevented by user data validation prior to transmission.

086      ENTRY DATA IGNORED FOR FORMAL ENTRY                          {Reference: CED}

            Reason:    Express Consignment manifest data was received with Line Identifier CED when the shipment value reported via Line Identifier CSD as Declared Value for CBP requires (or the Express AWB record already references) a CBP Formal Entry Number. Message Types: FXI, FXC transmitted by Air AMS Express Consignment participants only.

            Action:      No action needed, Line Identifier CED is ignored.

087      ENTRY DATA VALID ONLY FOR EXPRESS SHIPMENT             {Reference: CED}

            Reason:    Line Identifier CED was received with non-express manifest data via Air AMS Message Type FRI or FRC.

            Action:     This error should be prevented by user data validation prior to transmission.

088      INVALID FILER ID IN ENTRY NUMBER                                        {Reference: CED}

            Reason:    A CBP Entry number reported in Line Identifier CED must reference a valid entry filer code.  Message Types: FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

089      INVALID CPB ENTRY NUMBER                                                       {Reference: CED}

            Reason:    The CBP Entry number received in Line Identifier CED did not pass validation of the 3 character entry filer code, 7 digit serial number and check digit. Message Types: FXI, FXC.

            Action:      Contact the CBP Entry filer to determine whether a check digit offset value must be added to the calculated check digit.

090      ENTRY NUMBER IGNORED FOR INTANGIBLES                       {Reference: CED}

            Reason:    A CBP Entry number is not required when Line Identifier CED references Entry Type 87, Intangible; HTSUS Headnotes.  Message Types: FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

091      ENTRY REQUIRED FOR SPECIFIED ENTRY TYPE                      {Reference: CED}

            Reason:    The Custom Entry type code reported in Line Identifier CED must reference the entry number of the CBP Form 7501 referencing express shipments eligible for release via CBP Regulations Part 128 Express Consignments. Entry type codes: 11, 86, 92.  Message Type: FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

092      ENTRY TYPE INVALID FOR SHIPMENT VALUE                          {Reference: CED}

            Reason:    The entry type code reported in Line Identifier CED is invalid for the shipment value (ref. Line Identifier CSD).  Message Types: FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

093      VALUE EXCEEDS MAXIMUM FOR ENTRY TYPE                       {Reference: CED}

            Reason:    The express shipment value exceeded the maximum allowable for the entry type code reported in Line Identifier CED.  Message Types: FXI, FXC

            Action:      This error should be prevented by user data validation prior to transmission.

094      ENTRY IGNORED - ABI ENTRY  PREVIOUSLY FILED

            Reason:    Line Identifier CED detail was received after the referenced Air AMS Express AWB manifest record was updated by CBP processing of other CBP entry data,, thus precluding release based upon express consignment.  Message Types: FXI, FXC

            Note:         In the event the Air AMS Express Consignment participant has not received expected FSN message(s) referencing CBP processing of entry data (or entry data reported via Line Identifier CED), either the Express Consignment AWB manifest record is incomplete (ref. Error Code 188) or the Air AMS flight record referencing the importing flight and Landing Port (Express HUB/ECCF port code) does not indicate the flight has departed the last foreign port or an actual date of arrival in the U.S.

            Action:      CBP status of a shipment should be verified via an Air AMS Freight Status Query (FSQ) message FSQ code 02 (status) to receive an FSC message with FSC code 07 followed by the entry number (if any) referenced in the AMS air waybill record.

095      CED CANCEL IGNORED - NO ENTRY ON FILE                           {Reference: CED}

            Reason:    Line Identifier CED was received with Cancellation indicator ‘000’ (numeric zeroes) referencing an express shipment manifest record not found in the Air AMS express AWB record.  Message Types: FXI, FXC.

096      INVALID EXPRESS ENTRY TYPE                                                    {Reference: CED}

            Reason:   A CBP entry type code other than 11, 86, 87, 91, 92, 93, 94 was received in Line Identifier CED detail.  Message Types: FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

101      INVALID WAYBILL LINE FORMAT                                                {Reference: WBL}

            Reason:    The syntax was incorrect.  Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

102      INVALID NOMINATED AGENT LINE FORMAT                           {Reference: AGT}

            Reason:    The syntax was incorrect.  Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

103      INVALID TRANSFER LINE FORMAT                                              {Reference: TRN}

            Reason:    The syntax was incorrect.  Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.
　

104      INVALID CBP SHIPMENT LINE FORMAT                                      {Reference: SHP}

            Reason:    The syntax was incorrect.  Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

105      INVALID SHIPPER NAME LINE FORMAT                                      {Reference: SHP}

            Reason:    The syntax was incorrect.  Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

106      INVALID CONSIGNEE NAME LINE FORMAT                              {Reference: CNE}

            Reason:    The syntax was incorrect.  Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

110      CBP ENTRY LINE IGNORED                                                             {Reference: CED}

            Reason:    Related to reported error code(s) 086, 087, 088, 089, 090, 091, 092, 093, 094, 095, 096.  Message Types: FXI, FXC.

111      WAYBILL LINE IGNORED                                                                 {Reference: WBL}

            Reason:    Related to reported error code(s) 026, 027, 028, 035, 036, or 188.  Message Types: FRI, FRC, FXI, FXC

            Note:         Freight Status Notification (FSN) message(s) referencing disposition of the shipment will not be transmitted by Air AMS until valid WBL data has been received. (See General Note (3), Air AMS Error Codes).

112      NOMINATED AGENT LINE IGNORED                                            {Reference: AGT}

            Reason:    Related to reported error code 141 or 043.  Message Types: FRI, FRC.

113      TRANSFER LINE IGNORED                                                              {Reference: TRN}

            Reason:    Related to reported error codes 171, 172, 173, 174, 175, 176, 177, or 178. All transfer detail received was ignored by Air AMS.  Message Types: FRI, FRC, FXI, FXC.

114      CBP SHIPMENT LINE IGNORED                                                       {Reference: SHP}

            Reason:    Related to reported error code(s) 181, 182, 186, or 188.  Message Types:  FRI, FRC, FXI, FXC.

115      SHIPPER NAME LINE IGNORED                                                      {Reference: SHP}

            Reason:    Related to reported error code 105.  Message Types: FRI, FRC, FXI, FXC.

116      CONSIGNEE NAME LINE IGNORED                                               {Reference: CNE}

            Reason:    Related to reported error code 106.  Message Types: FRI, FRC, FXI, FXC.

117      WARNING – PART BOARDED QTY EQ WBL QTY                        {Reference: ARR}

            Reason:    Arrival detail boarded piece count was the same as the WBL detail Total piece count.

            Action:      If not cancelled or amended to report boarded piece count less than WBL Total piece count, AMS will reject subsequent Part Arrival manifest data (see error code 128).  Do not transmit Part Arrival Reference detail when the actual boarded piece count equals the shipment (WBL) Total piece count.  Message Types: FRI, FRC, FXI, FXC.

120      PART SHIPMENT DATA IGNORED                                                 {Reference: ARR}

            Reason:    The Part Arrival Reference character reported in Arrival detail was found in an Air AMS Part Arrival AWB manifest record referencing an importing flight other than the flight detail received with this Part Arrival Reference.  If this error code is reported with error code 119, a shipment originally manifested to arrive intact aboard the flight referenced in the first Arrival detail line cannot be amended via the second Arrival detail line reporting Part-Shipment details.  Message Types: FRI, FRC, FXI, FXC.

121      INVALID BOARDED QUANTITY                                                      {Reference: ARR}

            Reason:    Part Arrival boarded quantity reported in Arrival detail must be greater than zero and less than the total AWB piece count reported or previously reported in WBL detail.  Message Types;  FRI, FRC, FXI, FSC.

            Example: ARR/DL039/12JAN-A/B/K.0 (no value received for boarded quantity).

            Action:      This error should be prevented by user data validation prior to transmission.

122      INVALID BOARDED WEIGHT CODE                                             {Reference: ARR}

            Reason:    The code is neither an "L" nor a “K”.  Fatal error, Message Types:  FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

123      NON-NUMERIC BOARDED WEIGHT                                             {Reference: ARR}

            Reason:    The boarded weight either is non-numeric or has been omitted.  Fatal error, Message Types:  FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

125      BILL EXISTS AS A SINGLE SHIPMENT                                         {Reference: AWB}

            Reason:    This error code is reported by AMS when incomplete House-level shipment information (without cargo control location and arriving flight detail) is received after cancellation (via FRX or FXX) of a complete House AWB record (as updated by Master AWB cargo control location and arriving flight detail). This error code may be reported if an amendment or cancellation contained a Part Arrival Reference when the active air waybill record in AMS did not contain a Part Arrival Reference.  If received referencing a House AWB number, the House AWB data must be resubmitted with the cargo control location and arriving flight detail matching the active Master AWB.  Fatal Error, Message Type FRI, FRC, FXI, FXC.

            Action:      Use the Freight Status Query (FSQ) message referencing option FSQ/01 (routing) and the Master AWB number only, then amend House shipment information via FRC or FXC (express users only) and include CCL and ARR detail from the FSC message when FSC/08 information routing is followed by TXT/MASTER AWB.

126      BILL EXISTS AS A SPLIT SHIPMENT                                             {Reference: ARR}

            Reason:    An amendment or cancellation was received without Part Shipment detail when shipment identification and arriving flight detail reference an active Air AMS part-arrival AWB manifest record.  Fatal error, Message Type FRC.

            Action:      Verify the active Air AMS AWB data via Freight Status Query (FSQ) message referencing option FSQ/01 (routing).

            Action:      This error should be prevented by user data validation prior to transmission.

127      CORRECTION PART IND NOT =EQUAL ORIGINAL                  {Reference: ARR}

            Reason:    An amendment to an existing Air AMS Part Shipment AWB manifest record does not reference the same Part Arrival reference character previously received and accepted by Air AMS for the arriving flight detail.  Fatal error, Message Types: FRC, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

128      CUM PART QTYS EXCEED TOTAL QTY                                         {Reference: WBL}

            Reason:    The sum of the active Air AMS part-arrival AWB manifest boarded quantities and the boarded quantity received for the next Part Arrival arriving flight cannot exceed the AWB total piece count.  Fatal Error, Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

129      INVALID PART ARRIVAL INDICATOR                                         {Reference: ARR}

            Reason:    The part arrival indicator is a non-alpha character.  Fatal error, Message Types:  FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

130      TOT QTY NOT SPECIFIED ON ORIGINAL PART                         {Reference: WBL}

            Reason:    A part-arrival manifest record cannot be established in Air AMS without the waybill detail specified in Line Identifier WBL or the waybill detail received was ignored due to other error in the data elements.  See Error code 111 for a list of error codes referencing Line Identifier WBL data elements.  Fatal error, Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

131      INVALID WAYBILL QUANTITY                                                       {Reference: WBL}

            Reason:   The number of pieces is either non-numeric, zero or exceeds 99999.  Fatal error, Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

132      INVALID WEIGHT CODE                                                                  {Reference: WBL}

            Reason:    The weight code must either be “K” (Kilograms) or “L” (Pounds).  Fatal error, Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

133      NON- NUMERIC WEIGHT                                                                {Reference: WBL}

            Reason:    Weight must be greater than zero, may contain a decimal, but cannot exceed 7 characters.  A decimal, if included, must be preceded and followed by a number.  Fatal error, Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

134      DESCRIPTION LINE TRUNCATED TO 35 CHARS                        {Reference: WBL}

            Reason:    A cargo description was received longer than 35 characters in length.  Message Types:  FRI, FRC, FXI, FXC.

            Action:      Cargo descriptions over 35 characters should be sent via one or more continuation lines not exceeding 35 characters each.  Up to 13 additional cargo description continuation lines may follow the WBL line, commencing with a separator slant and terminated by CRLF (carriage return and line feed).

135      DESTINATION ARRIVAL DATE IGNORED                                  {Reference: WBL}

            Reason:    The date of arrival at the PTP destination port is invalid or is prior to the reported scheduled date of arrival at first U.S. port in Line Identifier ARR.

            Action:      Verify that the date reported for scheduled arrival at first U.S. port and the Permit-to-Proceed arrival date is in reference to the local time in effect at the respective U.S. airport(s).  Message Types: FRI, FRC, FXI, FXC.

            Note:         CBP entry data references the estimated date of arrival of imported cargo at the port of entry.  This is the Permit-to-Proceed Destination airport for shipments remaining on board the importing flight at the first U.S. port of arrival.

136      PART IGNORED - MASTER BILL ALREADY EXIST                   {Reference: ARR}

            Reason:    The bill already exists as a non-split bill.

            Action:      No action needed, part indicator ignored.

137      PART INDICATOR AND BOARDED DATA IGNORED               {Reference: ARR}

            Reason:    The bill already exists as a non-split bill. Informational.

            Note:         This error code has not been verified in use as of 07/29/01.

138      CONTROLLING PART ID CHANGED                                             {Reference: ARR}

            Reason:    The controlling part of a split shipment has been changed.  The new controlling part can be identified in the ERR message.  Informational.

            Note:         This error code is no longer in use as of 07/29/01.

141      INVALID NOMINATED AGENT ID                                                  {Reference: AGT}

            Reason:    The code provided in Line Identifier AGT was not in the format of an air carrier (2-chr. [aa, na] or 3-chr [aaa, ann]), CBP bonded cargo facility (FIRMS code: [annn]) or Air AMS ABI Filer Forwarder (7-chr [an]).  Message Types: FRI, FRC, FXI, FXC.

            Action:      Contact the intended agent to obtain its Air AMS identifier code

142      NOMINATED AGENT IGNORED SINCE NOT AUTO                    {Reference: AGT}

            Reason:    The code provided in Line Identifier AGT does not reference an Air AMS user record of air carrier code, deconsolidator FIRMS code, or freight forwarder identifier.  Message Types: FRI, FRC, FXI, FXC.

            Note:        An air carrier nominated as agent must participate in Air AMS at the port of unlading of the shipment or at the In-bond Destination port.

151      SHIPPER NAME TRUNCATED TO 35 CHARACTERS                  {Reference: SHP}

            Reason:    The shipper name cannot exceed 35 characters.  Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

152      SHIPPER ADDR TRUNCATED TO 35 CHARACTERS                   {Reference: SHP}

            Reason:    The shipper street address cannot exceed 35 characters.  Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

153      SHIPPER CITY TRUNCATED TO 17 CHARACTERS                      {Reference: SHP}

            Reason:    The shipper city cannot exceed 17 characters. Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

154      SHIPPER STATE TRUNCATED TO 9 CHARACTERS                     {Reference: SHP}

            Reason:    The shipper state cannot exceed nine characters. Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.
　

155      SHIPPER COUNTRY INVALID: WILL BE IGNORED                     {Reference: SHP}

            Reason:    The shipper country code is not a valid ISO country code. See Appendix A.  Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

156      SHIPPER ZIP CODE TRUNCATED TO 9 CHARS                            {Reference: SHP}

            Reason:    The shipper postal code cannot exceed nine characters. Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

161      CONS NAME TRUNCATED TO 35 CHARACTERS                        {Reference: CNE}

            Reason:    The consignee name cannot exceed 35 characters. Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

162      CONS ADDRESS TRUNCATED TO 35 CHARACTERS                 {Reference: CNE}

            Reason:    The consignee street address cannot exceed 35 characters. Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

163      CONS CITY TRUNCATED TO 17 CHARACTERS                          {Reference: CNE}

            Reason:    The consignee city cannot exceed 17 characters. Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

164      CONS STATE TRUNCATED TO 9 CHARACTERS                          {Reference: CNE}

            Reason:    The consignee state cannot exceed nine characters. Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

166      CONS ZIP CODE TRUNCATED TO 9 CHARACTERS                    {Reference: CNE}

            Reason:    A consignee postal code cannot exceed nine characters. Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

167      CONS TEL-NO TRUNCATED TO 14 CHARACTERS                      {Reference: CNE}

            Reason:     The consignee telephone number cannot exceed 14 characters.  Message Types: FRI, FRC, FXI, FXC.

            Action:      This error should be prevented by user data validation prior to transmission.

171      INVALID AIRPORT CODE FOR TRANSFER DEST                       {Reference: TRN}

            Reason:    The airport/city code specified in transfer detail is not located within a CBP port of entry. Message Types: FRI, FRC.  (See Appendix A of this document, U.S. Domestic Airports)

            Action:      This error should be prevented by user data validation prior to transmission.

172      INVALID DOMESTIC - INTERNATL INDICATOR                       {Reference: TRN}

            Reason:    The Domestic/International indicator must be either “D” for domestic U.S. “I” for international cargo unladen from the arriving flight for subsequent exportation from the U.S. via other transport, or “R” for Freight Remaining On Board a flight departing the U.S. directly to a foreign destination (e.g., fuel stop only).  Message Types: FRI, FRC.

            Action:      This error should be prevented by user data validation prior to transmission.

173      INVALID ONWARD CARRIER ID                                                   {Reference: TRN}

            Reason:    The onward carrier code provided does not identify an air carrier (aaa = ICAO-issued three letter), ann = CBP assigned 3-chr, or air carrier abbreviation (an, na = IATA Airline designation).  Message Types: FRI, FRC.

            Note:         The Standard Carrier Alpha Code (SCAC) issued by National Motor Freight Traffic Association is not supported by Air AMS.

            Action:      This error should be prevented by user data validation prior to transmission.

174      INVALID INBOND CONTROL NUMBER FORMAT                    {Reference: TRN}

            Reason:    The 9-digit CBP Form 7512 In-bond Control Number provided or the default air waybill serial number has a bad check digit.  Note: An 11-digit AWB number other than the importing shipment identification cannot be utilized to control an in-bond for cargo imported via air.  Message Types: FRI, FRC.

            Action:      This error should be prevented by user data validation prior to transmission.

175      DESTINATION SHED INVALID FOR EXPORT                              {Reference: TRN}

            Reason:    Cargo intended for an International = “I” in-bond transfer may only include the exporting air carrier code and a 9-digit in-bond control number, when provided in lieu of the default air waybill number. It cannot reference a destination shed in the TRN position following onward carrier code.  The Air-AMS default destination shed for an export shipment is the onward carrier at the CBP control destination airport and may be provided if it is other than the importing air carrier within Transfer detail after Domestic/International Indicator “I”, as Onward air carrier code.

            Action:      This error should be prevented by user data validation prior to transmission.

176      TRANSFER WITHIN PORT REQUIRES SHED                               {Reference: TRN}

            Reason:    Destination shed, identified as a FIRMS or air carrier code was not provided for a Domestic transfer with the same airport or the PTP airport.  This code must be provided in the TRN position following the position defined as onward carrier code. Message Types: FRI, FRC, FXI, FXC.

            Action:      To request a within port transfer to an Air-AMS deconsolidator/CFS, provide the CBP FIRMS code.  To request a within port transfer to an Air-AMS carrier, provide the carrier code.  This error should be prevented by user data validation prior to transmission.
　

177      INBOND CONTROL NUMBER IN USE                                            {Reference: TRN}

            Reason:    A nine-digit CBP Form 7512 in-bond control number or the default 11-digit importing Master Air Waybill number cannot be reused to control more than one Part Shipment.  Other Part Shipment boarded quantities which arrive or are unladen at a U.S. port other than the U.S. destination of the shipment will not be authorized for In-Bond transfer unless a valid, unique in-bond control number is received.

            Action:      This error should be prevented by user data validation prior to transmission.

179      FSN INVALID - NO ACTIVE INBOND ROUTING                           {Reference: ASN}

            Reason:    At the time Air-AMS processed an FSN message reporting ASN code 3 (Notice of arrival at in-bond destination port), the referenced AWB manifest record did not reference an active In-bond transfer.  (ASN code 4 will also update an active in-bond transfer.)

            Action:      This error should be prevented by user data validation prior to transmission.

181      COUNTRY OF ORIGIN CODE INVALID                                         {Reference: CSD}

            Reason:    The country of origin is not a valid ISO-issued country code. Message Types: FRI, FRC, FXI, FXC.

            Action:      Verify from this Appendix or the IATA Airline Coding Directory and correct.  This error should be prevented by user data validation prior to transmission.

182      INVALID VALUE FOR CBP ON INBOND                                        {Reference: CSD}

            Reason:    The shipment value for CBP must be numeric and greater than zero.

            Action:      This error should be prevented by user data validation prior to transmission.

183      INVALID HSA NUMBER                                                                    {Reference: CSD}

            Reason:    The Harmonized Commodity Code is invalid. Message Types: FRI, FRC, FXI, FXC.

            Action:      Verify and correct.

184      XFER AT MASTER LEVEL - HOUSE XFER INVALID                   {Reference: TRN}

            Reason:    An in-bond transfer initiated at the master level has been applied to House-level shipments manifested to arrive in the U.S. on the same flight referenced in the transferred Master AWB.  Air AMS does not support an in-bond transfer initiated referencing an associated house level shipment after in-bond transfer authorization has occurred at the Master AWB level.  Message Types: FRI, FRC.

            Action:      No action needed, house transfer request ignored.

185      XFER AT HOUSE LEVEL - MASTER XFER INVALID                   {Reference: TRN}

            Reason:    There has already been an in-bond transfer at the house level, therefore the request for an in-bond transfer at the master level is invalid.  Message Types: FRI, FRC.

            Action:      A request for transfer authorization at the Master AWB level must precede update of an associated House-level shipment. Once a consolidation has been broken by in-bond transfer of a House-level shipment, CBP cannot authorize a transfer at the Master AWB level.

186      INVALID ISO CURRENCY CODE                                                     {Reference: CSD}

            Reason:    The ISO currency code is invalid. Message Types: FRI, FRC, FXI, FXC.

            Action:      Verify ISO currency code from this Appendix or the IATA Airline Coding Directory.  This error should be prevented by user data validation prior to transmission.

187      XFER NOTIFICATIONS NOT RLSD NO HOUSE AWB                  {Reference: TRN}

            Reason:    At the time Air AMS processed transfer detail referencing a Master AWB , no active House AWB manifest records were found referencing the Master AWB number and arriving flight detail.  Advisory Message Types FRI, FRC.

            Note:         Due to Air AMS input message queuing by shipment identification, avoidance of this error by Air AMS carriers is possible only by deferring Master AWB transfer detail to an amendment message transmitted after initial House AWB manifest data has been transmitted to Air AMS.  Until House AWB manifest data has been accepted by Air AMS, FSN.1D and/or FSN.1F will not be transmitted by Air AMS.

188      EXPRESS RECORD INCOMPLETE            {Reference: Message Types: FXI, FXC/ }

            Reason:    One or more manifest data elements required for compliance with CBP Regulations Part 128 – Express Consignments are missing from the AMS AWB record.

            Note:         Not applicable to Air AMS Message Types FRI or FRC

189      TRANSFER MAY ONLY BE SPECIFIED IN MAWB                      {Reference: TRN}

            Reason:    A local (within unlading or CBP Control Destination port) transit/transfer request was previously received referencing the Master AWB and therefore cannot be specified referencing a House AWB.  Also, a Foreign Cargo Remaining On Board (FROB) transfer is specified at the house bill level which is invalid.  See Error code 113.  Message Types: FRI, FRC.

            Action:      This error should be prevented by user data validation prior to transmission.

190      LAST TRANSFER NOT ARRIVED                                                     {Reference: TRN}

            Reason:     When attempting to add a second on subsequent in-bond or local transfer, the previous in-bond has not been arrived by an ASN3 message or the previous local transfer has not been arrived by an ASN4 message.

            Action:       Before submitting a second or subsequent transfer be sure that the previous transfer has been arrived.
　

191      LAST TRANSFER IS NON-AUTO                                                       {Reference: TRN}

            Reason:     When attempting to add a second on subsequent in-bond or local transfer, the previous in-bond destination port or local transfer shed is non-auto.  In this case the previous destination must be automated in Air AMS.

            Action:       Before submitting a second or subsequent transfer, be sure that the previous transfer destination is automated in Air AMS.

192      LOCAL TRANSFER INVALID WITH FROB                                    {Reference: TRN}

            Reason:     When attempting to add a Foreign Cargo Remaining On Board (FROB) transfer a local transfer shed was supplied in the TRN line which in invalid.

            Action:       Before submitting a FROB transfer, make sure you do not include a local transfer.

193      HOUSE INBOND - DESTINATION MUST BE AUTO                      {Reference: TRN}

            Reason:     When an in-bond has been requested for a house air waybill and there is a subsequent request for an in-bond movement at the master air waybill level, the destination shed for the master air waybill in-bond transfer must be an Air AMS participant.

            Action:       Before submitting an in-bond transfer at the master air waybill level when a house air waybill has an existing in-bond, be sure that the master air waybill transfer destination is automated in Air AMS.

194      HOUSE INBOND - INTL INDICATOR INVALID                             {Reference: TRN}

            Reason:     When attempting to add an in-bond transfer at the master level when a house in-bond exists, the in-bond transfer was specified as a T & E or an IE.  In this situation the in-bond transfer must be domestic.

            Action:       Always use the domestic indicator for in-bond transfers at the master level when an in-bond transfer exits at the house level.

195      CUSTODIAL BOND NOT FOUND ONWARD CARRIER                {Reference: TRN}

            Reason:     The onward carrier code provided does not reference an active CBP Custodial Bond required for an in-bond movement.

            Action:       Route the shipment via a carrier with the proper CBP Bond.

196      CUSTODIAL BOND NOT FOUND CBP BOND ID                           {Reference: TRN}

            Reason:     The CBP Bond Identification provided does not reference an active CBP Custodial Bond required of an in-bond movement.

            Action:       Provide CBP Bond Identification referencing an active CBP Bond.
　

197      SHELL RECORD CREATED AND MANIFEST EXISTS             {Reference:  AWB}

            Reason:     The House shipment identifier referenced by the entry filer with the Master AWB does not match any active House shipment information associated to the active Master AWB record on file in Air AMS.

            Action:       the incoming air carrier (for Air AMS participant providing advance house shipment information to CBP Air AMS) must provide the same shipment identification to the CBP entry filer, otherwise the Air AMS participant in custody of the shipment will not receive a Freight Status Notification message reporting CBP entry processing results.

198      SHELL RECORD CREATED FOR ENTRY                                     {Reference: AWB}

            Reason:    Manifest data was not on file referencing the shipment, as identified by the entry filer, estimated to arrive in the U.S. port of entry via the air carrier and importing flight FER message, line 2, Flight Details.  Advisory.

            Note:         To facilitate electronic notification of CBP disposition/action at the House bill level, information in the entry must be identical to the House-level information provided by the importing Air AMS carrier, or other party, to -Air AMS).

            Action:      Provide manifest data for the AWB to receive the FSN containing the status action code pertaining to the entry filed for the cargo.

199      CALL USCS FOR EXPLANATION

            Reason:    Undefined error condition.

            Action:       Please verify with your software vendor, prior to contacting your Client Representative, that the error code explanation text corresponds to the current error code explanation text received from Air AMS within the Freight Error Report message.  Your software vendor may not have updated your Air AMS interface program after CPB implementation of new or modified error code explanation text.

999  FSQ MESSAGE REJECTED

Reason:    Error code 999 was added to the Air AMS error code to enable users to attribute the subsequent error code(s) to a Freight Status Query message (inquiry). Absence of error code 999 in a Freight Error Report (FER) message indicates the error code(s) reference Air AMS message types other than FSQ.

(Taken from International Organization for Standardization ISO)