to initiating this action, ELDs must be capable of reading a text
file from an authorized safety officials' drive and verifying it
against a file provided to ELD providers who have registered their
technologies as described in section 5.1.

<IP_ADDRESS>. Data Transfer via Scannable QR Codes

    ELD transmitting data via two-dimensional barcode(s) must be
capable of encoding the data file described in section <IP_ADDRESS> via a
QR code or a series of QR codes, as defined in ISO/IEC18004:2006
specification (incorporated by reference, see Sec.  395.38),
reference (6)(a) in section 6 of this appendix.

QR codes must be no smaller than 1.5 square inches and have the
following specifications:

Level: L
Version: 15
Color: Black and White

<IP_ADDRESS>. Data Transfer via TransferJet TM

    ELDs transmitting data via the close proximity wireless
technology must use the TransferJet protocol as defined in ISO/IEC
17568 (incorporated by reference, see Sec.  395.38), reference
(6)(b) in section 6 of this appendix.
    The device or component of the device transmitting the ELD data
via TransferJet must be capable of being removed from the CMV to
allow the official to receive the transmission without entering the
vehicle.
    An ELD must re-authenticate the driver prior to transferring
driver's ELD file via TransferJet.
    With the initiation of the authenticated driver, the ELD using
TransferJet must activate Proactive Mode prior to transmitting
driver's ELD data to an official.

<IP_ADDRESS>. Printout

    If the ELD technology complies with the roadside data transfer
requirement by producing a printout report, it must be able to
generate the compliant report as specified in this section.
    The printout must include separate reports for the inspected
driver's profile and the unidentified driver profile. If there are
no unidentified driver records existing on the ELD for the current
24-hour period and for any of the previous 7 consecutive days, an
ELD does not need to print for the authorized safety official.
Otherwise, both reports must be printed and provided to the
authorized safety official.
    Print paper must be at least 2 inches wide. The paper must also
be at least 11 inches in height, or on a roll of paper that can be
torn when each individual printout is complete.
    The printout must include the following information for the
current 24-hour period and each of the previous 7 consecutive days:
(Items in < . > are data elements.)
[GRAPHIC] [TIFF OMITTED] TP28MR14.024

[GRAPHIC] [TIFF OMITTED] TP28MR14.025

[GRAPHIC] [TIFF OMITTED] TP28MR14.026

[GRAPHIC] [TIFF OMITTED] TP28MR14.027

[GRAPHIC] [TIFF OMITTED] TP28MR14.028

[GRAPHIC] [TIFF OMITTED] TP28MR14.029

[GRAPHIC] [TIFF OMITTED] TP28MR14.030

[GRAPHIC] [TIFF OMITTED] TP28MR14.031

[GRAPHIC] [TIFF OMITTED] TP28MR14.032

    The printout must include a graph-grid consistent with Sec.
395.8(g) displaying each change of duty status. The graph-grid for
each day's RODS must be at least 4 inches by 1.5 inches in size.
    The graph-grid must also overlay periods of driver's indications
of authorized personal use of CMV and yard moves using a different
style line (such as dashed or dotted line) or shading. The
appropriate abbreviation must also be indicated on the graph-grid.
    Upon request, an ELD must also produce a printout including QR
Code(s) as specified in section <IP_ADDRESS> to allow for the complete
transfer of data via a scanner in addition to the visual
presentation of the data on the printout report. Data coded in QR
code(s) must be compliant with the ELD data output format specified
in section <IP_ADDRESS>.

4.10.3. Motor Carrier Support System Data Transmission

    Regardless of the roadside transmission option supported by the
ELD technology, the support systems of the motor carrier where
electronic ELD records are maintained and retained must be able to
transmit enforcement-specified historical data for their drivers
using one of three methods specified under section 4.9.2. Web
services option must follow the specifications described under
section <IP_ADDRESS>. Email option must follow the specifications
described under section <IP_ADDRESS>, and USB option must follow the
specifications of Universal Serial Bus Specification, revision 2.0
(incorporated by reference, see Sec.  395.38), reference (2)(a) in
section 6 of this appendix, and described under section <IP_ADDRESS>.

5. ELD--Registration-Certification

    As described in Sec.  395.22(a) of subpart B, motor carriers
must only use ELDs that are listed on the FMCSA Web site. An ELD
provider must register with FMCSA and certify each ELD model and
version for that ELD to be listed on this Web site.

5.1. ELD Provider's Registration

5.1.1. Registering Online

    An ELD provider developing an ELD technology must register
online at a secure FMCSA Web site where the ELD provider can
securely certify that its ELD is compliant with this appendix.
Provider's registration must include the following information:
    (1) Company name of the technology provider/manufacturer.
    (2) Name of an individual authorized by the provider to verify
that the ELD is compliant with this appendix and to certify it under
section 5.2 of this appendix.
    (3) Address of the registrant.
    (4) Email address of the registrant.
    (5) Telephone number of the registrant.

5.1.2. Keeping Information Current

    The ELD provider must keep the information in section 5.1.1
current through FMCSA's Web site.

5.1.3. Authentication Information Distribution

    FMCSA will provide a unique ELD registration ID, authentication
key(s), authentication file(s), and formatting and configuration
details required in this appendix to registered providers during the
registration process.

5.2. Certification of Conformity With FMCSA Standards

    A registered ELD provider must certify that each ELD model and
version has been sufficiently tested to meet the functional
requirements included in this appendix under the conditions in which
the ELD would be used.

5.2.1. Online Certification

    An ELD provider registered online as described in section 5.1.1
must disclose the following information about each ELD model and
version and certify that the particular ELD is compliant with the
requirements of this appendix. The online process will only allow a
provider to complete certification if the provider successfully
discloses all of the following required information:
    (1) Name of the product.
    (2) Model number of the product.
    (3) Software version of the product.
    (4) An ELD identifier, uniquely identifying the certified model
and version of the ELD, assigned by the ELD provider in accordance
with 7.1.15.
    (5) Picture and/or screen shot of the product.
    (6) User's manual describing how to operate the ELD.
    (7) Description of the supported and certified data transfer
mechanisms and step-by-step instructions for a driver to produce and
transfer the ELD records to an authorized safety official.
    (8) Summary description of ELD malfunctions.
    (9) Procedure to validate an ELD authentication value as
described in section 7.1.14.
    (10) Certifying statement describing how the product was tested
to comply with FMCSA regulations.

5.2.2. Procedure To Validate an ELD's Authenticity

    Section 5.2.1(9) requires that the ELD provider institute an
authentication process and disclose necessary details for FMCSA
systems to independently verify the ELD authentication values
included in the dataset of inspected ELD outputs. The authentication
value must include a hash component that only uses data elements
included in the ELD dataset and datafile. ELD authentication value
must meet the requirements specified in section 7.1.14.

5.3. Publicly Available Information

    Except for the information listed under section 5.1.1(2), (4),
and (5) and section 5.2.1(9), FMCSA will make the information in
sections 5.1.1 and 5.2.1 for each certified ELD publicly available
on a Web site to allow motor carriers to determine which products
have been properly registered and certified as ELDs compliant with
this appendix.

6. References

    (1) World Wide Web Consortium (W3C). 32 Vassar Street, Building
32-G514, Cambridge, MA 02139. Web page is http://www.w3.org;
telephone is<PHONE_NUMBER>.
    (a) ``Web Services Description Language (WSDL) 1.1, W3C Note 15,
March 2001,'' Ariba, IBM Research, Microsoft. (See Sec.  395.38,
Incorporation by Reference.)
    (b) ``Simple Object Access Protocol (SOAP) Version 1.2 Part 1:
Messaging Framework (Second Edition), W3C Recommendation 27 April
2007,'' W3C[supreg] (MIT, ERCIM, Keio). (See Sec.  395.38,
Incorporation by Reference.)
    (c) ``Extensible Markup Language (XML) 1.0 (Fifth Edition), W3C
Recommendation 26 November 2008,'' W3C[supreg] (MIT, ERCIM, Keio).
(See Sec.  395.38, Incorporation by Reference.)
    (d) RFC 2616 ``Hypertext Transfer Protocol--HTTP/1.1.'' (See
Sec.  395.38, Incorporation by Reference.)
    (2) Universal Serial Bus Implementers Forum (USBIF). 3855 SW.
153rd Drive, Beaverton, Oregon 97006. Web page is http://www.usb.org; telephone is<PHONE_NUMBER>.

    (a) ``Universal Serial Bus Specification,'' Compaq, Hewlett-
Packard, Intel, Lucent, Microsoft, NEC, Philips; April 27, 2000
(Revision 2.0). (See Sec.  395.38, Incorporation by Reference.)
    (3) American National Standards Institute (ANSI). 11 West 42nd
Street, New York, New York 10036. Web page is http://webstore.ansi.org; telephone is<PHONE_NUMBER>.
    (a) ``ANSI INCITS 446-2008, American National Standard for
Information Technology--Identifying Attributes for Named Physical
and Cultural Geographic Features (Except Roads and Highways) of the
United States, Its Territories, Outlying Areas, and Freely
Associated Areas and the Waters of the Same to the Limit of the
Twelve-Mile Statutory Zone (10/28/2008),'' (ANSI INCITS 446-2008).
(For further information, see also the Geographic Names Information
System (GNIS) at http://geonames.usgs.gov/domestic/index.html. (See
Sec.  395.38, Incorporation by Reference.)
    (b) ``Information Systems--Coded Character Sets--7-Bit American
National Standard Code for Information Interchange (7-Bit ASCII)'',
ANSI INCITS 4-1986 (R2007). (See Sec.  395.38, Incorporation by
Reference.)
    (4) IEEE Standards Association. 445 Hoes Lane, Piscataway, NJ
08854-4141. Web page is http://standards.ieee.org/index.html.
Telephone is<PHONE_NUMBER>.
    (a) ``Standard for Authentication in Host Attachments of
Transient Storage Devices'', IEEE Standards Association: 2009 (IEEE
Std. 1667-2009). (See Sec.  395.38, Incorporation by Reference.)
    (b) [Reserved]
    (5) U.S. Department of Commerce, National Institute of Standards
and Technology (NIST). 100 Bureau Drive, Stop 1070, Gaithersburg, MD
20899-1070. Web page is http://www.nist.gov. Telephone is (301) 975-
6478.
    (a) ``Federal Information Processing Standards (FIPS)
Publication 197, November 26, 2001, Announcing the ADVANCED
ENCRYPTION STANDARD (AES)''. (See Sec.  395.38, Incorporation by
Reference.)
    (b) ``Special Publication (SP) 800-32, February 26, 2001,
Introduction to Public Key Technology and the Federal PKI
Infrastructure.'' (See Sec.  395.38, Incorporation by Reference.)
    (6) International Standards Organization (ISO). 1, ch. de la
Voie-Creuse, CP 56-CH-1211, Geneva 20, Switzerland. Web page is
http://www.iso.org. Telephone is 41 22 749 03 46.
    (a) ``ISO/IEC 18004:2006 Information technology--Automatic
identification and data capture techniques--QR Code 2005 bar code
symbology specification''. (See Sec.  395.38, Incorporation by
Reference.)
    (b) ``ISO/IEC 17568 Information technology--Telecommunications
and information exchange between systems--Close proximity electric
induction wireless communications.'' (See Sec.  395.38,
Incorporation by Reference.)
    (7) Internet Engineering Task Force (IETF). C/o Association
Management Solutions, LLC (AMS), 48377 Freemont Blvd., Suite 117,
Freemont, CA 94538. Telephone is<PHONE_NUMBER>.
    (a) RFC 5246--``The Transport Layer Security (TLS) Protocol
Version 1.2'', August 2008. (See Sec.  395.38, Incorporation by
Reference.)
    (b) RFC 5321--``Simple Mail Transfer Protocol,'' October 2008.
(See Sec.  395.38, Incorporation by Reference.)
    (c) RFC 5322--``Internet Message Format,'' October 2008. (See
Sec.  395.38, Incorporation by Reference.)
    (8) Bluetooth SIG, Inc. 5209 Lake Washington Blvd. NE., Suite
350, Kirkland, WA 98033. Web page is https://www.bluetooth.org/Technical/Specifications/adopted.htm. Telephone is<PHONE_NUMBER>.
    (a) ``Specification of the Bluetooth System: Wireless
Connections Made Easy,'' Bluetooth SIG Covered Core Package version
2.1 + EDR or a higher version. (See Sec.  395.38, Incorporation by
Reference.)
    (b) [Reserved]

7. Data Elements Dictionary

7.1.1. 24-Hour Period Starting Time

    Description: This data element refers to the 24-hour period
starting time specified by the motor carrier for driver's home
terminal.
    Purpose: Identifies the bookends of the work day for the driver;
Makes ELD records consistent with Sec.  395.8 requirements which
require this information to be included on the form.
    Source: Motor carrier.
    Used in: ELD account profile; ELD outputs.
    Data Type: Programmed or populated on the ELD during account
creation and maintained by the motor carrier to reflect true and
accurate information for drivers.
    Data Range: 0000 to 2359; first two digits 00 to 23; last two
digits 00 to 59.
    Data Length: 4 characters.
    Data Format:  Military time format where ``HH'' refer
hours and ``MM'' refer minutes designation for start time expressed
in time standard in effect at the driver's home terminal.
    Disposition: Mandatory.
    Examples: [0600], [0730], [1800].

7.1.2. Carrier Name

    Description: This data element refers to the motor carrier's
legal name for conducting commercial business.
    Purpose: Provides a recognizable identifier about the motor
carrier on viewable ELD outputs; Provides ability to cross check
against USDOT number.
    Source: FMCSA's Safety and Fitness Electronic Records (SAFER)
System.
    Used in: ELD account profile.
    Data Type: Programmed on the ELD or entered once during the ELD
account creation process.
    Data Range: Any alphanumeric combination.
    Data Length: Minimum: 4; Maximum: 120 characters.
    Data Format:  as in  to .
    Disposition: Mandatory.
    Example: [CONSOLIDATED TRUCKLOAD INC.].

7.1.3. Carrier's USDOT Number

    Description: This data element refers to the motor carrier's
USDOT number.
    Purpose: Uniquely identifies the motor carrier employing the
driver using the ELD.
    Source: FMCSA's Safety and Fitness Electronic Records (SAFER)
System.
    Used in: ELD account profiles; ELD event records; ELD output
file.
    Data Type: Programmed on the ELD or entered once during the ELD
account creation process.
    Data Range: An integer number of length 1-8 assigned to the
motor carrier by FMCSA (9 position numbers reserved).
    Data Length: Minimum: 1; Maximum: 9 characters.
    Data Format:  as in  to .
    Disposition: Mandatory.
    Examples: [1], [1000003].

7.1.4. CMV Power Unit Number

    Description: This data element refers to the identifier the
motor carrier uses for their CMVs in their normal course of
business.
    Purpose: Identifies the vehicle a driver operates while a
driver's ELD records are recorded; Makes ELD records consistent with
Sec.  395.8 requirements which requires the truck or tractor number
to be included on the form.
    Source: Unique CMV identifiers a motor carrier's uses in their
normal course of business and include on dispatch documents or the
license number and the licensing State of the power unit.
    Used in: ELD event records; ELD output file.
    Data Type: Programmed on the ELD or populated by motor carrier's
extended ELD system or entered by the driver.
    Data Range: Any alphanumeric combination.
    Data Length: Minimum: 1; Maximum: 10 characters.
    Data Format:  as in  to .
    Disposition: Mandatory for all CMVs operated while using an ELD.
    Examples: [123], [00123], [BLUEKW123], [TX12345].

7.1.5. CMV VIN

    Description: This data element refers to the manufacturer
assigned vehicle identification number (VIN) for the CMV powered
unit.
    Purpose: Uniquely identifies the operated CMV not only within a
motor carrier at a given time but across all CMVs sold within a 30
year rolling period.
    Source: A robust unique CMV identifier standardized in North
America.
    Used in: ELD event records; ELD output file.
    Data Type: Retrieved from the engine ECM via the vehicle
databus.
    Data Range: Either blank or 17 characters long as specified by
NHTSA in 49 CFR part 565, or 18 characters long with first character
assigned as ``-'' (dash) followed by the 17 character long VIN.
Check digit, i.e., VIN character position 9, as specified in 49 CFR
part 565 must imply a valid VIN.
    Data Length: Blank or 17-18 characters.
    Data Format:  or <``-''>  or <{blank{time} >
as in , or <-CCCCCCCCCCCCCCCCC> or <>.
    Disposition: Mandatory for all CMVs linked to the engine ECM and
when VIN is

available from the engine ECM over the vehicle databus; Otherwise
optional. If optionally populated and source is not the engine ECM,
precede VIN with the character ``-'' in records.
    Examples: [1FUJGHDV0CLBP8834], [-1FUJGHDV0CLBP8896], [ ].

7.1.6. Comment/Annotation

    Description: This is a textual note related to a record, update
or edit capturing the comment or annotation a driver or another
authorized support personnel may input to the ELD.
    Purpose: Provides ability for a driver to offer explanations to
records, selections, edits or entries.
    Source: Driver or another authenticated motor carrier support
personnel.
    Used in: ELD events; ELD outputs.
    Data Type: Entered by the authenticated user via ELD's
interface.
    Data Range: Free form text of any alphanumeric combination.
    Data Length: 0-60 characters if optionally entered;
    4-60 characters if annotation is required and driver is prompted
by the ELD.
    Data Format:  as in <{blank{time} > or
to .
    Disposition: Optional in general; Mandatory if prompted by ELD.
    Examples: [ ], [Personal Conveyance. Driving to Restaurant in
bobtail mode], [Forgot to switch to SB. Correcting here].

7.1.7. Data Diagnostic Event Indicator Status

    Description: This is a Boolean indicator identifying whether the
used ELD unit has an active data diagnostic event set for the
authenticated driver at the time of event recording.
    Purpose: Documents the snapshot of ELD's data diagnostic status
for the authenticated driver at the time of an event recording.
    Source: ELD internal monitoring functions.
    Used in: ELD events; ELD outputs.
    Data Type: Internally monitored and managed.
    Data Range: 0 (no active data diagnostic events for the driver)
or 1 (at least one active data diagnostic event set for the driver).
    Data Length: 1 character.
    Data Format:  as in .
    Disposition: Mandatory.
    Examples: [0] or [1].

7.1.8. Date

    Description: In combination with the variable ``Time'', this
parameter stamps records with a reference in time; Even though date
and time must be captured in UTC, event records must use date and
time converted to the time zone in effect at the driver's home
terminal as specified in section 4.4.3.
    Purpose: Provides ability to record the instance of recorded
events.
    Source: ELD's converted time measurement.
    Used in: ELD events; ELD outputs.
    Data Type: UTC date must be automatically captured by ELD; Date
in effect at the driver's home terminal must be calculated as
specified in section 4.4.3.
    Data Range: Any valid date combination expressed in
format where ``MM'' refers to months, ``DD'' refers to days of the
month and ``YY'' refers to the last two digits of the calendar year.
    Data Length: 6 characters.
    Data Format:  where  must be between 01 and 12,
must be between 01 and 31, and  must be between 00 and 99.
    Disposition: Mandatory.
    Examples: [122815], [010114], [061228].

7.1.9. Distance Since Last Valid Coordinates

    Description: Distance in whole miles traveled since the last
valid latitude, longitude pair the ELD measured with the required
accuracy.
    Purpose: Provides ability to keep track of location for recorded
events in cases of temporary position measurement outage.
    Source: ELD internal calculations.
    Used in: ELD events; ELD outputs.
    Data Type: Kept track of by the ELD based on position
measurement validity.
    Data Range: An integer value between 0 and 6; If the distance
traveled since the last valid coordinate measurement exceeds 6
miles, the ELD must enter the value as 6.
    Data Length: 1 character.
    Data Format:  as in .
    Disposition: Mandatory.
    Examples: [0], [1], [5], [6].

7.1.10. Driver's License Issuing State

    Description: This data element refers to the issuing State,
Province or Jurisdiction of the listed Driver's License for the ELD
account holder.
    Purpose: In combination with ``Driver's License Number'', it
links the ELD driver account holder uniquely to an individual with
driving credentials; Ensures that only one driver account can be
created per individual.
    Source: Driver's license.
    Used in: ELD account profile(s); ELD output file.
    Data Type: Entered (during the creation of a new ELD account).
    Data Range: To character abbreviation listed on Table 6.
    Data Length: 2 characters.
     as in .
    Disposition: Mandatory for all driver accounts created on the
ELD; Optional for ``non-driver'' accounts.
    Example: [WA].

                                 Table 6--State and Province Abbreviation Codes
----------------------------------------------------------------------------------------------------------------
             State code                         State                  State code                 State
----------------------------------------------------------------------------------------------------------------
                                                     U.S.A.
----------------------------------------------------------------------------------------------------------------
AL..................................  ALABAMA                   MT.....................  MONTANA.
AK..................................  ALASKA                    NC.....................  NORTH CAROLINA.
AR..................................  ARKANSAS                  ND.....................  NORTH DAKOTA.
AZ..................................  ARIZONA                   NE.....................  NEBRASKA.
CA..................................  CALIFORNIA                NH.....................  NEW HAMPSHIRE.
CO..................................  COLORADO                  NJ.....................  NEW JERSEY.
CT..................................  CONNECTICUT               NM.....................  NEW MEXICO.
DC..................................  DISTRICT OF COLUMBIA      NV.....................  NEVADA.
DE..................................  DELAWARE                  NY.....................  NEW YORK.
FL..................................  FLORIDA                   OH.....................  OHIO.
GA..................................  GEORGIA                   OK.....................  OKLAHOMA.
HI..................................  HAWAII                    OR.....................  OREGON.
IA..................................  IOWA                      PA.....................  PENNSYLVANIA.
ID..................................  IDAHO                     RI.....................  RHODE ISLAND.
IL..................................  ILLINOIS                  SC.....................  SOUTH CAROLINA.
IN..................................  INDIANA                   SD.....................  SOUTH DAKOTA.
KS..................................  KANSAS                    TN.....................  TENNESSEE.
KY..................................  KENTUCKY                  TX.....................  TEXAS.
LA..................................  LOUISIANA                 UT.....................  UTAH.
MA..................................  MASSACHUSETTS             VA.....................  VIRGINIA.
MD..................................  MARYLAND                  VT.....................  VERMONT.
ME..................................  MAINE                     WA.....................  WASHINGTON.
MI..................................  MICHIGAN                  WI.....................  WISCONSIN.
MN..................................  MINNESOTA                 WV.....................  WEST VIRGINIA.

MO..................................  MISSOURI                  WY.....................  WYOMING.
MS..................................  MISSISSIPPI
----------------------------------------------------------------------------------------------------------------
                                      AMERICAN POSSESSIONS OR PROTECTORATES
----------------------------------------------------------------------------------------------------------------
AS..................................  AMERICAN SAMOA.
GU..................................  GUAM.
MP..................................  NORTHERN MARIANAS.
PR..................................  PUERTO RICO.
VI..................................  VIRGIN ISLANDS.
----------------------------------------------------------------------------------------------------------------
                                                     CANADA
----------------------------------------------------------------------------------------------------------------
            Province code                                              Province
----------------------------------------------------------------------------------------------------------------
AB..................................  ALBERTA.
BC..................................  BRITISH COLUMBIA.
MB..................................  MANITOBA.
NB..................................  NEW BRUNSWICK.
NF..................................  NEWFOUNDLAND.
NS..................................  NOVA SCOTIA.
NT..................................  NORTHWEST TERRITORIES.
ON..................................  ONTARIO.
PE..................................  PRINCE EDWARD ISLAND.
QC..................................  QUEBEC.
SK..................................  SASKATCHEWAN.
YT..................................  YUKON TERRITORY.
----------------------------------------------------------------------------------------------------------------
                                                     MEXICO
----------------------------------------------------------------------------------------------------------------
AG..................................  AGUASCALIENTES            MX.....................  MEXICO.
BN..................................  BAJA CALIFORNIA NORTE     NA.....................  NAYARIT.
BS..................................  BAJA CALIFORNIA SUR       NL.....................  NUEVO LEON.
CH..................................  COAHUILA                  OA.....................  OAXACA.
CI..................................  CHIHUAHUA                 PU.....................  PUEBLA.
CL..................................  COLIMA                    QE.....................  QUERETARO.
CP..................................  CAMPECHE                  QI.....................  QUINTANA ROO.
CS..................................  CHIAPAS                   SI.....................  SINALOA.
DF..................................  DISTRICTO FEDERAL         SL.....................  SAN LUIS POTOSI.
DG..................................  DURANGO                   SO.....................  SONORA.
GE..................................  GUERRERO                  TA.....................  TAMAULIPAS.
GJ..................................  GUANAJUATO                TB.....................  TABASCO.
HD..................................  HIDALGO                   TL.....................  TLAXCALA.
JA..................................  JALISCO                   VC.....................  VERACRUZ.
MC..................................  MICHOACAN                 YU.....................  YUCATAN.
MR..................................  MORELOS                   ZA.....................  ZACATECAS.
----------------------------------------------------------------------------------------------------------------
                                                      OTHER
----------------------------------------------------------------------------------------------------------------
            Province code                                     Province, state or country
----------------------------------------------------------------------------------------------------------------
OT..................................  ALL OTHERS NOT COVERED ABOVE.
----------------------------------------------------------------------------------------------------------------

7.1.11. Driver's License Number

    Description: This data element refers to the unique Driver's
License information required for each driver account on the ELD.
    Purpose: In combination with driver's license issuing State, it
links the ELD driver account holder to an individual with driving
credentials; Ensures that only one driver account can be created per
individual.
    Source: Driver's license.
    Used in: ELD account profile(s); ELD output file.
    Data Type: Entered (during the creation of a new ELD account).
    Data Range: Any alphanumeric combination.
    Data Length: Minimum: 1; Maximum: 20 characters.
    Data Format:  as in  to
. For ELD record keeping purposes, ELD must
only retain characters in a Driver's License Number entered during
an account creation process that are a number between 0-9 or a
character between A-Z (non-case sensitive).
    Disposition: Mandatory for all driver accounts created on the
ELD; Optional for ``non-driver'' accounts.
    Examples: [SAMPLMJ065LD], [D000368210361], [198],
[N02632676353666].

7.1.12. Driver's Location Description

    Description: This is a textual note related to the location of
the CMV input by the driver upon ELD's prompt.
    Purpose: Provides ability for a driver to enter location
information related to entry of missing records; Provides ability to
accommodate temporary positioning service interruptions or outage
without setting positioning malfunctions.
    Source: Driver, only when prompted by the ELD.
    Used in: ELD events; ELD outputs.
    Data Type: Entered by the authenticated driver when ELD solicits
this information as specified in section <IP_ADDRESS>.

    Data Range: Free form text of any alphanumeric combination.
    Data Length: 5-60 characters.
    Data Format:  to .
    Disposition: Mandatory when prompted by ELD.
    Examples: [ ], [5 miles SW of Indianapolis, IN], [Reston, VA].

7.1.13. ELD Account Type

    Description: An indicator designating whether an ELD account is
of type driver support personnel (non-driver).
    Purpose: Enables to verify account type specific requirements
set forth in this document.
    Source: ELD designated.
    Used in: ELD outputs.
    Data Type: Specified during the account creation process and
recorded on ELD.
    Data Range: Character ``D'' indicating of account type
``Driver'' or ``S'', indicating of account type (``motor carrier's
support personnel'' i.e. non-driver); ``Unidentified Driver''
account must be designated with type ``D''.
    Data Length: 1 character.
    Data Format: .
    Disposition: Mandatory.
    Examples: [D], [S].

7.1.14. ELD Authentication Value

    Description: An alphanumeric value that is unique to an ELD and
verifies the authenticity of the given ELD.
    Purpose: Provides ability to cross-check the authenticity of an
ELD used in the recording of a driver's records during inspections.
    Source: ELD provider assigned value; Includes a certificate
component and a hashed component; Necessary information related to
authentication keys and hash procedures disclosed by the registered
ELD provider during the online ELD certification process for
independent verification by FMCSA systems.
    Used in: ELD outputs.
    Data Type: Calculated from the authentication key and
calculation procedure privately distributed by the ELD provider to
FMCSA during the ELD registration process.
    Data Range: Alphanumeric combination.
    Data Length: 16-32 characters.
    Data Format: .
    Disposition: Mandatory.
    Example: [D3A4506EC8FF566B506EC8FF566BDFBB].

7.1.15. ELD Identifier

    Description: An alphanumeric identifier assigned by the ELD
provider to the ELD technology that is certified by the registered
provider at FMCSA's Web site.
    Purpose: Provides ability to cross-check that the ELD used in
the recording of a driver's records is certified through FMCSA's
registration and certification process as required.
    Source: Assigned and submitted by the ELD provider during the
online certification of an ELD model, and version.
    Used in: ELD outputs.
    Data Type: Coded on the ELD by the ELD provider and disclosed to
FMCSA during the online certification process.
    Data Range: A six character alphanumeric identifier using
characters A-Z and number 0-9
    Data Length: 6 characters.
    Data Format:  as in .
    Disposition: Mandatory.
    Examples: [1001ZE], [GAM112], [02P3P1].

7.1.16. ELD Registration ID

    Description: An alphanumeric registration identifier assigned to
the ELD provider that is registered with FMCSA during the ELD
registration process.
    Purpose: Provides ability to cross-check that the ELD provider
has registered as required.
    Source: Received from FMCSA during online provider registration.
    Used in: ELD outputs.
    Data Type: Coded on the ELD by the Provider.
    Data Range: A four character alphanumeric registration
identifier using characters A-Z and numbers 0-9.
    Data Length: 4 characters.
    Data Format:  as in .
    Disposition: Mandatory.
    Examples: [ZA10], [QA0C], [FAZ2].

7.1.17. ELD Username

    Description: This data element refers to the unique user
identifier assigned to the account holder on the ELD to authenticate
the corresponding individual during an ELD login process; The
individual may be a driver or a motor carrier's support personnel.
    Purpose: Documents the user identifier assigned to the driver
linked to the ELD account.
    Source: Assigned by the motor carrier during the creation of a
new ELD account.
    Used in: ELD account profile; Event records; ELD login process.
    Data Type: Entered (during account creation and user
authentication).
    Data Range: Any alphanumeric combination.
    Data Length: Minimum: 4; Maximum: 60 characters.
    Data Format:  as in  to .
    Disposition: Mandatory for all accounts created on the ELD.
    Examples: [smithj], [100384], [sj2345], [john.smith].

7.1.18. Engine Hours

    Description: Engine hours refer to the time the CMV's engine in
powered in decimal hours with 0.1 hr (6-minute) resolution; This
parameter is a placeholder for <{Total{time}  Engine Hours> which
refers to the aggregated time of a vehicle's engine's operation
since its inception and used in recording ``engine power on'' and
``engine shut down'' events, and also for <{Elapsed{time}  Engine
Hours> which refers to the elapsed time in engine's operation in the
given ignition power on cycle and used in the recording of all other
events.
    Purpose: Provides ability to identify gaps in the operation of a
CMV, when the vehicle's engine may be powered but the ELD may not;
Provides ability to cross check integrity of recorded data elements
in events and prevent gaps in the recording of ELD.
    Source: ELD measurement or sensing.
    Used in: ELD events; ELD outputs.
    Data Type: Acquired from the engine ECM or a comparable other
source as allowed in section <IP_ADDRESS>.
    Data Range: For <{Total{time}  Engine Hours>, range is between
0.0 and 99,999.9;
    For <{Elapsed{time}  Engine Hours>, range is between 0.0 and
99.9.
    Data Length: 3-7 characters.
    Data Format:  as in  to .
    Disposition: Mandatory.
    Examples: [0.0], [9.9], [346.1], [2891.4].

7.1.19. Event Code

    Description: A dependent attribute on ``Event Type'' parameter
that further specifies the nature of the change indicated in ``Event
Type''; This parameter indicates the new status after the change.
    Purpose: Provides ability to code the specific nature of the
change electronically.
    Source: ELD internal calculations.
    Used in: ELD event records; ELD outputs.
    Data Type: ELD recorded and maintained event attribute in
accordance with the type of event and nature of the new status being
recorded.
    Data Range: Dependent on the ``Event Type'' as indicated on
Table 7.
    Data Length: 1 character.
    Data Format:  as in .
    Disposition: Mandatory.
    Examples: [0], [1], [4], [9].

                Table 7--``Event Type'' Parameter Coding
------------------------------------------------------------------------
                                                          Event code
        Event type                Event code             description
------------------------------------------------------------------------
1........................   1......................  Driver's duty
                                                      status changed to
                                                      ``Off-duty''.
1........................   2......................   Driver's duty
                                                      status changed to
                                                      ``Sleeper Berth''.
1........................   3......................  Driver's duty
                                                      status changed to
                                                      ``Driving''.
1........................   4......................  Driver's duty
                                                      status changed to
                                                      ``On-duty not
                                                      driving''.
2........................   1......................  Intermediate log
                                                      with conventional
                                                      location
                                                      precision.
2........................   2......................  Intermediate log
                                                      with reduced
                                                      location
                                                      precision.
3........................   1......................  Driver indicates
                                                      ``Authorized
                                                      Personal Use of
                                                      CMV''.
3........................   2......................  Driver indicates
                                                      ``Yard Moves''.

3........................   0......................  Driver indication
                                                      for PC, YM and WT
                                                      cleared.
4........................  1.......................  Driver's first
                                                      certification of a
                                                      daily record.
4........................   n......................   Driver's n'th
                                                      certification of a
                                                      daily record (when
                                                      recertification
                                                      necessary). ``n''
                                                      is an integer
                                                      between 1 and 9.
                                                      If more than 9
                                                      certifications
                                                      needed, use 9 for
                                                      each new re-
                                                      certification
                                                      record.
5........................   1......................  Authenticated
                                                      driver's ELD login
                                                      activity.
5........................   2......................   Authenticated
                                                      driver's ELD
                                                      logout activity.
6........................   1......................   Engine power-up
                                                      with conventional
                                                      location
                                                      precision.
6........................   2......................  Engine power-up
                                                      with reduced
                                                      location
                                                      precision.
6........................  3.......................  Engine shut down
                                                      with conventional
                                                      location
                                                      precision.
6........................  4.......................  Engine shut-down
                                                      with reduced
                                                      location
                                                      precision.
7........................  1.......................   An ELD malfunction
                                                      logged.
7........................   2......................   An ELD malfunction
                                                      cleared.
7........................  3.......................  A data diagnostic
                                                      event logged.
7........................   4......................  A data diagnostic
                                                      event cleared.
------------------------------------------------------------------------

7.1.20. Event Data Check Value

    Description: A hexadecimal ``check'' value calculated in
accordance to procedure outlined in section <IP_ADDRESS> and attached to
each event record at the time of recording.
    Purpose: Provides ability to identify cases where an ELD event
record may have been inappropriately modified after its original
recording.
    Source: ELD internal
    Used in: ELD events; ELD output file.
    Data Type: Calculated by the ELD in accordance with <IP_ADDRESS>.
    Data Range: A number between hexadecimal 00 (decimal 0) and
hexadecimal FF (decimal 255).
    Data Length: 2 characters.
    Data Format:  as in .
    Disposition: Mandatory.
    Examples: [05], [CA], [F3].

7.1.21. Event Record Origin

    Description: An attribute for the event record indicating
whether it is automatically recorded, or edited, entered or accepted
by the driver, requested by another authenticated user, or assumed
from unidentified driver profile.
    Purpose: Provides ability to track origin of the records.
    Source: ELD internal calculations.
    Used in: ELD event records; ELD outputs.
    Data Type: ELD recorded and maintained event attribute in
accordance with the procedures outlined in sections <IP_ADDRESS>.2,
<IP_ADDRESS>.3, <IP_ADDRESS>.4 and <IP_ADDRESS>.5.
    Data Range: 1, 2, 3 or 4 as described on Table 8.
    Data Length: 1 character.
    Data Format:  as in .
    Disposition: Mandatory.
    Examples: [1], [2], [3], [4].

            Table 8--``Event Record Origin'' Parameter Coding
------------------------------------------------------------------------
                                                           Event record
                   Event record origin                      origin code
------------------------------------------------------------------------
Automatically recorded by ELD...........................               1
Edited or Entered by the Driver.........................               2
Edit Requested by an Authenticated User other than the                 3
 Driver.................................................
Assumed from Unidentified Driver profile................               4
------------------------------------------------------------------------

7.1.22. Event Record Status

    Description: An attribute for the event record indicating
whether an event is active or inactive and further, if inactive,
whether it is due to a change or lack of confirmation by the driver
or due to a driver's rejection of change request.
    Purpose: Provides ability to keep track of edits and entries
performed over ELD records while retaining original records.
    Source: ELD internal calculations.
    Used in: ELD event records; ELD outputs.
    Data Type: ELD recorded and maintained event attribute in
accordance with the procedures outlined in sections <IP_ADDRESS>.2,
<IP_ADDRESS>.3, <IP_ADDRESS>.4, <IP_ADDRESS>.5, and <IP_ADDRESS>.6.
    Data Range: 1, 2, 3 or 4 as described on Table 9.
    Data Length: 1 character.
    Data Format:  as in .
    Disposition: Mandatory.
    Examples: [1], [2], [3], [4]

            Table 9--``Event Record Status'' Parameter Coding
------------------------------------------------------------------------
                                                           Event record
                   Event record status                      status code
------------------------------------------------------------------------
Active..................................................               1
Inactive--Changed.......................................               2
Inactive--Change Requested..............................               3
Inactive--Change Rejected...............................               4
------------------------------------------------------------------------

7.1.23. Event Sequence ID Number

    Description: This data element refers to the serial identifier
assigned to each required ELD event as described in section 4.5.1.
    Purpose: Provides ability to keep a continuous records keeping
track on a given ELD across all users of that ELD.
    Source: ELD internal calculations.
    Used in: ELD event records; ELD outputs.
    Data Type: ELD maintained; Incremented by 1 for each new record
on the ELD; Continuous for each new event the ELD records regardless
of owner of the records.
    Data Range: 0 to FFFF; Initial factory value must be 0; After
FFFF hexadecimal (decimal 65535), the next Event Sequence ID number
must be 0.
    Data Length: 1-4 characters.
    Data Format:  as in  to .
    Disposition: Mandatory.
    Examples: [1], [1F2C], [2D3], [BB], [FFFE].

7.1.24. Event Type

    Description: An attribute specifying the type of the event
record.
    Purpose: Provides ability to code the type of the recorded event
in electronic format.
    Source: ELD internal calculations.
    Used in: ELD event records; ELD outputs.
    Data Type: ELD recorded and maintained event attribute in
accordance with the type of event being recorded.
    Data Range: 1-7 as described on Table 10.
    Data Length: 1 character.
    Data Format:  as in .
    Disposition: Mandatory.
    Examples: [1], [5], [4], [7].

                Table 10--``Event Type'' Parameter Coding
------------------------------------------------------------------------
                                                            Event type
                       Event type                              code
------------------------------------------------------------------------
A change in driver's duty-status........................               1
An intermediate log.....................................               2
A change in driver's indication of authorized personal                 3
 use of CMV or yard moves...............................
A driver's certification/re-certification of records....               4
A driver's login/logout activity........................               5
CMV's engine power up/shut down activity................               6
A malfunction or data diagnostic detection occurrence...               7
------------------------------------------------------------------------

7.1.25. Exempt Driver Configuration

    Description: A parameter indicating whether the motor carrier's
configured a driver's profile to claim exemption from ELD use.
    Purpose: Provides ability to code the motor carrier indicated
exemption for the driver electronically.
    Source: Motor carrier's configuration for a given driver.
    Used in: ELD outputs.
    Data Type: Motor carrier configured and maintained parameter in
accordance with the qualification requirements listed in Sec.
395.1.
    Data Range: E (exempt) or 0 (number zero).
    Data Length: 1 character.
    Data Format:  as in .
    Disposition: Mandatory.
    Examples: [E], [0].

7.1.26. File Data Check Value

    Description: A hexadecimal ``check'' value calculated in
accordance to procedure outlined in section <IP_ADDRESS> and attached to
each ELD output file.
    Purpose: Provides ability to identify cases where an ELD file
may have been inappropriately modified after its original creation.
    Source: ELD internal.
    Used in: ELD output files.
    Data Type: Calculated by the ELD in accordance with <IP_ADDRESS>.
    Data Range: A number between hexadecimal 0000 (decimal 0) and
hexadecimal FFFF (decimal 65535).
    Data Length: 4 characters.
    Data Format:  as in .
    Disposition: Mandatory.
    Examples: [F0B5], [00CA], [523E].

7.1.27. First Name

    Description: This data element refers to the given name of the
individual holding an ELD account.
    Purpose: Links an individual to the associated ELD account.
    Source: Driver's license for driver accounts; Driver's license
or government-issued ID for support personnel accounts.
    Used in: ELD account profile(s); ELD outputs (display and file).
    Data Type: Entered (during the creation of a new ELD account).
    Data Range: Any alphanumeric combination.
    Data Length: Minimum: 2; Maximum: 30 characters.
    Data Format:  as in  to  where
``C'' denotes a character.
    Disposition: Mandatory for all accounts created on the ELD.
    Example: [John].

7.1.28. Geo-Location

    Description: A descriptive indicator of the CMV position in
terms of a distance and direction to a recognizable location derived
from a GNIS database at a minimum containing all cities, towns and
villages with a population of 5,000 or greater.
    Purpose: Provide recognizable location information on
displayable outputs to users of the ELD.
    Source: ELD internal calculations as specified in section 4.4.2.
    Used in: ELD visual outputs (display, printout).
    Data Type: Identified from the underlying latitude/longitude
coordinates by the ELD.
    Data Range: Contains four segments in one text field; A
recognizable location driven from GNIS database containing--at a
minimum--all cities, towns and villages with a population of 5,000
in text format containing a location name and the State
abbreviation, distance from this location and direction from this
location.
    Data Length: Minimum: 5 Maximum: 60 characters.
    Data Format:
<'mi`>  <' `>  <' `>  where:  must either be <{blank{time} > or
 or  where the--up-to two character number specifies absolute
distance between identified geo-location and event location;
 must either be
<{blank{time} > or  or  or , must represent direction of
event location with respect to the identified geo-location, and must
take a value listed on Table 11;
     must
take values listed on Table 6;  must be the text description of the identified
reference location;
    Overall length of the ``Geo-location'' parameter must not be
longer than 60 characters long.
    Disposition: Mandatory.
    Examples: [2mi ESE IL Darien], [1mi SE TX Dallas], [11mi NNW IN
West Lafayette].

 Table 11--Conventional Compass Rose Direction Coding To Be Used in the
                         Geo-Location Parameter
------------------------------------------------------------------------
                  Direction                         Direction code
------------------------------------------------------------------------
At indicated geo-location...................  {blank{time}
North of indicated geo-location.............  N
North-North East of indicated geo-location..  NNE
North East of indicated geo-location........  NE
East-North East of indicated geo-location...  ENE
East of indicated geo-location..............  E
East-South East of indicated geo-location...  ESE
South East of indicated geo-location........  SE
South-South East of indicated geo-location..  SSE
South of indicated geo-location.............  S
South-South West of indicated geo-location..  SSW
South West of indicated geo-location........  SW
West-South West of indicated geo-location...  WSW
West of indicated geo-location..............  W
West-North West of indicated geo-location...  WNW
North West of indicated geo-location........  NW
North-North West of indicated geo-location..  NNW
------------------------------------------------------------------------

7.1.29. Last Name

    Description: This data element refers to the last name of the
individual holding an ELD account.
    Purpose: Links an individual to the associated ELD account.
    Source: Driver's license for driver accounts; Driver's license
or government-issued ID for support personnel accounts.
    Used in: ELD account profile(s); ELD outputs (display and file).
    Data Type: Entered (during the creation of a new ELD account).
    Data Range: Any alphanumeric combination.
    Data Length: Minimum: 2; Maximum: 30 characters.
    Data Format:  as in  to .
    Disposition: Mandatory for all accounts created on the ELD.
    Example: [Smith].

7.1.30. Latitude

    Description: An angular distance in degrees north and south of
the equator.
    Purpose: In combination with the variable ``Longitude'', this
parameter stamps records requiring a position attribute with a
reference point on the face of the earth.
    Source: ELD's position measurement.
    Used in: ELD events; ELD outputs.
    Data Type: Latitude and Longitude must be automatically captured
by the ELD.
    Data Range: -90.00 to 90.00 in decimal degrees (two decimal
point resolution) in records using conventional positioning
precision; -90.0 to 90.0 in decimal degrees (single decimal point
resolution) in records using reduced positioning precision when
allowed; Latitudes north of the equator must be specified by the
absence of a minus sign (-), preceding the digits designating
degrees; Latitudes south of the Equator must be designated by a
minus sign (-) preceding the digits designating degrees.
    Data Length: 3 to 6 characters,
    Data Format: First character: [<`-'> or <{blank{time} >] then
[ or ]; then <`.'>; then [ or ],
    Disposition: Mandatory.
    Examples: [-15.68], [38.89], [5.07], [-6.11], [-15.7], [38.9],
[5.1], [-6.1].

7.1.31. Line Data Check Value

    Description: A hexadecimal ``check'' value calculated in
accordance to procedure outlined in section <IP_ADDRESS> and attached to
each line of output featuring data at the time of output file being
generated.

    Purpose: Provides ability to identify cases where an ELD output
file may have been inappropriately modified after its original
generation.
    Source: ELD internal.
    Used in: ELD output file.
    Data Type: Calculated by the ELD in accordance with <IP_ADDRESS>.
    Data Range: A number between hexadecimal 00 (decimal 0) and
hexadecimal FF (decimal 255).
    Data Length: 2 characters.
    Data Format:  as in .
    Disposition: Mandatory.
    Examples: [01], [A4], [CC].

7.1.32. Longitude

    Description: An angular distance in degrees measured on a circle
of reference with respect to the zero (or prime) meridian; The prime
meridian runs through Greenwich, England.
    Purpose: In combination with the variable ``Longitude'', this
parameter stamps records requiring a position attribute with a
reference point on the face of the earth.
    Source: ELD's position measurement.
    Used in: ELD events; ELD outputs.
    Data Type: Latitude and Longitude must be automatically captured
by the ELD.
    Data Range: -179.99 to 180.00 in decimal degrees (two decimal
point resolution) in records using conventional positioning
precision; -179.9 to 180.0 in decimal degrees (single decimal point
resolution) in records using reduced positioning precision when
allowed; Longitudes east of the prime meridian must be specified by
the absence of a minus sign (-), preceding the digits designating
degrees of longitude; Longitudes west of the prime meridian must be
designated by minus sign (-) preceding the digits designating
degrees.
    Data Length: 3 to 7 characters
    Data Format: First character: [<`-'> or <{blank{time} >]; then
[,  or ]; then <`.'>; then [ or ].
    Disposition: Mandatory.
    Examples: [-157.81], [-77.03], [9.05], [-0.15], [-157.8], [-
77.0], [9.1], [-0.2].

7.1.33. Malfunction/Diagnostic Code

    Description: A code that further specifies the underlying
malfunction or data diagnostic event.
    Purpose: Enables coding the type of malfunction and data
diagnostic event to cover the standardized set in Table 4.
    Source: ELD internal monitoring.
    Used in: ELD events; ELD outputs.
    Data Type: Recorded by ELD when malfunctions and data diagnostic
events are set or reset.
    Data Range: As specified in Table 4.
    Data Length: 1 character
    Data Format:
    Disposition: Mandatory
    Examples: [1], [5], [P], [L].

7.1.34. Malfunction Indicator Status

    Description: This is a Boolean indicator identifying whether the
used ELD unit has an active malfunction set at the time of event
recording.
    Purpose: Documents the snapshot of ELD's malfunction status at
the time of an event recording.
    Source: ELD internal monitoring functions.
    Used in: ELD events; ELD outputs.
    Data Type: Internally monitored and managed.
    Data Range: 0 (no active malfunction) or 1 (at least one active
malfunction).
    Data Length: 1 character.
    Data Format:  as in .
    Disposition: Mandatory.
    Examples: [0] or [1].

7.1.35. Multiday Basis Used

    Description: This data element refers to the multiday basis (7
or 8 days) used by the motor carrier to compute cumulative duty
hours.
    Purpose: Provides ability to apply the HOS rules accordingly.
    Source: Motor carrier.
    Used in: ELD account profile; ELD outputs.
    Data Type: Entered by the motor carrier during account creation
process.
    Data Range: 7 or 8.
    Data Length: 1 character.
    Data Format:  as in .
    Disposition: Mandatory.
    Examples: [7], [8].

7.1.36. Order Number

    Description: A continuous integer number assigned in the forming
of a list, starting at 1 and incremented by 1 for each unique item
on the list.
    Purpose: Allows for more compact report file output generation
avoiding repetitious use of CMV identifiers and usernames affected
in records.
    Source: ELD internal.
    Used in: ELD outputs, listing of users and CMVs referenced in
ELD logs.
    Data Type: Managed by ELD.
    Data Range: Integer between 1 and 99.
    Data Length: 1-2 characters.
    Data Format:  as in  or .
    Disposition: Mandatory.
    Examples: [1], [5], [11], [28].

7.1.37. Output File Comment

    Description: A textual field that may be populated with
information pertaining to the created ELD output file; An authorized
safety official may provide a key phrase or code to be included in
the output file comment, which may be used to link the requested
data to an inspection, inquiry or other enforcement action; If
provided to the driver by an authorized safety official, it must be
entered into the ELD or its support system and included in the
exchanged dataset as specified.
    Purpose: The output file comment field provides an ability to
link a submitted data to an inspection, inquiry or other enforcement
action, if deemed necessary; Further, it may also serve a purpose to
link a dataset to a vehicle, driver, carrier and/or ELD which may
participate in voluntary future programs that may involve exchange
of ELD data.
    Source: Enforcement personnel or driver or motor carrier.
    Used in: ELD outputs.
    Data Type: If provided, output file comment is entered or
appended to the ELD dataset prior to submission of ELD data to
enforcement.
    Data Range: Blank or any alphanumeric combination specified and
provided by an authorized safety official.
    Data Length: 0-60 characters.
    Data Format: <{blank{time} >, or  thru .
    Disposition: Mandatory.
    Examples: [ ], [3BHG701015], [113G1EFW02], [7353930].

7.1.38. Shipping Document Number

    Description: Shipping document number the motor carrier uses in
their system and dispatch documents.
    Purpose: Links ELD data to the shipping records; Makes ELD
dataset consistent with Sec.  395.8 requirements.
    Source: Motor Carrier.
    Used in: ELD outputs.
    Data Type: Entered in the ELD by the authenticated driver or
populated by motor carrier's extended ELD support system and
verified by the driver.
    Data Range: Any alphanumeric combination.
    Data Length: 0-40 characters.
    Data Format: <{blank{time} >, or  thru .
    Disposition: Mandatory if a shipping number is used on motor
carrier's system.
    Examples: [], [B 75354], [FX334411707].

7.1.39. Time

    Description: In combination with the variable ``Date'', this
parameter stamps records with a reference in time; Even though date
and time must be captured in UTC, event records must use date and
time converted to the time zone in effect at the driver's home
terminal as specified in section 4.4.3.
    Purpose: Provides ability to record the instance of recorded
events.
    Source: ELD's converted time measurement.
    Used in: ELD events; ELD outputs.
    Data Type: UTC time must be automatically captured by ELD; Time
in effect at the driver's home terminal must be calculated as
specified in section 4.4.3.
    Data Range: Any valid date combination expressed in
format where ``HH'' refers to hours of the day, ``DD'' refers to
minutes and ``SS'' refers to seconds.
    Data Length: 6 characters.
    Data Format:  where  must be between 00 and 23,
and  must be between 00 and 59.
    Disposition: Mandatory.
    Examples: [070111], [001259], [151522], [230945].

7.1.40. Time Zone Offset From UTC

    Description: This data element refers to the offset in time
between UTC time and the time standard in effect at the driver's
home terminal.
    Purpose: Establishes the ability to link records stamped with
local time to a universal reference.
    Source: Calculated from measured variable <{UTC{time}  Time> and
<{Time Standard in Effect at driver's home terminal{time}  Time>;
Maintained together with ``24-hour Period Starting Time'' parameter
by the motor carrier or tracked automatically by ELD.

    Used in: ELD account profile; ELD event: Driver's certification
of own records.
    Data Type: Programmed or populated on the ELD during account
creation and maintained by the motor carrier or ELD to reflect true
and accurate information for drivers. This parameter must adjust for
Daylight Saving Time changes in effect at the driver's home
terminal.
    Data Range: 04 to 11; Omit sign.
    Data Length: 2 characters.
    Data Format:  as in  where ``HH''
refer to hours in difference.
    Disposition: Mandatory.
    Examples: [04], [05], [10].

7.1.41. Trailer Number(s)

    Description: This data element refers to the identifier(s) the
motor carrier uses for the trailers in their normal course of
business.
    Purpose: Identifies the trailer(s) a driver operates while a
driver's ELD records are recorded; Makes ELD records consistent with
Sec.  395.8 which requires the trailer number(s) to be included on
the form.
    Source: Unique trailer identifiers a motor carrier uses in their
normal course of business and include on dispatch documents or the
license number and licensing State of each towed unit; Trailer
number(s) must be updated each time hauled trailers change.
    Data Type: Automatically captured by the ELD or populated by
motor carrier's extended ELD system or entered by the driver; Must
be updated each time the hauled trailer(s) change.
    Data Range: Any alphanumeric combination.
    Data Length: Minimum: blank; Maximum: 32 characters (3 trailer
numbers each maximum 10 characters long, separated by spaces).
    Data Format: Trailer numbers; Separated by space in case of
multiple trailers hauled at one time; Field to be left ``blank'' for
non-combination vehicles (such as a straight truck or bobtail
tractor).
    1{time} ><' `>2{time} > <' `>3{time} > as in <{blank{time} > to .
    Disposition: Mandatory when operating combination vehicles.
    Examples: [987], [00987 PP2345], [BX987 POP712 10567], [TX12345
LA22A21], [ ].

7.1.42. Vehicle Miles

    Description: Vehicle miles refer to the distance traveled using
the CMV in whole miles; This parameter is a placeholder for
<{Total{time}  Vehicle Miles> which refers to the odometer reading
and used in recording ``engine power on'' and ``engine shut down''
events, and also for <{Accumulated{time}  Vehicle Miles> which
refers to the accumulated miles in the given ignition power on cycle
and used in the recording of all other events.
    Purpose: Provides ability to track distance traveled while
operating the CMV in each duty status. Total miles traveled within a
24-hour period is a required field in Sec.  395.8.
    Source: ELD measurement or sensing.
    Used in: ELD events; ELD outputs.
    Data Type: Acquired from the engine ECM or a comparable other
source as allowed in section <IP_ADDRESS>.
    Data Range: For <{Total{time}  Vehicle Miles>, range is between
0 and 9,999,999;
    For <{Accumulated{time}  Vehicle Miles>, range is between 0 and
9,999.
    Data Length: 1-7 characters.
    Data Format:  as in  to .
    Disposition: Mandatory.
    Examples: [99], [1004566], [0], [422].

    Issued under authority delegated in 49 CFR 1.87 on: March 11,
2014.
 Anne S. Ferro,
 Administrator.
[FR Doc. 2014-05827 Filed 3-27-14; 8:45 am]
BILLING CODE 4910-EX-P


[Federal Register Volume 88, Number 212 (Friday, November 3, 2023)]
[Proposed Rules]
[Pages 75513-75517]
[FR Doc No: 2023-24311]

========================================================================
Proposed Rules
                                                Federal Register
________________________________________________________________________

This section of the FEDERAL REGISTER contains notices to the public of
the proposed issuance of rules and regulations. The purpose of these
notices is to give interested persons an opportunity to participate in
the rule making prior to the adoption of the final rules.

========================================================================

Federal Register / Vol. 88, No. 212 / Friday, November 3, 2023 /
Proposed Rules

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

14 CFR Part 25

[Docket No. FAA-2021-1032; Notice No. 25-23-03-SC]

Special Conditions: Airbus Model A321neo XLR Airplanes; Flight
Envelope Protection, Icing and Non-Icing Conditions; High Incidence
Protection.

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Notice of proposed special conditions.

-----------------------------------------------------------------------

SUMMARY: This action proposes special conditions for the Airbus Model
A321neo XLR airplane. The airplane will have a novel or unusual design
feature when compared to the state of technology envisioned in the
airworthiness standards for transport-category airplanes. This design
feature is associated with flight-envelope protections, in icing and
non-icing conditions, that use high-incidence protection and an alpha-
floor system to automatically advance throttles when the airplane angle
of attack reaches a predetermined value. The applicable airworthiness
regulations do not contain adequate or appropriate safety standards for
this design feature. These special conditions contain the additional
safety standards that the Administrator considers necessary to
establish a level of safety equivalent to that established by the
existing airworthiness standards.

DATES: Send comments on or before December 4, 2023.

ADDRESSES: Send comments identified by Docket No. FAA-2021-1032 using
any of the following methods:
    Federal eRegulations Portal: Go to https://www.regulations.gov/ and
follow the online instructions for sending your comments
electronically.
    Mail: Send comments to Docket Operations, M-30, U.S. Department of
Transportation (DOT), 1200 New Jersey Avenue SE, Room W12-140, West
Building Ground Floor, Washington, DC 20590-0001.
    Hand Delivery or Courier: Take comments to Docket Operations in
Room W12-140 of the West Building Ground Floor at 1200 New Jersey
Avenue SE, Washington, DC, between 9 a.m. and 5 p.m., Monday through
Friday, except Federal holidays.
    Fax: Fax comments to Docket Operations at<PHONE_NUMBER>.
    Docket: Background documents or comments received may be read at
https://www.regulations.gov/ at any time. Follow the online
instructions for accessing the docket or go to Docket Operations in
Room W12-140 of the West Building Ground Floor at 1200 New Jersey
Avenue SE, Washington, DC, between 9 a.m. and 5 p.m., Monday through
Friday, except Federal holidays.

FOR FURTHER INFORMATION CONTACT: Troy Brown, Performance and
Environment Unit, AIR-621A, Technical Policy Branch, Policy and
Standards Division, Aircraft Certification Service, Federal Aviation
Administration, 1801 S. Airport Rd., Wichita, KS 67209-2190; telephone
and fax<PHONE_NUMBER>; email [email protected].

SUPPLEMENTARY INFORMATION:

Comments Invited

    The FAA invites interested people to take part in this rulemaking
by sending written comments, data, or views. The most helpful comments
reference a specific portion of the proposed special conditions,
explain the reason for any recommended change, and include supporting
data.
    Certification of the Airbus Model A321neo XLR airplane is currently
scheduled for December 2023. The substance of these special conditions,
in all material respects, has been subject to the notice and public-
comment procedure in several prior instances. Therefore, because a
delay would significantly affect the applicant's installation of the
novel or unusual design feature, and delay certification of the
airplane, the FAA is reducing the public-comment period to 30 days.
    The FAA will consider all comments received by the closing date for
comments, and will consider comments filed late if it is possible to do
so without incurring delay. The FAA may change these special conditions
based on the comments received.

Privacy

    Except for Confidential Business Information (CBI) as described in
the following paragraph, and other information as described in title
14, Code of Federal Regulations (14 CFR) 11.35, the FAA will post all
comments received without change to https://www.regulations.gov/,
including any personal information you provide. The FAA will also post
a report summarizing each substantive verbal contact received about
these special conditions.

Confidential Business Information

    Confidential Business Information (CBI) is commercial or financial
information that is both customarily and actually treated as private by
its owner. Under the Freedom of Information Act (FOIA) (5 U.S.C. 552),
CBI is exempt from public disclosure. If your comments responsive to
these special conditions contain commercial or financial information
that is customarily treated as private, that you actually treat as
private, and that is relevant or responsive to these special
conditions, it is important that you clearly designate the submitted
comments as CBI. Please mark each page of your submission containing
CBI as ``PROPIN.'' The FAA will treat such marked submissions as
confidential under the FOIA, and the indicated comments will not be
placed in the public docket of these special conditions. Send
submissions containing CBI to the individual listed in the For Further
Information Contact section below. Comments the FAA receives, which are
not specifically designated as CBI, will be placed in the public docket
for these special conditions.

Background

    On September 16, 2019, Airbus applied for an amendment to Type
Certificate No. A28NM to include the new Model A321neo XLR airplane.
These airplanes are twin-engine, transport-category airplanes with
seating for 244 passengers and a maximum take-off weight of 222,000
pounds.

Type Certification Basis

    Under the provisions of 14 CFR 21.101, Airbus must show that the
Model A321neo XLR airplane meets the applicable provisions of the
regulations

listed in Type Certificate No. A28NM, or the applicable regulations in
effect on the date of application for the change, except for earlier
amendments as agreed upon by the FAA.
    If the Administrator finds that the applicable airworthiness
regulations (e.g., 14 CFR part 25) do not contain adequate or
appropriate safety standards for the Airbus Model A321neo XLR airplanes
because of a novel or unusual design feature, special conditions are
prescribed under the provisions of Sec.  21.16.
    Special conditions are initially applicable to the model for which
they are issued. Should the type certificate for that model be amended
later to include any other model that incorporates the same novel or
unusual design feature, or should any other model already included on
the same type certificate be modified to incorporate the same novel or
unusual design feature, these special conditions would also apply to
the other model under Sec.  21.101.
    In addition to the applicable airworthiness regulations and special
conditions, the Airbus Model A321neo XLR airplane must comply with the
fuel-vent and exhaust-emission requirements of 14 CFR part 34, and the
noise-certification requirements of 14 CFR part 36.
    The FAA issues special conditions, as defined in Sec.  11.19, in
accordance with Sec.  11.38, and they become part of the type
certification basis under 14 CFR 21.101.

Novel or Unusual Design Features

    The Airbus Model A321neo XLR airplane will incorporate the
following novel or unusual design feature:
    Flight-envelope protections, in icing and non-icing conditions,
that use high- incidence protection and an alpha-floor function to
automatically advance throttles when the airplane angle of attack (AoA)
reaches a predetermined value.

Discussion

    The current airworthiness standards do not contain adequate safety
standards for the high-incidence protection system and the alpha-floor
system for the Airbus Model A321neo XLR series airplanes. This is
because the current standards were designed for more traditional
electronic flight control systems (EFCS), which involve less advanced
envelope protections, such as stick shakers and pushers. These special
conditions address the more advanced flight envelope protections,
including icing and non-icing conditions, that are part of the EFCS
design of the A321neo XLR airplane.
    The high-incidence protection system prevents the airplane from
stalling and, therefore, the stall warning system is not needed during
normal flight conditions. However, during failure conditions, which are
not shown to be extremely improbable, the requirements of 14 CFR 25.203
and 25.207 apply, although slightly modified. If there are failures not
shown to be extremely improbable, the flight characteristics at the
angle-of-attack for CLMAX must be suitable in the
traditional sense, and stall warning must be provided in a conventional
manner-. These special conditions address the need for modification
during icing conditions and non-icing conditions.
    The alpha-floor function automatically advances the throttles on
the operating engines under flight circumstances of low speed if the
airplane reaches a predetermined high AoA. This function is intended to
provide increased climb capability.
    These special conditions address these novel or unusual design
features on the Airbus Model A321neo XLR and contain the additional
safety standards that the Administrator considers necessary to
establish a level of safety equivalent to that established by the
existing airworthiness standards.

Applicability

    As discussed above, these special conditions apply to Airbus Model
A321neo XLR airplane. Should Airbus apply later for a change to the
type certificate to include another model incorporating the same novel
or unusual design feature, the special conditions would apply to that
model as well.

Conclusion

    This action affects only certain novel or unusual design features
on one model series of airplanes. It is not a rule of general
applicability.

List of Subjects in 14 CFR Part 25

    Aircraft, Aviation safety, Reporting and recordkeeping
requirements.

Authority Citation

    The authority citation for these special conditions is as follows:

    Authority: 49 U.S.C. 106(f), 106(g), 40113, 44701, 44702, and
44704.

The Proposed Special Conditions

    Accordingly, the Federal Aviation Administration (FAA) proposes the
following special conditions as part of the type certification basis
for Airbus Model A321neo XLR airplane. These special conditions are
issued in lieu of the paragraphs of 14 CFR part 25 referenced below.

Foreword

    In the following paragraphs, ``In icing conditions'' means with the
ice accretions, relevant for the flight phase, as defined in part 25,
amendment 121, appendix C.

(a) Definitions

    These special conditions address novel or unusual design features
of the Airbus A321neo XLR and use terminology that does not appear in
part 25. For the purpose of these special conditions, the following
terms describe certain aspects of these novel or unusual design
features:

High-Incidence Protection System Angle-of-Attack Limiting Function

    A system that operates directly and automatically on the airplane's
flying controls to limit the maximum angle of attack (AoA) that can be
attained to a value below that at which an aerodynamic stall would
occur.

Alpha-Floor System

    A system that automatically increases thrust on the operating
engines when AoA increases through a particular value.

Alpha Limit

    The maximum angle of attack at which the airplane stabilizes with
the high-incidence protection system operating and the longitudinal
control held on its aft stop.

VCLmax

    An airspeed calculated from a variety of factors, including load
factor normal to the flight path at VCLmax, airplane gross
weight, aerodynamic reference wing area, and dynamic pressure.

Vmin

    The minimum steady flight speed in the airplane configuration under
consideration with the high-incidence protection system operating.

Vmin1g

    Vmin corrected to 1g conditions. This is the minimum
calibrated airspeed at which the airplane can develop a lift force
normal to the flight path and equal to its weight when at an angle of
attack not greater than that determined for Vmin.

(b) Capability and Reliability of the High-Incidence Protection System

    Acceptable capability and reliability of the high-incidence
protection system can be established by flight test, simulation, and
analysis, as appropriate.

The capability and reliability required are as follows:
    (1) It must not be possible, during pilot-induced maneuvers, to
encounter a stall; and handling characteristics must be acceptable, as
required by condition (e) of these Special Conditions.
    (2) The airplane must be protected against stalling due to the
effects of wind-shears and gusts at low speeds as required by condition
(f) of these Special Conditions.
    (3) The ability of the high-incidence protection system to
accommodate any reduction in stalling incidence must be verified in
icing conditions.
    (4) The high-incidence protection system must be provided in each
abnormal configuration of the high-lift devices that are likely to be
used in-flight following system failures.
    (5) The reliability of the system and the effects of failures must
be acceptable in accordance with Sec.  25.1309.

(c) Minimum Steady Flight Speed and Reference Stall Speed

    In lieu of Sec.  25.103, minimum steady flight speed and reference
stall speed, the following requirements apply:
    (1) The minimum steady flight speed, Vmin, is the final
stabilized calibrated airspeed obtained when the airplane is
decelerated until the longitudinal control is on its stop in such a way
that the entry rate does not exceed 1 knot per second.
    (2) The minimum steady flight speed, Vmin, must be
determined in icing and non-icing conditions with:
    (i) The high-incidence protection system operating normally;
    (ii) Idle thrust and alpha-floor system inhibited;
    (iii) All combinations of flaps setting and landing gear position
for which Vmin is required to be determined;
    (iv) The weight used when the reference stall speed,
VSR, is being used as a factor to determine compliance with
a required performance standard;
    (v) The most unfavorable center of gravity allowable; and
    (vi) The airplane trimmed for straight flight at a speed achievable
by the automatic trim system.
    (3) The 1g minimum steady flight speed, Vmin1g, is the
minimum calibrated airspeed at which the airplane can develop a lift
force (normal to the flight path) equal to its weight, while at an
angle of attack not greater than that at which the minimum steady
flight speed of condition (c)(1), above, was determined. It must be
determined in icing and non-icing conditions.
    (4) The reference stall speed, VSR, is a calibrated
airspeed the applicant defines. VSR may not be less than a
1g stall speed. VSR must be determined in non-icing
conditions and expressed as:
[GRAPHIC] [TIFF OMITTED] TP03NO23.032

Where:

VCLmax = Calibrated airspeed obtained when the load
factor corrected lift coefficient (nzw W/qS) is first a
maximum during the maneuver prescribed in condition (c)(5)(viii) of
these Special Conditions;
nzw = Load factor normal to the flight path at
VCLmax;
W = Airplane gross weight;
S = Aerodynamic reference wing area; and
q = Dynamic pressure.

    (5) VCLmax is determined in non-icing conditions with:
    (i) Engines idling, or, if that resultant thrust causes an
appreciable decrease in stall speed, not more than zero thrust at the
stall speed;
    (ii) The airplane in other respects (such as flaps and landing
gear) in the condition existing in the test or performance standard in
which VSR is being used;
    (iii) The weight used when VSR is being used as a factor
to determine compliance with a required performance standard;
    (iv) The center of gravity position that results in the highest
value of reference stall speed;
    (v) The airplane trimmed for straight flight at a speed achievable
by the automatic trim system, but not less than 1.13 VSR and
not greater than 1.3 VSR;
    (vi) Alpha-floor system inhibited; and
    (vii) The high-incidence protection system adjusted, at the option
of the applicant, to allow higher incidence than is possible with the
normal production system.
    (viii) Starting from the stabilized trim condition, apply the
longitudinal control to decelerate the airplane so that the speed
reduction does not exceed 1 knot per second.

(d) Stall Warning

    In lieu of Sec.  25.207, the following requirements apply:
    (1) Normal Operation.
    If the capabilities of the high-incidence protection system are
met, then condition (b) of these Special Conditions are satisfied.
These conditions provide an equivalent level of safety to Sec.  25.207,
Stall Warning, so the provision of an additional, unique warning device
is not required.
    (2) High-Incidence Protection System Failure.
    (i) In non-icing conditions, following failures of the high-
incidence protection system, not shown to be extremely improbable, such
that the capability of the system no longer satisfies conditions
(b)(1), (2), and (3) of these Special Conditions, stall warning must be
provided in accordance with Sec.  25.207(a), (b), and (f).
    (ii) In icing conditions, after a failure leading to the loss of
the high-incidence protection system, a safety margin not less than 3
percent or 3 knots between stall warning and stall must be maintained.

(e) Handling Characteristics at High Incidence

    (1) High Incidence Handling Demonstrations.
    In lieu of Sec.  25.201: High-incidence handling demonstration in
icing and non-icing conditions:
    (i) Maneuvers to the limit of the longitudinal control, in the nose
up sense, must be demonstrated in straight flight and in 30-degree
banked turns with:
    (A) The high-incidence protection system operating normally.
    (B) Initial power conditions of:
    (1) Power off.
    (2) The power necessary to maintain level flight at 1.5
VSR1, where VSR1 is the reference stall speed
with flaps in approach position, the landing gear retracted, and
maximum landing weight.
    (C) Alpha-floor system operating normally unless more severe
conditions are achieved with inhibited alpha floor.
    (D) Flaps, landing gear, and deceleration devices in any likely
combination of positions.
    (E) Representative weights within the range for which certification
is requested; and
    (F) The airplane trimmed for straight flight at a speed achievable
by the automatic trim system.
    (ii) The following procedures must be used to show compliance in
non-icing and icing conditions:
    (A) Starting at a speed sufficiently above the minimum steady
flight speed to ensure that a steady rate of speed reduction can be
established, apply the longitudinal control so that the speed reduction
does not exceed 1 knot per second until the control reaches the stop.
    (B) The longitudinal control must be maintained at the stop until
the airplane has reached a stabilized flight condition, and must then
be recovered through normal recovery techniques.
    (C) Maneuvers with increased deceleration rates:
    (1) In non-icing conditions, the requirements must also be met with
increased rates of entry to the incidence limit, up to the maximum rate
achievable.

    (2) In icing conditions, with the anti-ice system working normally,
the requirements must also be met with increased rates of entry to the
incidence limit up to 2 knots per second.
    (D) Maneuvers with ice accretion prior to operation of the normal
anti-ice system: With the ice accretion prior to operation of the
normal anti-ice system, the requirement must also be met in
deceleration at 1 knot per second up to full back stick maintained for
at least 3 seconds before normal recovery is performed (requirement to
be met with and without alpha floor operating).
    (2) Characteristics in High-Incidence Maneuvers.
    In lieu of Sec.  25.203: Characteristics in High Incidence.
    In icing and non-icing conditions:
    (i) Throughout maneuvers with a rate of deceleration of not more
than 1 knot per second, both in straight flight and in 30-degree banked
turns, the airplane's characteristics must be as follows:
    (A) The airplane must not exhibit abnormal nose-up pitching.
    (B) The airplane must not exhibit uncommanded nose-down pitching,
which would be indicative of stall. However, reasonable attitude
changes associated with stabilizing the incidence at alpha limit, as
the longitudinal control reaches the stop, would be acceptable.
    (C) The airplane must not exhibit uncommanded lateral or
directional motion, and the pilot must retain good lateral and
directional control through conventional use of the controls,
throughout the maneuver.
    (D) Buffeting:
    (1) In non-icing conditions, the airplane must not exhibit
buffeting of a magnitude and severity that would act as a deterrent
from completing the maneuver specified in condition (e)(1)(i) of these
Special Conditions.
    (2) In icing conditions, the airplane may exhibit buffeting of a
stronger magnitude and severity than in non-icing conditions, provided
that the airplane is demonstrated to be free from excessive vibration
and buffeting over the range of speeds adequate for normal operation.
    (ii) In maneuvers with increased rates of deceleration, some
degradation of characteristics are acceptable, associated with a
transient excursion beyond the stabilized alpha limit. However, the
airplane must not exhibit dangerous characteristics, nor
characteristics that would deter the pilot from holding the
longitudinal control on the stop for a period of time appropriate to
the maneuver.
    (iii) The pilot must always be able to reduce incidence through
conventional use of the controls.
    (iv) The rate at which the airplane can be maneuvered from trim
speeds associated with scheduled operating speeds such as V2
and Vref, up to alpha limit, must not be unduly damped or be
significantly slower than can be achieved on conventionally controlled
transport airplanes.
    (3) Characteristics up to VCLmax.
    Maneuvers with a rate of deceleration of not more than 1 knot per
second, up to the angle of attack at which VCLmax was
obtained as defined in condition (c)(4) of these Special Conditions,
must be demonstrated in straight flight and in 30-degree banked turns
with:
    (i) The high-incidence protection system deactivated or adjusted,
at the option of the applicant, to allow higher incidence than is
possible with the normal production system,
    (ii) Alpha-floor system inhibited,
    (iii) Engines idling,
    (iv) Flaps and landing gear in any likely combination of positions,
and
    (v) The airplane trimmed for straight flight at a speed achievable
by the automatic trim system.
    During such maneuvers, the airplane must not exhibit dangerous
characteristics; the pilot must always be able to reduce angle of
attack by conventional use of the controls. The pilot must retain good
lateral and directional control, by conventional use of the controls,
throughout the maneuver.

(f) Atmospheric Disturbances

    Operation of the high-incidence protection system must not
adversely affect airplane control during expected levels of atmospheric
disturbances, nor impede the application of recovery procedures in case
of wind shear. This must be demonstrated in non-icing conditions only,
and must allow for drawing conclusion for icing conditions without
further demonstration.

(g) Speed Associated With Other Requirements

    The design must meet the following modified requirements:
    a. Section 25.145(a): Vmin in lieu of ``stall
identification.''
    b. Section 25.145(b): Vmin in lieu of Vsw.
    c. Section 25.1323(d): ``From 1.23 VSR to
Vmin'' in lieu of ``1.23 VSR to stall warning
speed'' and ``speeds below Vmin'' in lieu of ``speeds below
stall warning.''

(h) Alpha Floor

    In icing and non-icing conditions, the alpha-floor setting must be
such that the airplane can be flown at the speeds and bank angles
specified in Sec.  25.143(h). The applicant also must show that the
alpha-floor setting does not interfere with normal maneuvering of the
airplane. In addition, the airplane must exhibit no alpha-floor
triggering unless appropriate when the airplane is flown in usual
operational maneuvers and in turbulence.

(i) Proof of Compliance

    In addition to the requirements in Sec.  25.21(b), the following
requirement applies:
    The flying qualities will be evaluated at the most unfavorable
center-of-gravity (CG) position.

(j) Performance in Icing Conditions

    (1) Take-off
    In lieu of compliance with Sec.  25.105(a)(2)(i), the following
special conditions apply:
    (a) In icing conditions, if in the configuration used in showing
compliance with Sec.  25.121(b), and with the most critical of the
``Take-off Ice'' accretion(s) defined in 14 CFR part 25, amendment 121,
appendix C:
    (i) The V2 speed scheduled in non-icing conditions does
not provide the maneuvering capability specified in Sec.  25.143(h) for
the take-off configuration.

    Note: This requirement does not apply if the Vmin1g
is increased in icing conditions, with the ``Take-off Ice''
accretion defined in part 25, amendment 121, appendix C, by less
than 2.5 knots or 2.5 percent, whichever is greater.

    (2) Climb: one-engine inoperative.
    In lieu of compliance with Sec.  25.121(b)(2)(ii)(A), the following
special conditions apply:
    (a) In icing conditions, with the most critical of the take-off ice
accretion(s) defined in appendix C, if in the configuration used to
show compliance with Sec.  25.121(b) with this take-off ice accretion:
    (i) The V2 speed scheduled in non-icing conditions does
not provide the maneuvering capability specified in Sec.  25.143(h),
for the take-off configuration.

    Note:  This requirement does not apply if the Vmin1g
is increased in icing conditions, with the ``Take-off Ice''
accretion defined in 14 CFR part 25, amendment 121, appendix C, by
less than 2.5 knots or 2.5 percent, whichever is greater.

    In lieu of compliance with Sec.  25.121(c)(2)(ii)(A) and (B), the
following special conditions apply:
    (a) In icing conditions, with the most critical of the final take-
off ice accretion(s) defined in appendix C, if in

the configuration used to show compliance with Sec.  25.121(b) with the
take-off ice accretion used to show compliance with Sec.
25.111(c)(5)(i):
    (i) The VFTO (final take-off speed) scheduled in non-
icing conditions does not provide the maneuvering capability, specified
in Sec.  25.143(h), for the en-route configuration.

    Note:  This requirement does not apply if the Vmin1g
is increased in icing conditions, with the ``Final Take-off Ice''
accretion defined in 14 CFR part 25, amendment 121, appendix C, by
less than 2.5 knots or 2.5 percent, whichever is greater.

    (ii) The degradation of the gradient of climb, determined in
accordance with Sec.  25.121(b), with the take-off ice accretion used
in showing compliance with Sec.  25.111(c)(5)(i), is greater than one-
half of the applicable actual-to-net take-off flight path gradient
reduction defined in Sec.  25.115(b);
    In lieu of compliance with 25.121(d)(2)(ii), the following special
conditions apply:
    (a) In icing conditions, with the most critical of the approach ice
accretion(s) defined in 14 CFR part 25, amendment 121, appendix C, as
applicable, in a configuration corresponding to the normal all-engines-
operating procedure, the Vmin1g for this configuration does
not exceed 110 percent of the Vmin1g for the related all-
engines-operating landing configuration in icing conditions, with a
climb speed established with normal landing procedures, but not more
than 1.4 VSR (VSR determined in non-icing
conditions).
    (3) En-route flight paths.
    In lieu of compliance with 25.123(b)(2)(i), the following special
conditions apply:
    (a) In icing conditions with the most critical of the en-route ice
accretion(s) defined in 14 CFR part 25, amendment 121, appendix C, if:
    (i) The VFTO speed scheduled in non-icing conditions
does not provide the maneuvering capability, specified in Sec.
25.143(h), for the en-route configuration.

    Issued in in Kansas City, Missouri, on October 27, 2023.
Patrick R. Mullen,
Manager, Technical Policy Branch, Policy and Standards Division,
Aircraft Certification Service.
[FR Doc. 2023-24311 Filed 11-2-23; 8:45 am]
BILLING CODE 4910-13-P