Page Range | 23563-24008 | |
FR Document |
Page and Subject | |
---|---|
81 FR 23755 - Sunshine Act Meetings | |
81 FR 23757 - Sunshine Act; Notice of a Matter To Be Added to the Agenda for Consideration at an Agency Meeting | |
81 FR 23744 - Sunshine Act Meetings | |
81 FR 23700 - Notification of a Public Teleconference of the Science and Information Subcommittee | |
81 FR 23746 - Temporary Road Closure on Public Lands in Owyhee County, ID | |
81 FR 23666 - Resource Management Planning | |
81 FR 23683 - Applications for New Awards; Magnet Schools Assistance Program | |
81 FR 23801 - Notice of Opportunity for Public Comment on a Property Swap at Augusta State Airport in Augusta, ME | |
81 FR 23680 - Pacific Fishery Management Council; Public Meeting | |
81 FR 23678 - Fisheries of the South Atlantic; South Atlantic Fishery Management Council and Mid-Atlantic Fishery Management Council; Public Meeting; Correction | |
81 FR 23705 - Agency Information Collection Activities: Proposed Collection; Comment Request | |
81 FR 23761 - Tennessee Valley Authority; Watts Bar Nuclear Plant, Unit 1; Application and Amendment to Facility Operating License; Correction | |
81 FR 23702 - Federal Travel Regulation (FTR); Relocation Allowances-Relocation Income Tax (RIT) Allowance Tables | |
81 FR 23762 - Steam Generator Materials and Design | |
81 FR 23758 - Guidance for Closure of Activities Related to Recommendation 2.1, Flooding Hazard Reevaluation | |
81 FR 23747 - Outer Continental Shelf (OCS), Gulf of Mexico, Oil and Gas Lease Sales for 2017-2022 MMAA104000 | |
81 FR 23762 - Request for a License To Import Radioactive Waste | |
81 FR 23761 - Request for a License To Export Radioactive Waste | |
81 FR 23676 - Diamond Sawblades and Parts Thereof From the People's Republic of China: Rescission of Antidumping Duty Administrative Review in Part; 2014-2015 | |
81 FR 23675 - Steel Concrete Reinforcing Bar From the Republic of Turkey: Notice of Partial Rescission of Countervailing Duty Administrative Review, 2014 | |
81 FR 23704 - Agency Information Collection Activities: Submission for OMB Review; Comment Request | |
81 FR 23682 - Privacy Act of 1974; System of Records | |
81 FR 23754 - Information Collection; Request for Public Comments | |
81 FR 23604 - Special Local Regulation; Regattas and Marine Parades in the COTP Lake Michigan Zone-Chinatown Chamber of Commerce Dragon Boat Race, Chicago, IL | |
81 FR 23757 - Proposal Review Panel for Materials Research; Notice of Meeting | |
81 FR 23700 - Environmental Impact Statements; Notice of Availability | |
81 FR 23683 - Strategic Environmental Research and Development Program, Scientific Advisory Board; Notice of Federal Advisory Committee Meeting | |
81 FR 23758 - Proposal Review Panel for Materials Research; Notice of Meeting | |
81 FR 23701 - Notice to All Interested Parties of the Termination of the Receivership of 10281, Independent National Bank, Ocala, FL | |
81 FR 23799 - Culturally Significant Objects Imported for Exhibition Determinations: “The Brothers Le Nain: Painters of Seventeenth-Century France” Exhibition | |
81 FR 23798 - Culturally Significant Objects Imported for Exhibition Determinations: “Karel Appel: A Gesture of Color-Paintings and Sculptures, 1947-2004” Exhibition | |
81 FR 23798 - Culturally Significant Object Imported for Exhibition Determinations: “Medieval Permanent Collection Galleries” Exhibition | |
81 FR 23798 - Culturally Significant Objects Imported for Exhibition Determinations: “Moholy-Nagy: Future Present” Exhibition | |
81 FR 23798 - Department of State FY 2015 Service Contract Inventory | |
81 FR 23702 - Agency Forms Undergoing Paperwork Reduction Act Review | |
81 FR 23700 - 63SU 8ME LLC; Supplemental Notice That Initial Market-Based Rate Filing Includes Request for Blanket Section 204 Authorization | |
81 FR 23697 - Combined Notice of Filings | |
81 FR 23748 - Notice of Proposed Information Collection; Request for Comments for 1029-0120 | |
81 FR 23796 - Oklahoma Disaster #OK-00102 | |
81 FR 23797 - Mississippi Disaster Number MS-00084 | |
81 FR 23797 - Illinois Disaster #IL-00048 | |
81 FR 23694 - Appliance Standards and Rulemaking Federal Advisory Committee | |
81 FR 23694 - Orders Granting Authority To Import and Export Natural Gas, To Import and Export Liquefied Natural Gas, and To Vacate Authorization During March 2016 | |
81 FR 23680 - Procurement List; Additions and Deletions | |
81 FR 23682 - Procurement List; Proposed Deletions | |
81 FR 23708 - Announcement of the Award a Single-Source Program Expansion Supplement Grant to BCFS Health and Human Services in San Antonio, TX | |
81 FR 23751 - Agency Information Collection Activities; Comment Request; Youthful Offender Grants Management Information System, (OMB Control No. 1205-0513) Extension With Revisions | |
81 FR 23752 - Program Reporting and Performance Standards System for Indian and Native American Programs Under Title I, Section 166 of the Workforce Innovation and Opportunity Act (WIOA), Extension With Revision; OMB Control No. 1205-0422 | |
81 FR 23753 - Proposed Collection, Comment Request | |
81 FR 23756 - Agency Information Collection Activities: Reverse Mortgage Products: Guidance for Managing Compliance and Reputation Risks; Comment Request | |
81 FR 23803 - Advisory Committee: National Academic Affiliations Council; Notice of Meeting | |
81 FR 23701 - Formations of, Acquisitions by, and Mergers of Bank Holding Companies | |
81 FR 23702 - Change in Bank Control Notices; Acquisitions of Shares of a Bank or Bank Holding Company | |
81 FR 23722 - Determination of Regulatory Review Period for Purposes of Patent Extension; LUZU | |
81 FR 23708 - Scientific Evidence in Development of Human Cells, Tissues, and Cellular and Tissue-Based Products Subject to Premarket Approval; Public Workshop | |
81 FR 23661 - Draft Guidances Relating to the Regulation of Human Cells, Tissues, and Cellular and Tissue-Based Products; Rescheduling of Public Hearing; Request for Comments | |
81 FR 23701 - Radio Broadcasting Services; AM or FM Proposals To Change the Community of License | |
81 FR 23723 - Authorization of Emergency Use of an In Vitro Diagnostic Device for Detection of Zika Virus; Availability | |
81 FR 23709 - Authorization of Emergency Use of an In Vitro Diagnostic Device for Detection of Ebola Zaire Virus; Availability | |
81 FR 23720 - Agency Information Collection Activities; Proposed Collection; Comment Request; Export of Medical Devices; Foreign Letters of Approval | |
81 FR 23733 - Risk Assessment of Foodborne Illness Associated With Pathogens From Produce Grown in Fields Amended With Untreated Biological Soil Amendments of Animal Origin; Request for Scientific Data, Information, and Comments; Extension of Comment Period | |
81 FR 23664 - Draft Guidances Relating to the Regulation of Human Cells, Tissues, and Cellular and Tissue-Based Products; Extension of Comment Periods | |
81 FR 23758 - Advisory Committee for Computer and Information Science and Engineering; Notice of Meeting | |
81 FR 23679 - North Pacific Fishery Management Council; Public Meeting | |
81 FR 23675 - Del Norte County Resource Advisory Committee | |
81 FR 23674 - Fishlake Resource Advisory Committee | |
81 FR 23767 - Submission for OMB Review; Comment Request | |
81 FR 23779 - Submission for OMB Review; Comment Request | |
81 FR 23792 - Submission for OMB Review; Comment Request | |
81 FR 23793 - Submission for OMB Review; Comment Request | |
81 FR 23745 - Endangered Species; Receipt of Applications for Permit | |
81 FR 23667 - NASA Federal Acquisition Regulation Supplement: Clarification of Award Fee Evaluations and Payments (NFS Case 2016-N008) | |
81 FR 23757 - Arts Advisory Panel Meetings | |
81 FR 23677 - Taking and Importing Marine Mammals; Taking Marine Mammals Incidental to Fisheries Research | |
81 FR 23695 - Combined Notice of Filings #1 | |
81 FR 23699 - Great Lakes Hydro America, LLC; Notice of Application Accepted for Filing and Soliciting Comments, Motions To Intervene, and Protests | |
81 FR 23696 - Combined Notice of Filings #2 | |
81 FR 23692 - Agency Information Collection Activities; Submission to the Office of Management and Budget for Review and Approval; Comment Request; ED School Climate Surveys (EDSCLS) Benchmark Study 2017 Update | |
81 FR 23631 - Drawbridge Operation Regulation; Arthur Kill, Staten Island, New York | |
81 FR 23632 - Safety Zone; Xterra Swim, Myrtle Beach, SC Intracoastal Waterway; Myrtle Beach, SC | |
81 FR 23678 - Submission for OMB Review; Comment Request | |
81 FR 23679 - Submission for OMB Review; Comment Request | |
81 FR 23739 - Agency Information Collection Activities: Regulations Relating to Recordation and Enforcement of Trademarks and Copyrights | |
81 FR 23803 - Clinical Science Research and Development Service Cooperative Studies Scientific Evaluation Committee; Notice of Meeting | |
81 FR 23749 - Certain Three-Dimensional Cinema Systems and Components Thereof; Commission Determination To Extend the Target Date; Schedule for Filing Written Submissions on Certain Issues | |
81 FR 23749 - Polyethylene Retail Carrier Bags From China, Indonesia, Malaysia, Taiwan, Thailand, and Vietnam; Determinations | |
81 FR 23750 - 1,1,1,2-Tetrafluoroethane (R-134a) From China; Determination | |
81 FR 23578 - Special Conditions: Bombardier Inc. Model BD-700-2A12 and BD-700-2A13 Airplanes; Airplane Electronic System Security Protection From Unauthorized External Access | |
81 FR 23579 - Special Conditions: Gulfstream Aerospace Corporation Model GVII-G500 Airplanes; Airplane Electronic System Security Protection From Unauthorized External Access | |
81 FR 23570 - Special Conditions: Gulfstream Aerospace Corporation Model GVII-G500 Airplanes, Pilot Compartment View Requirements With an Enhanced Flight Vision System | |
81 FR 23566 - Special Conditions: Dassault Aviation Model Falcon 5X Airplane; Use of Automatic Power Reserve (APR), an Automatic Takeoff Thrust Control System (ATTCS) for Go-Around Performance Credit | |
81 FR 23801 - Petition for Exemption; Summary of Petition Received; Precisionhawk | |
81 FR 23800 - Petition for Exemption; Summary of Petition Received; Rotorcraft Leasing Co. | |
81 FR 23802 - Petition for Exemption; Summary of Petition Received; Delta Air Lines Inc. | |
81 FR 23800 - Petition for Exemption; Summary of Petition Received; William Nelson | |
81 FR 23746 - Indian Gaming; Approval of Amendment to Tribal-State Class III Gaming Compact in the State of South Dakota | |
81 FR 23799 - Petition for Exemption; Summary of Petition Received; Airlines for America | |
81 FR 23802 - Petition for Exemption; Summary of Petition Received; Delta Air Lines, Inc. | |
81 FR 23737 - Prospective Grant of Exclusive License: The Development of Anti-CD70 Chimeric Antigen Receptors (CARs) for the Treatment of Chronic Myelogenous Leukemia | |
81 FR 23786 - Self-Regulatory Organizations; New York Stock Exchange LLC; Notice of Filing of Proposed Rule Change Establishing Fees Relating to End Users and Amending the Definition of “Affiliate,” as Well as Amending the Exchange's Price List To Reflect the Changes | |
81 FR 23773 - Self-Regulatory Organizations; NYSE Arca, Inc.; Notice of Filing of Proposed Rule Change Establishing Fees Relating to End Users and Amending the Definition of “Affiliate,” as Well as Amending the Arca Options Fee Schedule and the NYSE Arca Equities Schedule of Fees and Charges for Exchange Services to Reflect the Changes | |
81 FR 23780 - Self-Regulatory Organizations; NYSE MKT LLC; Notice of Filing of Proposed Rule Change Establishing Fees Relating to End Users and Amending the Definition of “Affiliate,” as Well as Amending the NYSE MKT Equities Price List and the NYSE Amex Options Fee Schedule To Reflect the Changes | |
81 FR 23768 - Self-Regulatory Organizations; Bats BZX Exchange, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change to Rule 14.3 Regarding the Requirements for the Listing of Securities That Are Issued by the Exchange or Any of Its Affiliates | |
81 FR 23771 - Self-Regulatory Organizations; Bats BYX Exchange, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Adopt Exchange Rule 14.10 Setting Forth Additional Requirements for the Listing of Securities That Are Issued by the Exchange or Any of Its Affiliates | |
81 FR 23765 - Self-Regulatory Organizations; Bats EDGA Exchange, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Adopt Exchange Rule 14.10 Setting Forth Additional Requirements for the Listing of Securities That Are Issued by the Exchange or Any of Its Affiliates | |
81 FR 23793 - Self-Regulatory Organizations; Bats EDGX Exchange, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Adopt Exchange Rule 14.10 Setting Forth Additional Requirements for the Listing of Securities That Are Issued by the Exchange or Any of Its Affiliates | |
81 FR 23735 - National Institute of General Medical Sciences; Notice of Closed Meeting | |
81 FR 23739 - National Cancer Institute; Notice of Closed Meetings | |
81 FR 23734 - National Center for Advancing Translational Sciences; Notice of Closed Meeting | |
81 FR 23735 - Submission for OMB Review; 30-Day Comment Request; The Framingham Heart Study (NHLBI) | |
81 FR 23796 - Aldine Capital Fund II, L.P.; License No. 05/05-0310; Notice Seeking Exemption Under Section 312 of the Small Business Investment Act, Conflicts of Interest | |
81 FR 23573 - Special Conditions: Gulfstream Aerospace Corporation, Gulfstream GVI Airplane; Non-Rechargeable Lithium Battery Installations | |
81 FR 23631 - Drawbridge Operation Regulation; Newark Bay, Jersey City, NJ | |
81 FR 23669 - International Fisheries; Tuna and Tuna-Like Species in the Eastern Pacific Ocean; Fishing Restrictions Regarding Mobulid Rays | |
81 FR 23645 - Fisheries of the Exclusive Economic Zone Off Alaska; Fixed-Gear Commercial Halibut and Sablefish Fisheries; Bering Sea and Aleutian Islands Crab Rationalization Program; Cost Recovery Authorized Payment Methods | |
81 FR 23764 - New Postal Product | |
81 FR 23563 - Surety Bond Guarantee Program; Miscellaneous Amendments | |
81 FR 23706 - Announcement of the Re-Approval of the American Society of Histocompatibility and Immunogenetics (ASHI) as an Accreditation Organization Under the Clinical Laboratory Improvement Amendments of 1988 | |
81 FR 23658 - Proposed Amendment of Class E Airspace, Truckee, CA | |
81 FR 23737 - Submission for OMB Review; 30-Day Comment Request; The Agricultural Health Study: A Prospective Cohort Study of Cancer and Other Diseases Among Men and Women in Agriculture (NIEHS) | |
81 FR 23605 - Special Local Regulations and Safety Zones; Recurring Marine Events and Fireworks Displays Within the Fifth Coast Guard District | |
81 FR 23604 - Mandatory Declassification Review Program | |
81 FR 23656 - Airworthiness Directives; Airbus Helicopters Deutschland GmbH Helicopters | |
81 FR 23634 - International Product Changes | |
81 FR 23693 - President's Advisory Commission on Asian Americans and Pacific Islanders | |
81 FR 23666 - Air Plan Approval: Tennessee: Knox County VOC Limits Revision for Permits | |
81 FR 23639 - Air Plan Approval; Tennessee: Knox County VOC Limits Revision for Permits | |
81 FR 23591 - Establishment of Class E Airspace; Coldwater, KS | |
81 FR 23650 - Raisins Produced From Grapes Grown in California; Hearing on Proposed Amendment of Marketing Order No. 989 | |
81 FR 23734 - Announcement of Intent To Establish the Secretary's Advisory Committee on National Health Promotion and Disease Prevention Objectives for 2030 and Solicitation of Nominations for Membership; Correction | |
81 FR 23916 - Business and Financial Disclosure Required by Regulation S-K | |
81 FR 23740 - Federal Property Suitable as Facilities To Assist the Homeless | |
81 FR 23581 - Airworthiness Directives; The Boeing Company Airplanes | |
81 FR 23641 - Amendments Related to: Tier 3 Motor Vehicle Emission and Fuel Standards | |
81 FR 23660 - Proposed Revocation of Class E Airspace; Lake Providence, LA | |
81 FR 23593 - Establishment of Class E Airspace; Danville AR | |
81 FR 23592 - Establishment of Class E Airspace; Moriarty, NM | |
81 FR 23597 - Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures; Miscellaneous Amendments | |
81 FR 23601 - Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures; Miscellaneous Amendments | |
81 FR 23594 - Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures; Miscellaneous Amendments | |
81 FR 23602 - Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures; Miscellaneous Amendments | |
81 FR 23586 - Airworthiness Directives; The Boeing Company Airplanes | |
81 FR 23806 - National Performance Management Measures; Assessing Performance of the National Highway System, Freight Movement on the Interstate System, and Congestion Mitigation and Air Quality Improvement Program |
Agricultural Marketing Service
Forest Service
International Trade Administration
National Oceanic and Atmospheric Administration
Army Department
Federal Energy Regulatory Commission
Centers for Disease Control and Prevention
Centers for Medicare & Medicaid Services
Children and Families Administration
Food and Drug Administration
National Institutes of Health
Coast Guard
U.S. Customs and Border Protection
Fish and Wildlife Service
Indian Affairs Bureau
Land Management Bureau
Ocean Energy Management Bureau
Surface Mining Reclamation and Enforcement Office
Employment and Training Administration
Labor Statistics Bureau
National Endowment for the Arts
Federal Aviation Administration
Federal Highway Administration
Consult the Reader Aids section at the end of this issue for phone numbers, online resources, finding aids, and notice of recently enacted public laws.
To subscribe to the Federal Register Table of Contents LISTSERV electronic mailing list, go to http://listserv.access.thefederalregister.org and select Online mailing list archives, FEDREGTOC-L, Join or leave the list (or change settings); then follow the instructions.
U.S. Small Business Administration.
Final rule.
The Small Business Administration (SBA) is issuing this final rule to change the regulations for SBA's Surety Bond Guarantee Program in four areas. First, as a condition for participating in the Prior Approval and Preferred Surety Bond Programs, this rule clarifies that a Surety must directly employ underwriting and claims staffs sufficient to perform and manage these functions, and that final settlement authority for claims and recovery is vested only in salaried employees of the Surety. Second, this rule provides that all costs incurred by the Surety's salaried claims staff are ineligible for reimbursement by SBA, except the amounts actually paid for reasonable and necessary travel expenses. In addition, the Surety may seek reimbursement for amounts paid for specialized services that are provided by outside consultants in connection with the processing of a claim. Third, the rule modifies the criteria for determining when a Principal that caused a Loss to SBA is ineligible for a bond guaranteed by SBA. Fourth, the rule modifies the criteria for admitting Sureties to the Preferred Surety Bond Program by increasing the Surety's underwriting limitation, as certified by the U.S. Treasury Department on its list of acceptable sureties, from at least $2 million to at least $6.5 million.
This rule is effective May 23, 2016.
Barbara J. Brannan, Office of Surety Guarantees, (202) 205-6545 or email:
The U.S. Small Business Administration (SBA) guarantees bid, payment and performance bonds for small and emerging contractors who cannot obtain surety bonds through regular commercial channels. SBA's guarantee gives Sureties an incentive to provide bonding for small businesses and, thereby, assists small businesses in obtaining greater access to contracting opportunities. SBA's guarantee is an agreement between a Surety and SBA that SBA will assume a certain percentage of the Surety's loss should a contractor default on the underlying contract.
On April 14, 2015, SBA published a notice of proposed rulemaking with a request for comments in the
(1) The rule proposed to clarify that to participate in the Prior Approval and Preferred Surety Bond (PSB) Programs, a Surety must directly employ underwriting and claims staffs sufficient to perform and manage these functions, and that final settlement authority for claims and recoveries must be vested only in the Surety's salaried claims staff.
(2) The rule proposed to specify that the costs that the Surety incurs for its salaried claims staff are ineligible for reimbursement by SBA and that the Surety may seek reimbursement for amounts actually paid by the Surety for specialized services that are provided by an outside consultant, which is not an Affiliate of the Surety, in connection with the processing of a claim, provided that such services are beyond the capability of the Surety's salaried claims staff.
(3) The rule proposed to modify the conditions under which a Principal, and its Affiliates, would be deemed ineligible for a bond guaranteed by SBA in the circumstance where the Principal has previously defaulted on an SBA guaranteed surety bond. The rule provided that a Principal, or any of its Affiliates, would lose eligibility for further SBA bond guarantees if the Principal, or any of its Affiliates, had defaulted on an SBA guaranteed bond resulting in a Loss (as defined in 13 CFR 115.16) that had not been fully reimbursed to SBA, or if SBA had not been fully reimbursed for any Imminent Breach payments. It also provided that the Principal, or any of its Affiliates, may be reinstated only if SBA had been fully repaid for the Loss or for the Imminent Breach payment, unless SBA's Office of Surety Guarantees (OSG) found good cause for reinstating the Principal. In addition, the discharge of the indebtedness in bankruptcy would no longer be specifically included as a condition for reinstatement, but the circumstances of such discharge could be considered as part of OSG's good cause analysis for reinstatement. The Proposed Rule also clarified that the same standards regarding the loss of eligibility and the conditions for reinstatement would apply to both the Prior Approval Program and the PSB Program.
(4) The rule proposed to modify the criteria for admitting a Surety to participate in the PSB Program by increasing the Surety's underwriting limitation, as certified by the U.S. Treasury Department on its list of acceptable sureties on Federal bonds, from at least $2 million to at least $6.5 million.
The comment period was open until June 15, 2015, and SBA received comments from one trade association and one surety company. One other comment was received from an individual, but this comment did not relate to the Proposed Rule or the SBG Program.
One of the commenters indicated its support for the proposed changes that modify the conditions under which a Principal, and its Affiliates, would be deemed ineligible for a bond guaranteed by SBA and that modify the requirements for reinstatement. The commenter also expressed support for SBA's effort to address the failure of some participating Sureties to maintain adequate in-house claims personnel, and to ensure that participating Sureties handle their SBA-guaranteed bond claims in the same manner as their other bond claims.
However, both commenters expressed concern that the proposed changes to 13
SBA has considered the suggestion but has concluded that the reasonable cost standard proposed by the commenters does not adequately reflect the requirement that Sureties employ sufficient in-house staff to handle all customary claims and recovery functions. SBA expects participating Sureties to employ adequate in-house staff to perform these functions and to bear the full cost of performing such functions. The Proposed Rule does recognize that there may be circumstances where an outside consultant with a particular expertise beyond the capabilities of the Surety's salaried claims staff is needed in connection with a claim, and would allow Sureties to seek reimbursement for the costs of such expertise. As described in the preamble to the Proposed Rule, an example of such “specialized services . . . beyond the capability of the Surety's salaried claims staff” would be the services of a structural engineer that are needed to evaluate the Principal's compliance with engineering specifications, and a commenter agreed with this example. SBA believes that its proposed language is sufficiently broad to cover the various situations that may arise.
In addition, a commenter suggested that the proposed requirement in 13 CFR 115.11 that the Surety must have a salaried staff “to perform all claims and recovery functions” be revised by removing the term “all” to account for those instances where outside consultants are retained to assist in claim and recovery functions. Instead of removing the term “all”, SBA is revising this section to recognize that the Surety may seek reimbursement for specialized services provided by outside consultants under 13 CFR 115.16(e)(1). Again, SBA expects that these consultants will be needed to provide a specialized service that is beyond the expertise of the Surety's salaried claims staff.
Finally, both commenters stated that travel by in-house claims staff is often necessary and expressed concern that the proposed language in 13 CFR 115.16(f)(1) excludes travel costs as a reimburseable expense. SBA agrees that Sureties may seek reimbursement for reasonable and necessary travel expenses by their in-house claims staff, and has amended the language in 13 CFR 115.16(e)(1) and 115.16(f)(1) accordingly.
In addition, as proposed, the same criteria on ineligibility and conditions for reinstatement would apply to both the Prior Approval Program and the PSB Program. As the same conditions for reinstatement will apply to both the Prior Approval Program and the PSB Program, the conditions for reinstatement set forth in 13 CFR 115.36(b) and (c) will be moved in their entirety to 13 CFR 115.14(b) and (c), and the heading of this section will be changed to “Loss of Principal's eligibility for future assistance and reinstatement of Principal.”
There are no changes to this provision as proposed.
Compliance with Executive Orders 12866, 13563, 12988, and 13132, the Paperwork Reduction Act (44 U.S.C. Ch. 35) and the Regulatory Flexibility Act (5 U.S.C. 601-612).
The Office of Management and Budget (OMB) has determined that this rule does not constitute a significant regulatory action under Executive Order 12866. This rule is also not a major rule under the Congressional Review Act (5 U.S.C. 800).
In accordance with Executive Order 13563, SBA discussed with several surety companies issues regarding the SBG Program regulations. In particular, SBA discussed the underwriting and claims staffing requirements that Sureties must meet in order to participate in SBA's SBG Program. SBA also discussed with these companies the conditions for reimbursement of the costs incurred by their claims staffs. Generally, the Sureties responded favorably to SBA's position that changes were necessary to clarify or amend the regulations on these issues.
This action meets applicable standards set forth in Sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden. The action does not have retroactive or preemptive effect.
SBA has determined that this rule will not have substantial, direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, for purposes of Executive Order 13132, SBA has determined that this rule has no federalism implications warranting preparation of a federalism assessment.
For the purpose of the Paperwork Reduction Act, 44 U.S.C., Chapter 35, SBA has determined that this rule will not impose any new reporting or recordkeeping requirements.
The Regulatory Flexibility Act (RFA) 5 U.S.C. 601, requires administrative agencies to consider the effect of their actions on small entities, small non-profit enterprises, and small local governments. Pursuant to the RFA, when an agency issues a rulemaking, the agency must prepare a regulatory flexibility analysis which describes the impact of the rule on small entities. However, section 605 of the RFA allows an agency to certify a rule, in lieu of preparing an analysis, if the rulemaking is not expected to have a significant economic impact on a substantial number of small entities. There are 23 Sureties that participate in the SBA program, and no part of this rule would impose any significant additional cost or burden on them. Consequently, this rule does not meet the significant economic impact on a substantial number of small businesses criterion anticipated by the Regulatory Flexibility Act.
Claims, Reporting and recordkeeping requirements, Small businesses, Surety bonds.
For the reasons stated in the preamble, SBA amends 13 CFR part 115 as follows:
5 U.S.C. app 3; 15 U.S.C. 687b, 687c, 694a, 694b note; and Pub. L. 110-246, Sec. 12079, 122 Stat. 1651.
* * * At a minimum, each applicant must have salaried staff that is employed directly (not an agent or other individual or entity under contract with the applicant) to oversee its underwriting function and perform all claims and recovery functions other than specialized services the costs of which may be reimbursable under 13 CFR 115.16(e)(1). Final settlement authority for claims and recovery must be vested only in the applicant's salaried claims staff. The applicant must continue to comply with SBA's standards and procedures for underwriting, administration, claims, recovery, and staffing requirements while participating in SBA's Surety Bond Guarantee Programs.
(a) * * *
(7)
(a) * * *
(4) The Principal, or any of its Affiliates, has defaulted on an SBA-
(b)
(1) A Prior Approval Surety may recommend that such Principal's eligibility be reinstated, and OSG may agree to reinstate the Principal if:
(i) The Surety has settled its claim with the Principal, or any of its Affiliates, for an amount that results in no Loss to SBA or in no amount owed for Imminent Breach payments, or OSG finds good cause for reinstating the Principal notwithstanding the Loss to SBA or amount owed for Imminent Breach payments; or
(ii) OSG and the Surety determine that further bond guarantees are appropriate after the Principal was deemed ineligible for further SBA bond guarantees under paragraph (a)(1), (2), (3), (5) or (6) of this section.
(2) A PSB Surety may:
(i) Recommend that such Principal's eligibility be reinstated, and OSG may agree to reinstate the Principal, if the Surety has settled its claim with the Principal, or any of its Affiliates, for an amount that results in no Loss to SBA or in no amount owed for Imminent Breach payments, or OSG finds good cause for reinstating the Principal notwithstanding the Loss to SBA or amount owed for Imminent Breach payments; or
(ii) Reinstate a Principal's eligibility upon the Surety's determination that further bond guarantees are appropriate after the Principal was deemed ineligible for further SBA bond guarantees under paragraph (a)(1), (2), (3), (5) or (6) of this section.
(c)
(e) * * *
(1) Amounts actually paid by the Surety for specialized services that are provided under contract by an outside consultant, which is not an Affiliate of the Surety, provided that such services are beyond the capability of the Surety's salaried claims staff, and amounts actually paid by the Surety for travel expenses of the Surety's claims staff. The cost of the consultant's services and the travel expenses of the Surety's claims staff must be reasonable and necessary and must specifically concern the investigation, adjustment, negotiation, compromise, settlement of, or resistance to a claim for Loss resulting from the breach of the terms of the bonded Contract. The cost allocation method must be reasonable and must comply with generally accepted accounting principles; and
(f) * * *
(1) Any unallocated expenses, all direct and indirect costs incurred by the Surety's salaried claims staff (except for reasonable and necessary travel expenses of such staff), or any clear mark-up on expenses or any overhead of the Surety, its attorney, or any other consultant hired by the Surety or the attorney;
(a) * * *
(2)
Federal Aviation Administration (FAA), DOT.
Final special conditions; request for comments.
These special conditions are issued for the Dassault Aviation (Dassault) Model Falcon 5X airplane. This airplane will have a novel or unusual design feature associated with go-around performance credit when using an automatic takeoff thrust-control system. 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.
This action is effective on Dassault Aviation on April 22, 2016. We must receive your comments by June 6, 2016.
Send comments identified by docket number FAA-2014-1078 using any of the following methods:
•
•
•
•
Chris Parker, FAA, Propulsion and Mechanical Systems Branch, ANM-112, Transport Airplane Directorate, Aircraft Certification Service, 1601 Lind Avenue SW., Renton, Washington 98057-3356; telephone 425-227-1509; facsimile 425-227-1320.
The substance of these special conditions has been subject to the public comment process in several prior instances with no substantive comments received. The FAA therefore finds that good cause exists for making these special conditions effective upon publication in the
We invite 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 special conditions, explain the reason for any recommended change, and include supporting data.
We will consider all comments we receive by the closing date for comments. We may change these special conditions based on the comments we receive.
On July 1, 2012, Dassault Aviation applied for a type certificate for their new Model Falcon 5X airplane. This airplane is a transport-category airplane to be operated in private/corporate transportation with a maximum of 19 passengers. The Model Falcon 5X airplane incorporates a low, swept wing and twin rear-fuselage-mounted Snecma Silvercrest turbofan engines. The fuselage is about 23 m long with a 26 m wingspan.
The current requirements of Title 14, Code of Federal Regulations (14 CFR) part 25 are inadequate for addressing approach climb using ATTCS. Part 25 appendix I limits the application of performance credit for ATTCS to takeoff only.
Under the provisions of 14 CFR 21.17, Dassault Aviation must show that the Model Falcon 5X airplane meets the applicable provisions of part 25, as amended by Amendments 25-1 through 25-136.
If the Administrator finds that the applicable airworthiness regulations (
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, these special conditions would also apply to the other model under § 21.101.
In addition to the applicable airworthiness regulations and special conditions, the Model Falcon 5X 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 14 CFR 11.19, in accordance with § 11.38, and they become part of the type certification basis under § 21.17(a)(2).
The Dassault Aviation Model Falcon 5X airplane will incorporate the following novel or unusual design feature.
An automatic takeoff thrust-control system (ATTCS), described as an automatic power reserve (APR) system, which is available at all times without any additional action or input from the pilot; and which the applicant proposes would not only function during the go-around, in addition to the takeoff phase of flight, but also allow the applicant to take performance credit for the system's function during that phase.
Dassault Aviation proposes to include an APR system (a part 23 term; the part 25 term is ATTCS) in the Model Falcon 5X airplane. Dassault proposes to use the APR system during go-around, and is requesting approach climb performance credit for the use of the additional power APR up-trim provides.
The Model Falcon 5X powerplant control system comprises a full-authority digital electronic control (FADEC) for the Snemca Silvercrest engine. The engine FADEC system includes APR system functions. The proposed configuration, which is novel or unusual, provides for APR activation during takeoff and go-around flight operations, requiring no additional action from the pilot. The airplane performance data will be based on the availability of the up-trim power during takeoff and approach climb.
The part 25 standards applicable to the automatic advancement of reserve power, known as ATTCS and contained in § 25.904 and appendix I, specifically restrict performance credit for ATTCS to the takeoff phase of flight. At the time these standards were issued, the FAA considered including other phases of flight, including go-around. Concerns about flightcrew workload precluded including those additional phases of flight. As the preamble of Amendment 25-62 to part 25 states:
In regard to ATTCS credit for approach climb and go-around maneuvers, current regulations preclude a higher power for the approach climb (Section 25.121(d)) than for the landing climb (Section 25.119). The workload required for the flightcrew to monitor and select from multiple in-flight power settings in the event of an engine failure during a critical point in the approach, landing, or go-around operations is excessive. Therefore, the FAA does not agree that the scope of the amendment should be changed to include the use of ATTCS for anything except the takeoff phase.
The ATTCS incorporated on the Model Falcon 5X airplane allows the pilot to use the same power-setting procedure during a go-around regardless of whether or not an engine fails. Because the ATTCS is always active, it will function automatically following an engine failure, and will advance the remaining engine to the APR power level.
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.
As discussed above, these special conditions are applicable to the Model Falcon 5X airplane. Should Dassault Aviation apply at a later date for a change to the type certificate to include another model incorporating the same novel or unusual design feature, these special conditions would apply to that model as well.
This action affects only a certain novel or unusual design feature on one model of airplane. It is not a rule of general applicability.
The substance of these special conditions has been subjected to the notice and comment period in several prior instances and has been derived without substantive change from those previously issued. It is unlikely that prior public comment would result in a significant change from the substance contained herein. Therefore, the FAA has determined that prior public notice and comment are unnecessary and impracticable, and good cause exists for adopting these special conditions upon publication in the
Aircraft, Aviation safety, Reporting and recordkeeping requirements.
The authority citation for these special conditions is as follows:
49 U.S.C. 106(g), 40113, 44701, 44702, 44704.
Accordingly, pursuant to the authority delegated to me by the Administrator, the following special conditions are issued as part of the type certification basis for Dassault Aviation Model Falcon 5X airplanes.
1. The Model Falcon 5X airplane must comply with the requirements of 14 CFR 25.904 and appendix I to 14 CFR part 25 and the following requirements pertaining to the go-around phase of flight:
2. Definitions
a.
b.
c.
i. When conducting an approach for landing using ATTCS, the critical time interval is defined as follows:
1. The critical time interval begins at a point on a 2.5 degree approach glide path from which, assuming a simultaneous engine and ATTCS failure, the resulting approach climb flight path intersects a flight path originating at a later point on the same approach path corresponding that corresponds to the 14 CFR part 25 one-engine-inoperative approach climb gradient. The period of time from the point of simultaneous engine and ATTCS failure to the intersection of these flight paths must be no shorter than the time interval used in evaluating the critical time interval for takeoff beginning from the point of simultaneous engine and ATTCS failure and ending upon reaching a height of 400 feet.
2. The critical time interval
ii. The critical time interval must be determined at the altitude resulting in the longest critical time interval for which one-engine-inoperative approach climb performance data are presented in the airplane flight manual (AFM).
iii. The critical time interval is illustrated in the following figure:
The all-engines-operating go-around flight path, and the 14 CFR part 25 one-engine-inoperative approach climb gradient flight path (engine failed, ATTCS operating path in Figure 1), originate from a common point, point C, on a 2.5-degree approach path. The period of time, “time interval DE,” from the point of simultaneous engine and ATTCS failure, point D, to the intersection of these flight paths, point E, must be no shorter than the corresponding time in Figure 2, “I25.2(b) time interval FG.”
d. The critical time interval must be determined at the altitude resulting in the longest critical time interval for which one-engine-inoperative approach climb performance data are presented in the AFM.
e. The “critical time interval AD” is illustrated in Figure 1.
3. Performance and system reliability requirements: The applicant must comply with the performance and ATTCS reliability requirements as follows:
a. An ATTCS failure or a combination of failures in the ATTCS during the critical time interval (Figure 2):
i. Must not prevent the insertion of the maximum approved go-around thrust or power, or must be shown to be a remote event.
ii. Must not result in a significant loss or reduction in thrust or power, or must be shown to be an extremely improbable event.
b. The concurrent existence of an ATTCS failure and an engine failure during the critical time interval must be shown to be extremely improbable.
c. All applicable performance requirements of 14 CFR part 25 must be met with an engine failure occurring at the most critical point during go-around with the ATTCS functioning.
d. The probability analysis must include consideration of ATTCS failure occurring after the time at which the flightcrew last verifies that the ATTCS is in a condition to operate until the beginning of the critical time interval.
e. The propulsive thrust obtained from the operating engine after failure of the critical engine during a go-around used to show compliance with the one-engine-inoperative climb requirements of § 25.121(d) may not be greater than the lesser of:
i. The actual propulsive thrust resulting from the initial setting of power or thrust controls with the ATTCS functioning; or
ii. 111% of the propulsive thrust resulting from the initial setting of power or thrust controls with the ATTCS failing to reset thrust or power and without any action by the flightcrew to reset thrust or power.
4. Thrust setting
a. The initial go-around thrust setting on each engine at the beginning of the go-around phase may not be less than any of the following:
i. That required to permit normal operation of all safety-related systems and equipment dependent upon engine thrust or power lever position; or
ii. That shown to be free of hazardous engine response characteristics and not to result in any unsafe aircraft operating or handling characteristics when thrust or power is advanced from the initial go-around position to the maximum approved power setting.
b. For approval to use an ATTCS for go-arounds, the thrust setting procedure must be the same for go-arounds initiated with all engines operating as for go-arounds initiated with one engine inoperative.
5. Powerplant controls
a. In addition to the requirements of § 25.1141, no single failure or malfunction, or probable combination thereof, of the ATTCS, including associated systems, may cause the failure of any powerplant function necessary for safety.
b. The ATTCS must be designed to:
i. Apply thrust or power on the operating engine(s), following any one-engine failure during a go-around, to achieve the maximum approved go-around thrust without exceeding the engine operating limits;
ii. Permit manual decrease or increase in thrust or power up to the maximum go-around thrust approved for the airplane under the existing conditions through the use of the power lever. For airplanes equipped with limiters that automatically prevent the engine operating limits from being exceeded under existing ambient conditions, other means may be used to increase the thrust in the event of an ATTCS failure, provided that the means:
1. Is located on or forward of the power levers;
2. Is easily identified and operated under all operating conditions by a single action of either pilot with the hand that is normally used to actuate the power levers; and
3. Meets the requirements of § 25.777(a), (b), and (c).
iii. Provide a means to verify to the flightcrew before beginning an approach for landing that the ATTCS is in a condition to operate (unless it can be demonstrated that an ATTCS failure combined with an engine failure during an entire flight is extremely improbable); and
iv. Provide a means for the flightcrew to deactivate the automatic function. This means must be designed to prevent inadvertent deactivation.
6. Powerplant instruments: In addition to the requirements of § 25.1305:
a. A means must be provided to indicate when the ATTCS is in the armed or ready condition; and
b. If the inherent flight characteristics of the airplane do not provide adequate warning that an engine has failed, a warning system that is independent of the ATTCS must be provided to give the pilot a clear warning of any engine failure during a go-around.
Federal Aviation Administration (FAA), DOT.
Final special conditions; request for comments.
These special conditions are issued for the Gulfstream Aerospace Corporation (Gulfstream) Model GVII-G500 airplane. This 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 an enhanced flight vision system (EFVS) that includes a head-up display (HUD) capable of displaying forward-looking infrared (FLIR) imagery, intended to be used for instrument approaches under provisions of Title 14, Code of Federal Regulations (14 CFR) 91.175(l) and (m). 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.
This action is effective on Gulfstream Aerospace Corporation on April 22, 2016. We must receive your comments by June 6, 2016.
Send comments identified by docket number FAA-2015-7301 using any of the following methods:
•
•
•
•
Dale Dunford, FAA, Airplane and Flightcrew Interface Branch, ANM-111, Transport Airplane Directorate, Aircraft Certification Service, 1601 Lind Avenue SW., Renton, Washington 98057-3356; telephone 425-227-2239; facsimile 425-227-1320.
The FAA has determined that notice of, and opportunity for prior public comment on, these special conditions is impracticable because these procedures would significantly delay issuance of the design approval and thus delivery of the affected airplane.
In addition, the substance of these special conditions has been subject to the public comment process in several prior instances with no substantive comments received. The FAA therefore finds that good cause exists for making these special conditions effective upon publication in the
We invite 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 special conditions, explain the reason for any recommended change, and include supporting data.
We will consider all comments we receive by the closing date for comments. We may change these special conditions based on the comments we receive.
On March 29, 2012, Gulfstream Aerospace Corporation applied for a type certificate for their new Model GVII-G500 series airplane. The Model GVII-G500 series airplane will be a business jet capable of accommodating up to 19 passengers. It will incorporate a low, swept-wing design with winglets and a T-tail. The powerplant will consist of two aft-fuselage-mounted Pratt & Whitney turbofan engines.
Under the provisions of Title 14, Code of Federal Regulations (14 CFR) 21.17, Gulfstream must show that the Model GVII-G500 series airplane meets the applicable provisions of 14 CFR part 25, as amended by Amendments 25-1 through 25-129.
If the Administrator finds that the applicable airworthiness regulations (
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 or similar novel or unusual design feature, the special conditions would also apply to the other model under § 21.101.
In addition to the applicable airworthiness regulations and special conditions, the Model GVII-G500 series 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 must issue a finding of regulatory adequacy under § 611 of Public Law 92-574, the “Noise Control Act of 1972.”
The FAA issues special conditions, as defined in 14 CFR 11.19, in accordance with § 11.38, and they become part of the type-certification basis under § 21.17(a)(2).
The Gulfstream Model GVII-G500 airplane will incorporate the following novel or unusual design feature:
An enhanced flight vision system (EFVS) that includes a head-up display (HUD) capable of displaying forward-looking infrared (FLIR) imagery, intended to be used for instrument approaches under provisions of § 91.175(l) and (m).
The EFVS uses novel technology for which the FAA has no certification criteria. Furthermore, 14 CFR 25.773, which was not written in anticipation of such technology, does not permit visual distortions and reflections that could interfere with the pilot's compartment view. The video image potentially interferes with the pilot's ability to see the natural scene in the center of their forward field of view. Because § 25.773 does not provide for alternatives or considerations for such a novel system, it is necessary to establish safety requirements that assure an equivalent level of safety and effectiveness of the pilot compartment view as intended by this rule. These special conditions for the EFVS are prescribed under the provisions of § 21.16. Other applications for certification of such technology are anticipated in the near future, and magnify the need to establish FAA safety standards that can be applied consistently for all such approvals.
Unlike the pilot's natural forward vision, the EFVS image is infrared-based, monochrome, 2-dimensional (
These special conditions provide the unique pilot-compartment view requirements for the EFVS installation.
Compliance with these special conditions is required for the EFVS to be found acceptable, for the following intended functions, in accordance with § 91.175(l) and (m):
1. Presenting an image that would aid the pilot during a straight-in instrument approach.
2. Enable the pilot to determine the “enhanced flight visibility,” as required by § 91.175(l)(2), for descent and operation below M
3. Enable the pilot to use the EFVS imagery to detect and identify the “visual references for the intended runway,” required by § 91.175(l)(3), to continue the approach with vertical
Note: The term “Enhanced Vision System,” or EVS, commonly refers to a system comprising a HUD, imaging sensor(s), and avionics interface(s) that displays the sensor imagery on the HUD and overlays it with alpha-numeric and symbolic flight information. However, the term has also been used to refer to systems that display the sensor imagery, with or without other flight information, on a head-down display. Therefore, to avoid confusion, the FAA has defined the term “Enhanced Flight Vision System” (EFVS) to refer to certain EVS that meet the requirements of § 91.175(m), in particular the requirement for a HUD and specified flight information, and the ability to determine “enhanced flight visibility.” Accordingly, an EFVS can be considered a subset of systems otherwise labeled EVS.
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.
As discussed above, these special conditions are applicable to the Gulfstream Model GVII-G500 airplane. Should Gulfstream apply at a later date for a change to the type certificate to include another model incorporating the same novel or unusual design feature, these special conditions would apply to that model as well.
This action affects only a certain novel or unusual design feature on one model series of airplane. It is not a rule of general applicability.
The substance of these special conditions has been subjected to the notice and comment period in several prior instances and has been derived without substantive change from those previously issued. It is unlikely that prior public comment would result in a significant change from the substance contained herein. Therefore, because a delay would significantly affect the certification of the airplane, the FAA has determined that prior public notice and comment are unnecessary and impracticable, and good cause exists for adopting these special conditions upon publication in the
The FAA is requesting comments to allow interested persons to submit views that may not have been submitted in response to the prior opportunities for comment described above.
Aircraft, Aviation safety, Reporting and recordkeeping requirements.
The authority citation for these special conditions is as follows:
49 U.S.C. 106(g), 40113, 44701, 44702, 44704.
Accordingly, pursuant to the authority delegated to me by the Administrator, the following special conditions are issued as part of the type certification basis for Gulfstream Model GVII-G500 airplanes.
1. Enhanced flight vision system (EFVS) imagery on the head-up display (HUD) must not degrade the safety of flight or interfere with the effective use of outside visual references for required pilot tasks during any phase of flight in which it is to be used.
2. To avoid unacceptable interference with the safe and effective use of the pilot-compartment view, the EFVS device must meet the following requirements:
a. EFVS design must minimize unacceptable display characteristics or artifacts (
b. Control of EFVS display brightness must be sufficiently effective, in dynamically changing background (ambient) lighting conditions, to prevent full or partial blooming of the display that would distract the pilot, impair the pilot's ability to detect and identify visual references, mask flight hazards, or otherwise degrade task performance or safety. If automatic control for image brightness is not provided, it must be shown that a single manual setting is satisfactory for the range of lighting conditions encountered during a time-critical, high-workload phase of flight (
c. A readily accessible control must be provided that permits the pilot to immediately deactivate and reactivate display of the EFVS image on demand, without removing the pilot's hands from the primary flight controls (yoke or equivalent) or thrust control.
d. The EFVS image on the HUD must not impair the pilot's use of guidance information, or degrade the presentation and pilot awareness of essential flight information displayed on the HUD, such as alerts, airspeed, attitude, altitude and direction, approach guidance, wind-shear guidance, traffic collision avoidance system (TCAS) resolution advisories, and unusual-attitude recovery cues.
e. The EFVS image and the HUD symbols, which are spatially referenced to the pitch scale, outside view, and image, must be scaled and aligned (
f. A HUD system used to display EFVS images must, if previously certified, continue to meet all of the requirements of the original approval.
3. The safety and performance of the pilot tasks associated with the use of the pilot-compartment view must be not be degraded by the display of the EFVS image. Pilot tasks which must not be degraded by the EFVS image include:
a. Detection, accurate identification, and maneuvering, as necessary, to avoid traffic, terrain, obstacles, and other hazards of flight.
b. Accurate identification and utilization of visual references required for every task relevant to the phase of flight.
4. Appropriate limitations must be stated in the Operating Limitations section of the Airplane Flight Manual to prohibit the use of the EFVS for functions that have not been found to be acceptable.
Federal Aviation Administration (FAA), DOT.
Final special conditions.
These special conditions are issued for the Gulfstream Aerospace Corporation (Gulfstream) GVI airplane. This 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 non-rechargeable lithium batteries. 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.
Effective April 22, 2017.
Nazih Khaouly, Airplane and Flight Crew Interface Branch, ANM-111, Transport Airplane Directorate, Aircraft Certification Service, 1601 Lind Avenue SW., Renton, Washington, 98057-3356; telephone 425-227-2432; facsimile 425-227-1149.
The FAA anticipates that non-rechargeable lithium batteries will be installed in other makes and models of airplanes. We have determined to require special conditions for all applications requesting non-rechargeable lithium battery installations, except the installations excluded in the Applicability section, until the airworthiness requirements can be revised to address this issue. Applying special conditions to these installations across the range of all transport-airplane makes and models will ensure regulatory consistency among applicants.
These are the first special conditions the FAA has issued for non-rechargeable lithium battery installations on any airplane. The FAA has determined that these special conditions become effective 1 year after their publication in the
Gulfstream applied for several changes to type certificate no. T00015AT to install non-rechargeable lithium batteries in the Model GVI airplane. The Gulfstream Model GVI airplane is a twin-engine, transport-category airplane with a maximum passenger capacity of 19 and maximum takeoff weight of 99,600 pounds.
Under the provisions of Title 14, Code of Federal Regulations (14 CFR) 21.101, Gulfstream must show that the design change and areas affected by the change continue to meet the applicable provisions of the regulations listed in type certificate no. T00015AT, or the applicable regulations in effect on the date of application for the change, except for earlier amendments as agreed upon by the FAA. The regulations listed in the type certificate are commonly referred to as the “original type certification basis.” The regulations listed in type certificate no. T00015AT are 14 CFR part 25 effective February 1, 1965, including Amendments 25-1 through 25-120, 25-122, 25-124, and 25-132. The certification basis also includes certain special conditions, exemptions, and equivalent-safety findings that are not relevant to these special conditions.
In addition to the applicable airworthiness regulations and special conditions, the Gulfstream Model GVI 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.
If the Administrator finds that the applicable airworthiness regulations (
Special conditions are initially applicable to the Gulfstream Model GVI airplane 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 § 21.101.
The FAA issues special conditions, as defined in 14 CFR 11.19, in accordance with § 11.38, and they become part of the type-certification basis under § 21.101.
The Gulfstream Model GVI airplane will incorporate non-rechargeable lithium batteries.
A battery system consists of the battery and any protective, monitoring, and alerting circuitry or hardware inside or outside of the battery, and venting capability where necessary. For the purpose of these special conditions, we refer to a battery and battery system as a battery.
The FAA derived the current regulations governing installation of batteries in transport-category airplanes from Civil Air Regulations (CAR) 4b.625(d) as part of the re-codification of CAR 4b that established 14 CFR part 25 in February 1965. This re-codification basically reworded the CAR 4b battery requirements, which are currently in § 25.1353(b)(1) through (b)(4). Non-rechargeable lithium batteries are novel and unusual with respect to the state of technology considered when these requirements were codified. These batteries introduce higher energy levels into airplane systems through new chemical compositions in various battery-cell sizes and construction. Interconnection of these cells in battery packs introduces failure modes that require unique design considerations, such as provisions for thermal management.
Recent events involving rechargeable and non-rechargeable lithium batteries prompted the FAA to initiate a broad evaluation of these energy-storage technologies. In January 2013, two independent events involving rechargeable lithium-ion batteries revealed unanticipated failure modes. A National Transportation Safety Board (NTSB) letter to the FAA, dated May 22, 2014, which is available at
On July 12, 2013, an event involving a non-rechargeable lithium battery, in an emergency-locator-transmitter installation, demonstrated unanticipated failure modes. The United Kingdom's Air Accidents
Some known uses of rechargeable and non-rechargeable lithium batteries on airplanes include:
• Flight deck and avionics systems such as displays, global-positioning systems, cockpit voice recorders, flight-data recorders, underwater locator beacons, navigation computers, integrated avionics computers, satellite network and communication systems, communication-management units, and remote-monitor electronic line-replaceable units;
• Cabin safety, entertainment, and communications equipment, including emergency-locator transmitters, life rafts, escape slides, seatbelt air bags, cabin-management systems, Ethernet switches, routers and media servers, wireless systems, internet and in-flight entertainment systems, satellite televisions, remotes, and handsets;
• Systems in cargo areas including door controls, sensors, video-surveillance equipment, and security systems.
Some known potential hazards and failure modes associated with non-rechargeable lithium batteries are:
• Internal failures: In general, these batteries are significantly more susceptible to internal failures that can result in self-sustaining increases in temperature and pressure (
• Fast or imbalanced discharging: Fast discharging or an imbalanced discharge of one cell of a multi-cell battery may create an overheating condition that results in an uncontrollable venting condition, which in turn leads to a thermal event or an explosion.
• Flammability: Unlike nickel-cadmium and lead-acid batteries, lithium batteries use higher energy and current in an electrochemical system that can be configured to maximize energy storage of lithium. They also use liquid electrolytes that can be extremely flammable. The electrolyte, as well as the electrodes, can serve as a source of fuel for an external fire if the battery casing is breached.
Special condition no. 1 requires that each individual cell within a non-rechargeable lithium battery be designed to maintain safe temperatures and pressures. Special condition no. 2 addresses these same issues but for the entire battery. Special condition no. 2 requires the battery be designed to prevent propagation of a thermal event, such as self-sustained, uncontrolled increases in temperature or pressure from one cell to adjacent cells.
Special condition nos. 1 and 2 are intended to ensure that the non-rechargeable lithium battery and its cells are designed to eliminate the potential for uncontrollable failures. However, a certain number of failures will occur due to various factors beyond the control of the battery designer. Therefore, other special conditions are intended to protect the airplane and its occupants if failure occurs.
Special condition nos. 3, 7, and 8 are self-explanatory; the FAA does not provide further explanation for them at this time.
The FAA requires special condition no. 4 to make it clear that the flammable-fluid fire-protection requirements of § 25.863 apply to non-rechargeable lithium battery installations. Section 25.863 is applicable to areas of the airplane that could be exposed to flammable-fluid leakage from airplane systems. Non-rechargeable lithium batteries contain an electrolyte that is a flammable fluid.
Special condition no. 5 requires each non-rechargeable lithium battery installation to not damage surrounding structure or adjacent systems, equipment, or electrical wiring from corrosive fluids or gases that may escape.
Special condition no. 5 addresses corrosive fluids and gases, whereas special condition no. 6 addresses heat. Special condition no. 6 requires each non-rechargeable lithium battery installation to have provisions to prevent any hazardous effect on airplane structure or systems caused by the maximum amount of heat the battery installation can generate due to any failure of it or its individual cells. The means of meeting these special conditions may be the same, but they are independent requirements addressing different hazards.
These special conditions apply to all non-rechargeable lithium battery installations in lieu of § 25.1353(b)(1) through (b)(4) at Amendment 25-113. Sections 25.1353(b)(1) through (b)(4) at Amendment 25-113 remain in effect for other battery installations.
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.
Notice of proposed special conditions no. 25-15-09-SC, for the Gulfstream GVI airplane, was published in the
The Aerospace Industries Association (AIA) recommended revising proposed special condition no. 1 to read (see italics), “. . . each non-rechargeable lithium battery installation must maintain safe cell temperatures and pressure under all foreseeable operating conditions to prevent fire and explosion
AIA recommended revising proposed special condition no. 2 to read, “. . . each non-rechargeable lithium battery installation must prevent the occurrence of self-sustaining, uncontrolled increases in temperature or pressure
AIA recommended revising proposed special condition no. 3 to read, “. . . each non-rechargeable lithium battery installation must not emit explosive or toxic gases in normal operation, or as a result of
AIA recommended deleting proposed special condition no. 4. AIA stated that it does not introduce a new airworthiness requirement and that it seems more appropriate to clarify applicability of an existing airworthiness requirement via policy. The FAA does not agree with the proposal. Section 25.863 historically has been applied to flammable fluids related to propulsion and hydraulic systems. The FAA has not issued guidance material at this time that would ensure a proper understanding that this section also applies to non-rechargeable lithium battery installations, which contain flammable fluid. We have determined to not delete proposed special condition no. 4.
AIA recommended revising proposed special condition no. 5 to read, “. . . each non-rechargeable lithium battery installation must not
AIA recommended revising proposed special condition no. 6 to read, “. . . each non-rechargeable lithium battery installation must have provisions to prevent any hazardous effect on airplane structure or systems caused by the maximum amount of heat it can generate due to any failure of
AIA recommended deleting proposed special condition no. 7, which reads, “. . . each non-rechargeable lithium battery installation must be capable of automatically controlling the discharge rate of each cell to prevent cell imbalance, back-charging, overheating, and uncontrollable temperature and pressure.” AIA stated that the hazard intended to be addressed by this special condition would be prevented by meeting special condition nos. 1, 2, 4 and 5. The intent of proposed special condition no. 7 was to also address charge imbalance because an in-service event demonstrated that a charge imbalance is one of many failure modes that can lead to a thermal runaway condition. However, the FAA agrees with deleting proposed special condition no. 7 because compliance with special condition nos. 1 and 2 accomplish the safety objectives of proposed special condition no. 7.
AIA recommended deleting proposed special condition no. 8, which reads, “. . . each non-rechargeable lithium battery installation must have a means to automatically disconnect from its discharging circuit in the event of an over-temperature condition, cell failure, or battery failure.” The FAA agrees with deleting this proposed special condition because doing so does not relieve applicants from the need to comply with § 25.1309. In addition to § 25.1309, all applicable system-level requirements may require the connected system to automatically disconnect from the battery discharging circuit in the event of an over-temperature condition, cell failure, or battery failure.
AIA recommended revising proposed special condition no. 9 (which is now special condition no. 7 in these special conditions) to read, “. . . each non-rechargeable lithium battery installation must have a failure sensing and warning system to alert the flightcrew if its failure affects
AIA recommended revising proposed special condition no. 10 (which is now special condition no. 8 in these special conditions) to read, “. . . each non-rechargeable lithium battery installation must have a means for the flightcrew or maintenance personnel to determine the battery charge state if the battery's function is required for
The Boeing Company commented that they concur with AIA's comments.
The Boeing Company also requested that the FAA provide adequate time before non-rechargeable lithium battery special conditions become effective, to support validation activities by foreign civil airworthiness authorities (FCAA) and to not adversely impact future airplane deliveries by all applicants. The Boeing Company stated that they have been “informed by FCAAs that validation activities for FAA type certificate data sheet certification basis changes can take up to 12 months after receipt of application.” The FAA agrees that adequate time is necessary to allow Gulfstream, and other applicants for which similar special conditions will be issued, to coordinate with FCAAs, and to conduct other activities associated
The Boeing Company commented that “. . . these special conditions should clearly indicate the scope of changes for which the certification basis is deemed inadequate and requires application of the special conditions.” The Boeing Company made this comment in regards to the applicability of these special conditions to batteries that have less than 2 watt-hours of energy and meet Underwriters Laboratories (UL) 1642 or UL 2054. The FAA has determined that the use of UL 1642 and UL 2054 should be addressed as a method-of-compliance issue rather than exclusion criteria for certain battery sizes. These special conditions are to apply to all non-rechargeable lithium batteries regardless of their size. These special conditions require this where it states “. . . each non-rechargeable lithium battery installation must . . .”
Airbus commented that they assume that the FAA considers the standards in Radio Technical Commission for Aeronautics (RTCA) DO-227,
Airbus commented that batteries that are Category I, as defined in RTCA DO-227, should be excluded from proposed special condition nos. 1 through 8 (which are special condition nos. 1 through 6 in these special conditions). RTCA DO-227 defines these batteries as “solid-cathode cells that contain less than 0.15 grams of lithium or lithium alloy, and batteries that use not more than four such cells.” The FAA does not concur. These special conditions are intended to provide an appropriate level of safety for all non-rechargeable lithium battery installations.
Bombardier provided the following comment on proposed special condition no. 3: “The quantity of [lithium battery] gas that will constitute a hazard is difficult to define and test. An outgassing limit in corresponding to cell size/number would be easier to comply with and test. This should only apply in the failure case, as in normal cell operation non-rechargeable [lithium batteries] are expected to remain sealed. We recommend wording that would instead limit cell size/number and require cell isolation to minimize hazard to airplane and occupant in case of failure and be sealed in normal operation. Exposure to occupants may be achieved by locating battery installations away from occupant areas on the airplane.” The FAA does not agree with the proposal. The FAA considers that a special condition that limits the number of cells and their size would be unnecessarily restrictive. Note that this special condition does not require applicants to determine the quantity of gas that would constitute a hazard. For example, an acceptable means of complying with this special condition is to demonstrate, through tests, that all emitted gasses are contained or vented overboard through designed ports. However, this special condition does allow explosive and toxic gases to be uncontained and not vented overboard if they do not accumulate in hazardous quantities within the airplane.
Bombardier commented that a design that prevents fluids and gases from escaping the installation should be an acceptable means of complying with proposed special condition no. 5. Bombardier recommended addressing the need for fluid containment. These comments address how to show compliance with the special conditions and would not change the special conditions. These comments can be addressed during the type certification projects.
Transport Canada recommended revising proposed special condition no. 1 to address “all hazards.” We have not revised this special condition because it is intended to address only the cell-level hazards, which are fire and explosion. All hazards are addressed through compliance with the complete set of applicable special conditions.
Transport Canada recommended adding a sentence to proposed special condition no. 2 that reads, “
Transport Canada recommended revising proposed special condition no. 5 to read, “. . . each non-rechargeable lithium battery installation must not damage surrounding structure or adjacent systems, equipment, or electrical wiring from corrosive fluids or gases that may escape
Transport Canada recommended revising proposed special condition no. 6 to refer to “essential systems” instead of “systems,” because the FAA previously found that wording acceptable for rechargeable lithium battery special conditions. Alternatively, Transport Canada recommended that the FAA be consistent and use “systems” for both rechargeable and non-rechargeable lithium battery special conditions in the future. The intent of this special condition is to address the hazards to the airplane regardless of the system critically. The FAA agrees with using “systems” in this special condition and in the next special conditions we propose for a rechargeable lithium battery installation.
Transport Canada recommended revising proposed special condition no. 6 to read, “. . .each non-rechargeable lithium battery installation must have provisions to prevent any hazardous effect on airplane structure or systems caused by the maximum amount of heat it can generate due to any
Transport Canada recommended including “unbalanced discharge” in the list of conditions intended to be prevented in proposed special condition no. 7. As a result of a comment from AIA addressed above, the FAA deleted proposed special condition no. 7 because compliance with special condition nos. 1 and 2 accomplish its safety objectives. Special conditions 1 and 2 also address unbalanced discharge.
Transport Canada recommended revising proposed special condition no. 8 to read, “. . . each non-rechargeable lithium battery installation must have a means to automatically
Transport Canada recommended adding a special condition to require instructions for continued airworthiness (ICAs) to address handling and storage of non-rechargeable lithium batteries at a minimum. The FAA has not added the recommended special condition because § 25.1529 requires ICAs for non-rechargeable lithium battery installations. To ensure compliance with § 25.1529, the FAA is documenting acceptable methods of compliance with § 25.1529 for non-rechargeable lithium battery installations as part of the certification process. These methods of compliance address the issues Transport Canada raised. The FAA previously included a special condition that requires compliance with § 25.1529 in rechargeable lithium battery special conditions. For consistency and the above-stated reasons, the FAA plans to no longer include that special condition in special conditions applicable to rechargeable lithium batteries.
Transport Canada recommended “the special condition be written in such a way as to drive the requirement for original equipment manufacturers to complete an adequate failure modes and effects analysis (FMEA) in order to discover and mitigate for all failure modes, including those that are less well known.” The FAA does not agree with the proposal. The current FAA AC 25.1309-1A and Aviation Rulemaking Advisory Committee (ARAC) recommended AC 25.1309-Arsenal contain guidance to utilize FMEA in the safety-assessment process. The FAA believes that these special conditions, and the hazards identified, drive the FMEA or any other system-safety assessment tool to comprehensively assess the risk of battery failures. We believe that we have accomplished Transport Canada's recommendation.
Transport Canada recommended changes to FAA TSO-142a,
Transport Canada recommended adding a special condition that reads, “
The FAA has determined that “uncontrolled” in special condition no. 2 should be “uncontrollable” to more accurately describe the concern. This revision does not change the intended meaning of this special condition.
Except as discussed above, the special conditions are adopted as proposed.
As discussed above, these special conditions are applicable to the Gulfstream Model GVI airplane. Should Gulfstream apply at a later date for a change to the type certificate to include another model incorporating the same novel or unusual design feature, these special conditions would apply to that model as well.
These special conditions are only applicable to design changes applied for after its effective date. The existing airplane fleet and follow-on deliveries of airplanes with previously certified non-rechargeable lithium battery installations are not affected.
These special conditions are not applicable to changes to previously certified non-rechargeable lithium battery installations where the only change is either cosmetic or relocating the installation to improve the safety of the airplane and occupants. The FAA determined that this exclusion is in the public interest because the need to meet all of the special conditions might otherwise deter design changes that solely involve relocating batteries to improve safety. A cosmetic change is a change in appearance only, and does not change any function or safety characteristic of the battery installation.
This action affects only certain novel or unusual design features on one model of airplane. It is not a rule of general applicability.
Aircraft, Aviation safety, Reporting and record keeping requirements.
The authority citation for these special conditions is as follows:
49 U.S.C. 106(g), 40113, 44701, 44702, 44704.
Accordingly, the following special conditions are part of the type certification basis for Gulfstream Model GVI airplanes.
In lieu of § 25.1353(b)(1) through (b)(4) at Amendment 25-113, each non-rechargeable lithium battery installation must:
1. Maintain safe cell temperatures and pressures under all foreseeable operating conditions to prevent fire and explosion.
2. Prevent the occurrence of self-sustaining, uncontrollable increases in temperature or pressure.
3. Not emit explosive or toxic gases, either in normal operation or as a result of its failure, that may accumulate in hazardous quantities within the airplane.
4. Meet the requirements of § 25.863.
5. Not damage surrounding structure or adjacent systems, equipment, or electrical wiring from corrosive fluids or gases that may escape in such a way as to cause a major or more-severe failure condition.
6. Have provisions to prevent any hazardous effect on airplane structure or systems caused by the maximum amount of heat it can generate due to any failure of it or its individual cells.
7. Have a failure sensing and warning system to alert the flightcrew if its failure affects safe operation of the airplane.
8. Have a means for the flightcrew or maintenance personnel to determine the battery charge state if the battery's function is required for safe operation of the airplane.
A battery system consists of the battery and any protective, monitoring, and alerting circuitry or hardware inside or outside of the battery. It also includes vents (where necessary) and packaging. For the purpose of these special conditions, a “battery” and “battery system” are referred to as a battery.
Federal Aviation Administration (FAA), DOT.
Final special conditions; request for comments.
These special conditions are issued for the Bombardier Inc. Model BD-700-2A12 and BD-700-2A13 airplanes. These airplanes will have a digital-systems network architecture composed of several connected networks that may allow access to or by external computer systems and networks, and may result in airplane systems-security vulnerabilities. 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.
This action is effective on Bombardier Inc. on April 22, 2016. We must receive your comments by June 6, 2016.
Send comments identified by docket number FAA-2016-4819 using any of the following methods:
•
•
•
•
Varun Khanna, FAA, Airplane and Flight Crew Interface, ANM-111, Transport Airplane Directorate, Aircraft Certification Service, 1601 Lind Avenue SW., Renton, Washington 98057-3356; telephone 425-227-1298; facsimile 425-227-1149.
The substance of these special conditions has been subject to the public comment process in several prior instances with no substantive comments received. The FAA therefore finds that good cause exists for making these special conditions effective upon publication in the
We invite 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 special conditions, explain the reason for any recommended change, and include supporting data.
We will consider all comments we receive by the closing date for comments. We may change these special conditions based on the comments we receive.
On June 13, 2012, Bombardier Inc. applied for an amended type certificate for their new Model BD-700-2A12 and BD-700-2A13 airplanes. These airplanes are derivatives of the Model BD-700 series of airplanes, and are marketed as the Bombardier Global 7000 and Global 8000, respectively. These airplanes are ultra-long-range, executive-interior business jets.
The Model BD-700-2A12 and BD-700-2A13 airplanes have a maximum certified passenger capacity of 19, and include new high-speed transonic wings with improved aerodynamic efficiency and a pressurized cabin for luxury interiors.
Under the provisions of Title 14, Code of Federal Regulations (14 CFR) 21.101, Bombardier Inc. must show that the Model BD-700-2A12 and BD-700-2A13 airplanes meet the applicable provisions of part 25 as amended by Amendments 25-1 through 25-137.
If the Administrator finds that the applicable airworthiness regulations (
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 § 21.101.
In addition to the applicable airworthiness regulations and special conditions, the Model BD-700-2A12 and BD-700-2A13 airplanes 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 14 CFR 11.19, in accordance with § 11.38, and they become part of the type certification basis under § 21.101.
The Model BD-700-2A12 and BD-700-2A13 airplanes will incorporate the following novel or unusual design feature: A digital-systems network architecture composed of several connected networks. This network architecture and network configuration will have the capability to allow access to or by external network sources, and may be used for or interfaced with a diverse set of functions, including:
• Flight-safety-related control, communication, and navigation systems (airplane-control domain);
• Operator business and administrative support (operator-information domain); and
• Passenger information and entertainment systems (passenger-entertainment domain).
The Model BD-700-2A12 and BD-700-2A13 airplanes' digital-systems network architecture is novel or unusual for commercial transport airplanes as it allows connection to airplane electronic systems and networks, and access from sources external to the airplane (
The existing regulations and guidance material did not anticipate these types of digital-system network architectures, nor access to airplane systems. Furthermore, 14 CFR part 25 regulations, and current system-safety assessment policy and techniques, do not address potential security vulnerabilities by unauthorized access to airplane data busses and servers. Therefore, these special conditions are issued to ensure that the security, integrity, and availability of airplane systems are not compromised by certain wired or wireless electronic connections between airplane data busses and networks.
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.
As discussed above, these special conditions are applicable to the Model BD-700-2A12 and BD-700-2A13 airplanes. Should Bombardier Inc. apply at a later date for a change to the type certificate to include another model incorporating the same novel or unusual design feature, these special conditions would apply to that model as well.
This action affects only a certain novel or unusual design feature on one model series of airplanes. It is not a rule of general applicability.
The substance of these special conditions has been subjected to the notice and comment period in several prior instances and has been derived without substantive change from those previously issued. It is unlikely that prior public comment would result in a significant change from the substance contained herein. Therefore, the FAA has determined that prior public notice and comment are unnecessary and impracticable, and good cause exists for adopting these special conditions upon issuance. The FAA is requesting comments to allow interested persons to submit views that may not have been submitted in response to the prior opportunities for comment described above.
Aircraft, Aviation safety, Reporting and recordkeeping requirements.
The authority citation for these special conditions is as follows:
49 U.S.C. 106(g), 40113, 44701, 44702, 44704.
Accordingly, pursuant to the authority delegated to me by the Administrator, the following special conditions are issued as part of the type certification basis for electronic system-security protection from unauthorized external access on Bombardier Inc. Model BD-700-2A12 and BD-700-2A13 airplanes.
1. The applicant must ensure that the airplane electronic systems are protected from access by unauthorized sources external to the airplane, including those possibly caused by maintenance activity.
2. The applicant must ensure that electronic system-security threats are identified and assessed, and that effective electronic system-security protection strategies are implemented to protect the airplane from all adverse impacts on safety, functionality, and continued airworthiness.
3. The applicant must establish appropriate procedures to allow the operator to ensure that continued airworthiness of the airplane is maintained, including all post-type-certification modifications that may have an impact on the approved electronic system-security safeguards.
Federal Aviation Administration (FAA), DOT.
Final special conditions; request for comments.
These special conditions are issued for the Gulfstream Aerospace Corporation (Gulfstream) Model GVII-G500 airplane. These airplanes will
This action is effective on Gulfstream Aerospace Corporation on April 22, 2016. We must receive your comments by June 6, 2016.
Send comments identified by docket number FAA-2016-4238 using any of the following methods:
•
•
•
•
Varun Khanna, FAA, Airplane and Flight Crew Interface, ANM-111, Transport Airplane Directorate, Aircraft Certification Service, 1601 Lind Avenue SW., Renton, Washington, 98057-3356; telephone 425-227-1298; facsimile 425-227-1149.
The substance of these special conditions has been subject to the public comment process in several prior instances with no substantive comments received. The FAA therefore finds that good cause exists for making these special conditions effective upon publication in the
We invite 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 special conditions, explain the reason for any recommended change, and include supporting data.
We will consider all comments we receive by the closing date for comments. We may change these special conditions based on the comments we receive.
On March 29, 2012, Gulfstream Aerospace Corporation applied for a type certificate for their new Model GVII-G500 airplane.
The Model GVII-G500 airplane will be a business jet capable of accommodating up to 19 passengers. It will incorporate a low, swept-wing design with winglets and a T-tail. The powerplant will consist of two aft-fuselage-mounted Pratt & Whitney turbofan engines.
Under the provisions of Title 14, Code of Federal Regulations (14 CFR) 21.17, Gulfstream must show that the Model GVII-G500 airplane meets the applicable provisions of part 25, as amended by Amendments 25-1 through 25-137.
If the Administrator finds that the applicable airworthiness regulations (
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, these special conditions would also apply to the other model under § 21.101.
In addition to the applicable airworthiness regulations and special conditions, the Model GVII-G500 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 14 CFR 11.19, in accordance with § 11.38, and they become part of the type certification basis under § 21.17.
The Model GVII-G500 airplane will incorporate the following novel or unusual design feature: A digital-systems network architecture composed of several connected networks. This network architecture and network configuration will have the capability to allow access to or by external network sources, and may be used for or interfaced with a diverse set of functions, including:
• Flight-safety-related control, communication, and navigation systems (airplane-control domain);
• Operator business and administrative support (operator-information domain); and
• Passenger information and entertainment systems (passenger-entertainment domain).
The Model GVII-G500 airplane's digital-systems network architecture is novel or unusual for commercial transport airplanes as it allows connection to airplane electronic systems and networks, and access from sources external to the airplane (
The existing regulations and guidance material did not anticipate these types of digital-system architectures, nor access to airplane systems. Furthermore,
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.
As discussed above, these special conditions are applicable to the Model GVII-G500 airplane. Should Gulfstream apply at a later date for a change to the type certificate to include another model incorporating the same novel or unusual design feature, these special conditions would apply to that model as well.
This action affects only a certain novel or unusual design feature on one model series of airplane. It is not a rule of general applicability.
The substance of these special conditions has been subjected to the notice and comment period in several prior instances and has been derived without substantive change from those previously issued. It is unlikely that prior public comment would result in a significant change from the substance contained herein. Therefore, the FAA has determined that prior public notice and comment are unnecessary and impracticable, and good cause exists for adopting these special conditions upon issuance. The FAA is requesting comments to allow interested persons to submit views that may not have been submitted in response to the prior opportunities for comment described above.
Aircraft, Aviation safety, Reporting and recordkeeping requirements.
The authority citation for these special conditions is as follows:
49 U.S.C. 106(g), 40113, 44701, 44702, 44704.
Accordingly, pursuant to the authority delegated to me by the Administrator, the following special conditions are issued as part of the type certification basis for electronic system-security protection from unauthorized external access on the Gulfstream Aerospace Corporation Model GVII-G500 airplane.
1. The applicant must ensure that the airplane electronic systems are protected from access by unauthorized sources external to the airplane, including those possibly caused by maintenance activity.
2. The applicant must ensure that electronic system-security threats are identified and assessed, and that effective electronic system-security protection strategies are implemented to protect the airplane from all adverse impacts on safety, functionality, and continued airworthiness.
3. The applicant must establish appropriate procedures to allow the operator to ensure that continued airworthiness of the airplane is maintained, including all post-type-certification modifications that may have an impact on the approved electronic system-security safeguards.
Federal Aviation Administration (FAA), DOT.
Final rule; request for comments.
We are adopting a new airworthiness directive (AD) for The Boeing Company Model 787-8 and 787-9 airplanes powered by General Electric (GE) GEnx-1B engines. This AD requires revising the airplane flight manual (AFM) to provide the flight crew a revised fan ice removal procedure and a new associated mandatory flight crew briefing to reduce the likelihood of engine damage due to fan ice shedding. This AD also removes certain dispatch relief. For airplanes with certain engines, this AD also requires reworking or replacing at least one engine. This AD was prompted by a recent engine fan blade rub event that caused an in-flight non-restartable power loss. We are issuing this AD to prevent susceptibility to heavy fan blade rubs, which could result in engine damage and a possible in-flight non-restartable power loss of one or both engines.
This AD is effective May 9, 2016.
The Director of the Federal Register approved the incorporation by reference of a certain publication listed in this AD as of May 9, 2016.
The Director of the Federal Register approved the incorporation by reference of a certain other publication listed in this AD as of March 18, 2016 (81 FR 14704, March 18, 2016).
We must receive comments on this AD by June 6, 2016.
You may send comments, using the procedures found in 14 CFR 11.43 and 11.45, by any of the following methods:
•
•
•
•
For service information identified in this final rule, contact General Electric Company, GE Aviation, Room 285, 1 Neumann Way, Cincinnati, OH 45215; phone: 513-552-3272; email:
You may examine the AD docket on the Internet at
Sue Lucier, Aerospace Engineer, Propulsion Branch, ANM-140S, FAA, Seattle Aircraft Certification Office (ACO), 1601 Lind Avenue SW., Renton, WA 98057-3356; phone: 425-917-6438; fax: 425-917-6590; email:
On March 14, 2016, we issued AD 2016-06-08, Amendment 39-18439 (81 FR 14704, March 18, 2016) (“AD 2016-06-08”), for Boeing Model 787-8 and 787-9 airplanes powered by GE GEnx engines. AD 2016-06-08 was prompted by a report of a significant fan rub event involving a GEnx-1B Performance Improvement Program (PIP) 2 engine, apparently caused by partial fan ice shedding and a resulting fan imbalance that in turn caused substantial damage to the engine and an in-flight non-restartable power loss. GEnx-1B PIP1 engines have model designators GEnx-1B( )/P1. GEnx-1B PIP2 engines have model designators GEnx-1B( )/P2.
We continue to investigate this issue with Boeing and GE; however, the engine damage appears to be a result of susceptibility to heavy fan blade rubs common to the GEnx-1B PIP2 engine. The other engine on the event airplane was an older design GEnx-1B PIP1 configuration that incurred expected wear and minor damage during the icing event and continued to operate normally. The event occurred in icing conditions at an altitude of 20,000 feet.
The urgency of this issue stems from the safety concern over continued safe flight and landing for airplanes that are powered by two GEnx-1B PIP2 engines operating in a similar environment to the event airplane. In this case both GEnx-1B PIP2 engines may be similarly damaged and unable to be restarted in flight. The potential for common cause failure of both engines in flight is an urgent safety issue.
AD 2016-06-08 requires revising the airplane flight manual (AFM) to provide the flight crew a new fan ice removal procedure to reduce the likelihood of engine damage due to fan ice shedding. AD 2016-06-08 also requires, for certain airplanes, reworking the fan stator module assembly on GEnx-1B PIP2 engines.
Susceptibility to heavy fan blade rubs, if not corrected, could result in engine damage and a possible in-flight non-restartable power loss of one or both engines. We are issuing this AD to correct the unsafe condition on these products.
The preamble to AD 2016-06-08 explains that we regard the requirements “interim action” and were considering further rulemaking. We now have determined that further rulemaking is indeed necessary, and this AD follows from that determination.
We reviewed GE GEnx-1B Service Bulletins 72-0309 R00, dated March 11, 2016; and 72-0314 R00, dated April 1, 2016. The service information describes procedures for reworking the fan stator module assembly on GEnx-1B PIP2 engines. This service information is reasonably available because the interested parties have access to it through their normal course of business or by the means identified in the
We are issuing this AD because we evaluated all the relevant information and determined the unsafe condition described previously is likely to exist or develop in other products of the same type design.
This AD requires revising the AFM to provide the flight crew a revised fan ice removal procedure and a new associated mandatory flight crew briefing to reduce the likelihood of engine damage due to fan ice shedding. This AD also removes certain dispatch relief. For an airplane with two GEnx-1B PIP2 engines having specified model and part numbers, this AD also requires reworking or replacing at least one engine.
We consider this AD interim action. This action addresses rework of a single engine on any airplane that has two GEnx-1B PIP2 engines having certain model and part numbers. We may consider issuing further rulemaking to require rework of the remainder of the GEnx-1B PIP2 engines in this fleet.
An unsafe condition exists that requires the immediate adoption of this AD. The FAA has found that the risk to the flying public justifies waiving notice and comment prior to adoption of this rule because susceptibility to heavy fan blade rubs could result in engine damage and a possible in-flight non-restartable power loss of one or both engines. Therefore, we find that notice and opportunity for prior public comment are impracticable and that good cause exists for making this amendment effective in less than 30 days.
The FAA has evaluated the safety risk associated with this condition and has determined that in the interest of safety it is necessary to mandate three actions:
• Revise the Boeing Model 787 AFM to provide the flight crew a revised fan ice removal procedure and a new daily flight crew briefing on the existing engine ice shed procedure. The compliance time is 7 days.
• Removes certain dispatch relief, effective within 7 days.
• Rework or replacement of at least one engine, for airplanes with two GEnx-1B PIP2 engines. The compliance time is about 150 calendar days after issuance of this AD. Boeing and the engine manufacturer, GE, have developed a maintenance plan to support this compliance schedule.
The FAA has determined that allowing for notice and public comment through a notice of proposed rulemaking (NPRM) prior to mandating these actions is neither practicable nor in the public interest.
Recognizing the urgency of this safety issue, this AD represents a compressed schedule to rework a large number of airplanes located around the world. Both specialized tooling and trained personnel are required on-site to perform the rework at various maintenance facilities around the world. To complete the work, 29 airlines will need to reallocate 176 airplanes from revenue service to maintenance in order to conduct the (on-wing) rework. The FAA has determined that 150 days is the minimum time to rework one engine per airplane on the entire fleet.
Issuing an NPRM would require time to allow for public comment, and time for the FAA to consider and respond to those comments. As a result, the time allowed for the operators to perform the engine rework would be significantly reduced from 150 days, owing to the time that elapsed during the notice and comment period.
As a result, the considerable reduction in allowable compliance time would require operators to perform the rework significantly out of sequence with the maintenance schedule plan. In some cases, airplanes could be grounded. Thus, the reduced compliance time could substantially disrupt certain operators. The FAA
This AD is a final rule that involves requirements affecting flight safety and was not preceded by notice and an opportunity for public comment. However, we invite you to send any written data, views, or arguments about this AD. Send your comments to an address listed under the
We will post all comments we receive, without change, to
We estimate that this AD affects 43 airplanes of U.S. registry. We estimate the following costs to comply with this AD:
Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. “Subtitle VII: Aviation Programs” describes in more detail the scope of the Agency's authority.
We are issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: “General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.
This AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.
For the reasons discussed above, I certify that this AD:
(1) Is not a “significant regulatory action” under Executive Order 12866,
(2) Is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979),
(3) Will not affect intrastate aviation in Alaska, and
(4) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.
Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.
Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:
49 U.S.C. 106(g), 40113, 44701.
This AD is effective May 9, 2016.
This AD affects AD 2016-06-08, Amendment 39-18439 (81 FR 14704, March 18, 2016) (“AD 2016-06-08”).
This AD applies to The Boeing Company Model 787-8 and 787-9 airplanes, certificated in any category, powered by General Electric (GE) GEnx-1B engines.
Air Transport Association (ATA) of America Code 72, engines.
This AD was prompted by a recent engine fan blade rub event that caused an in-flight non-restartable power loss. We are issuing this AD to prevent susceptibility to heavy fan blade rubs, which could result in engine damage and a possible in-flight non-restartable power loss of one or both engines.
Comply with this AD within the compliance times specified, unless already done.
Within 7 days after the effective date of this AD, revise the Certificate Limitations chapter of the applicable Boeing 787 AFM to include the statement provided in figure 1 to paragraph (g) of this AD. This may be done by inserting a copy of this AD into the AFM. Once accomplished, the AFM revision required by this paragraph terminates the requirements of paragraph (g) of AD 2016-06-08, and the AFM revision required by paragraph (g) of AD 2016-06-08 must be removed from the AFM.
Within 7 days after the effective date of this AD, revise the Operating Procedures chapter of the Boeing 787 AFM to include the statement provided in figure 2 to paragraph (h) of this AD. This may be done by inserting a copy of this AD into the AFM. Once accomplished, the AFM revision required by this AD terminates the requirements of paragraph (h) of AD 2016-06-08, and the AFM revision required by paragraph (h) of AD 2016-06-08 must be removed from the AFM.
As of 7 days after the effective date of this AD: Notwithstanding the provisions of the operator's minimum equipment list (MEL), dispatch of an airplane is prohibited unless the equipment specified in paragraph (i)(1) and (i)(2) is operational.
(1) At least one Engine Anti-Ice (EAI) Indication.
(2) At least one Ice Detector.
For an airplane powered by two engines having any model number GEnx-1B64/P2, -1B67/P2, -1B70/P2, -1B70C/P2, -1B70/75/P2, or -1B74/75/P2, and any GEnx engine
(1) Rework at least one engine in accordance with paragraph 3.B. or 3.C. of the Accomplishment Instructions of GE GEnx-1B Service Bulletin 72-0309 R00, dated March 11, 2016; or paragraph 3.B. or 3.C. of the Accomplishment Instructions of GE GEnx-1B Service Bulletin 72-0314 R00, dated April 1, 2016. Although GE GEnx Service Bulletins GEnx-1B 72-0314 R00, dated April 1, 2016; and GEnx-1B 72-0309 R00, dated March 11, 2016; specify submitting certain tip clearance measurements to GE, no report is required by this AD.
(2) Remove at least one engine and replace with an engine that is eligible for installation that is not identified in the introductory text to paragraph (j) of this AD.
(1) The Manager, Seattle Aircraft Certification Office (ACO), FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the manager of the ACO, send it to the attention of the person identified in paragraph (l) of this AD. Information may be emailed to:
(2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office.
(3) An AMOC that provides an acceptable level of safety may be used for any repair, modification, or alteration required by this AD if it is approved by the Boeing Commercial Airplanes Organization Designation Authorization (ODA) that has been authorized by the Manager, Seattle ACO, to make those findings. To be approved, the repair method, modification deviation, or alteration deviation must meet the certification basis of the airplane, and the approval must specifically refer to this AD.
For more information about this AD, contact Sue Lucier, Aerospace Engineer, Propulsion Branch, ANM-140S, FAA, Seattle ACO, 1601 Lind Avenue SW., Renton, WA 98057-3356; phone: 425-917-6438; fax: 425-917-6590; email:
(1) The Director of the Federal Register approved the incorporation by reference (IBR) of the service information listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.
(2) You must use this service information as applicable to do the actions required by this AD, unless the AD specifies otherwise.
(3) The following service information was approved for IBR on May 9, 2016.
(i) GE GEnx-1B Service Bulletin 72-0314 R00, dated April 1, 2016.
(ii) Reserved.
(4) The following service information was approved for IBR on March 18, 2016 (81 FR 14704, March 18, 2016).
(i) GE GEnx-1B Service Bulletin 72-0309 R00, dated March 11, 2016.
(ii) Reserved.
(5) For service information identified in this AD, contact General Electric Company, GE Aviation, Room 285, 1 Neumann Way, Cincinnati, OH 45215; phone: 513-552-3272; email:
(6) You may view this service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, WA. For information on the availability of this material at the FAA, call 425-227-1221.
(7) You may view this service information that is incorporated by reference at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to
Federal Aviation Administration (FAA), DOT.
Final rule.
We are superseding Airworthiness Directive (AD) 2012-17-13, which applied to certain The Boeing Company Model 707 airplanes, and Model 720 and 720B series airplanes. For certain airplanes, AD 2012-17-13 required using redefined flight cycle counts; determining the type of material of the horizontal stabilizer, rear spar, and upper and lower chords on the inboard and outboard ends of the rear spar; repetitively inspecting for cracking of the horizontal stabilizer components; and repairing or replacing the chord, or modifying chord segments made of 7079 aluminum, if necessary. For all airplanes, AD 2012-17-13 required inspecting certain structurally significant items, and repairing discrepancies if necessary. This new AD adds a requirement to replace all chord segments made of 7079 aluminum with new, improved chord segments made of 7075 aluminum. This AD was prompted by a determination that all chord segments made of 7079 aluminum must be replaced with new, improved chord segments made of 7075 aluminum. We are issuing this AD to detect and correct stress corrosion and potential early fatigue cracking in the horizontal stabilizer, which could result in reduced structural integrity of the horizontal stabilizer.
This AD is effective May 27, 2016.
The Director of the Federal Register approved the incorporation by reference of a certain publication listed in this AD as of May 27, 2016.
The Director of the Federal Register approved the incorporation by reference of certain other publications listed in this AD as of October 16, 2012 (77 FR 55681, September 11, 2012).
For service information identified in this final rule, contact Boeing Commercial Airplanes, Attention: Data & Services Management, 3855 Lakewood Boulevard, MC D800-0019, Long Beach, CA 90846-0001; telephone 206-544-5000, extension 2; fax 206-766-5683; Internet
You may examine the AD docket on the Internet at
Chandra Ramdoss, Aerospace Engineer, Airframe Branch, ANM-120L, FAA, Los Angeles Aircraft Certification Office (ACO), 3960 Paramount Boulevard, Lakewood, CA 90712-4137; phone: 562-627-5239; fax: 562-627-5210; email:
We issued a notice of proposed rulemaking (NPRM) to amend 14 CFR part 39 to supersede AD 2012-17-13, Amendment 39-17176 (77 FR 55681, September 11, 2012) (“AD 2012-17-13”). AD 2012-17-13 applied to certain The Boeing Company Model 707 airplanes, and Model 720 and 720B series airplanes. The NPRM published in the
We gave the public the opportunity to participate in developing this AD. The following presents the comments received on the NPRM and the FAA's response to each comment.
Boeing asked that we clarify the description of the affected components specified in paragraph (i) of the proposed AD, which is a restatement of paragraph (i) of AD 2012-17-13. Boeing stated that the intent of paragraph (i) of AD 2012-17-13 was to specify the inspection requirements for rear spar upper inboard chord segments made from 7075 aluminum. Boeing added that the restatement in paragraph (i) of the proposed AD specifies, “For all airplanes with horizontal stabilizer components made from 7075 . . .” and noted that this description could apply to any chord segment, not just the inboard upper. Boeing asked that the description be clarified to specify “any horizontal stabilizer with a rear spar upper inboard chord segment made from 7075 aluminum, as determined during the inspection required by paragraph (h) of this AD.”
We agree to clarify paragraph (i) of this AD. The inspection required by paragraph (i) of this AD must be done on upper chords made from 7075 aluminum that are on the inboard end of the rear spar, as specified in Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; and Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014; which are the appropriate sources of service information for accomplishing the required actions. We have revised paragraph (i) of this AD to clarify the inspection requirements. No additional action is necessary for operators that have already complied with paragraph (i) of this AD.
Boeing also asked that we clarify the language in the restatement of actions specified in paragraph (j) of the proposed AD in order to specify that the inspections in paragraph (i) of the proposed AD can only be deferred for 4,000 flight cycles if the upper inboard chord is replaced with a new chord. Boeing stated that changing paragraph (i) of the proposed AD ensures that it is clear that the inspection can only be deferred for 4,000 flight cycles if the upper inboard chord is replaced.
We agree with the commenter for the reason provided. We have changed paragraph (j) of this AD to specify “For airplanes on which the rear spar upper inner chord is replaced with a new chord . . . :”
Boeing also asked that we clarify the language in the new actions specified in paragraph (q) of the proposed AD. Boeing stated that paragraph (j) of the proposed AD states when to resume the inspections after the chord is replaced. Boeing added that paragraph (i) of the proposed AD states the type of inspection and the repetitive inspection interval. Therefore, Boeing stated that paragraph (q) of the proposed AD should point to paragraph (i) of the proposed AD.
We agree to clarify paragraph (q) of this AD. As noted above, paragraph (j) of the this AD specifies inspecting the new chord within 4,000 flight cycles after the chord replacement, as required by paragraph (i) of this AD, and repeating the inspections thereafter at the times specified in paragraph (i) of this AD. Therefore, we have included similar language in paragraph (q) of this AD.
In addition, Boeing asked that we include 707 in the title for “Boeing Service Bulletin 3381,” as identified in paragraphs (k) and (l) of the proposed AD, to be consistent with all the other service information references in the NPRM.
We agree with the commenter for the reasons provided. We have changed the service information references in paragraphs (k)(3)(i) and (l) of this AD to specify “Boeing 707 Service Bulletin 3381.”
Boeing also asked that we change the semi-colon (located between the service information references) in paragraph (k)(3)(ii) of the proposed AD to a comma, because it breaks up the sentence in an unintended way.
We do not agree to change the semi-colon in paragraph (k)(3)(ii) of this AD. In ADs, we use a semi-colon to separate service information references, except in cases where the semi-colon between service information might cause confusion,
We reviewed the available data and determined that air safety and the public interest require adopting this AD with the changes described previously, and minor editorial changes. We have determined that these minor changes:
• Are consistent with the intent that was proposed in the NPRM for correcting the unsafe condition; and
• Do not add any additional burden upon the public than was already proposed in the NPRM.
We reviewed Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014. The service
We estimate that this AD affects 10 airplanes of U.S. registry.
We estimate the following costs to comply with this AD:
Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, Section 106, describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the Agency's authority.
We are issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701, “General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.
We have determined that this AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.
For the reasons discussed above, I certify that this AD:
(1) Is not a “significant regulatory action” under Executive Order 12866,
(2) Is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979),
(3) Will not affect intrastate aviation in Alaska, and
(4) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.
Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.
Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:
49 U.S.C. 106(g), 40113, 44701.
This AD is effective May 27, 2016.
This AD replaces AD 2012-17-13, Amendment 39-17176 (77 FR 55681, September 11, 2012).
This AD applies to The Boeing Company airplanes, certificated in any category; identified in paragraphs (c)(1) and (c)(2) of this AD.
(1) Model 707 airplanes identified in Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014.
(2) Model 720 and 720B series airplanes identified in Boeing 707 Alert Service Bulletin A3516, dated April 4, 2008.
Air Transport Association (ATA) of America Code 55, Stabilizers.
This AD was prompted by a determination that all chord segments made of 7079 aluminum must be replaced with new, improved chord segments made of 7075 aluminum. We are issuing this AD to detect and correct stress corrosion and potential early fatigue cracking in the horizontal stabilizer, which could result in reduced structural integrity of the horizontal stabilizer.
Comply with this AD within the compliance times specified, unless already done.
This paragraph restates the requirements of paragraph (g) of AD 2012-17-13, Amendment 39-17176 (77 FR 55681, September 11, 2012), with revised service information. Flight cycles, as used in this AD, must be counted as defined in the service information identified in paragraph (g)(1), (g)(2), or (g)(3) of this AD.
(1) Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007 (for Model 707 airplanes).
(2) Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014 (for Model 707 airplanes).
(3) Boeing 707 Alert Service Bulletin A3516, dated April 4, 2008 (for Model 707 airplanes, and Model 720 and 720B series airplanes).
This paragraph restates the actions required by paragraph (h) of AD 2012-17-13, Amendment 39-17176 (77 FR 55681, September 11, 2012), with revised service information. For airplanes identified in Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014: At the earlier of the times specified in paragraphs (h)(1) and (h)(2) of this AD, determine the type of material of the horizontal stabilizer, rear spar, upper chords, and lower chords on the inboard and outboard ends of the rear spar, in accordance with Part 2 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014.
(1) Within 180 days after October 16, 2012 (the effective date of AD 2012-17-13, Amendment 39-17176 (77 FR 55681, September 11, 2012)).
(2) Before further flight after any horizontal stabilizer is replaced after October 16, 2012.
This paragraph restates the actions required by paragraph (i) of AD 2012-17-13, Amendment 39-17176 (77 FR 55681, September 11, 2012), with revised service information and affected component description. For airplanes with any horizontal stabilizer with a rear spar upper inboard chord segment made from 7075 aluminum, as determined during the inspection required by paragraph (h) of this AD: Within 180 days after October 16, 2012 (the effective date of AD 2012-17-13), and before further flight after any replacement of the horizontal stabilizer, do a special detailed inspection for cracking of the upper chord on the inboard end of the rear spar on both the left and right side horizontal stabilizers, from stabilizer station −13.179 to 92.55, in accordance with Part 3 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014. Repeat the inspections thereafter at intervals not to exceed 500 flight cycles, and before further flight after any replacement of the horizontal stabilizer, except as provided by paragraph (j) of this AD. If any cracking is found, before further flight, either repair the cracking in accordance with Part 3 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014, except as required by paragraph (n) of this AD; or replace the chord with a new chord, in accordance with Part 6 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014.
This paragraph restates the actions required by paragraph (j) of AD 2012-17-13, Amendment 39-17176 (77 FR 55681, September 11, 2012), with revised service information and revised langue for affected airplanes. For airplanes on which the rear spar upper inner chord is replaced with a new chord in accordance with Part 6 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014: Within 4,000 flight cycles after the chord replacement, inspect the new chord, as required by paragraph (i) of this AD, and repeat the inspections thereafter at the times specified in paragraph (i) of this AD.
This paragraph restates the actions required by paragraph (k) of AD 2012-17-13, Amendment 39-17176 (77 FR 55681, September 11, 2012), with revised service information. For airplanes with horizontal stabilizers that have components of the chords of the rear spar made from 7079 aluminum, as determined during the inspection required by paragraph (h) of this AD: Within 180 days after October 16, 2012 (the effective date of AD 2012-17-13), do the actions required by paragraphs (k)(1), (k)(2), and (k)(3) of this AD, and repeat those actions at the applicable intervals specified in paragraphs (k)(1), (k)(2), and (k)(3) of this AD.
(1) Do a special detailed inspection for cracking of the upper chord of the inboard side of the rear spar of both the left and right side horizontal stabilizers from stabilizer station −13.179 to 92.55, in accordance with Part 3 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014. Repeat the inspection thereafter at intervals not to exceed 250 flight cycles or 180 days, whichever occurs first. If any cracking is found during any inspection required by this paragraph, before further flight, either repair the cracking, in accordance with Part 3 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014, except as required by paragraph (n) of this AD; or replace the chord with a new chord, in accordance with Part 6 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014.
(2) Do a high frequency eddy current inspection for cracking of the web flanges of the upper and lower chords of the rear spar in the left and right side horizontal stabilizers from stabilizer stations 92.55 to 272.55, in accordance with Part 4 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014. Repeat the inspection thereafter at intervals not to exceed 1,000 flight cycles or 180 days, whichever occurs first. If any cracking is found during any inspection required by this paragraph, before further flight, do the actions specified in paragraph (k)(2)(i) or (k)(2)(ii) of this AD.
(i) Determine whether the cracking meets the limits specified in Part 4 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014, and whether a previous repair has been done; determine if all 7079 upper and lower chord segments installed on the horizontal stabilizer have had the Part II, Group 1, Preventative Modification specified in Boeing 707 Service Bulletin 3356 done; and do all applicable repairs and modifications, in accordance with the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007' or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014. Do the actions required by this paragraph in accordance with Part 4 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014, except as required by paragraph (n) of this AD. Do all applicable repairs and modifications before further flight.
(ii) Replace the chord with a new chord, in accordance with Part 6 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014.
(3) Do low frequency eddy current (LFEC) inspections for cracking of the forward skin flanges of the upper and lower chords of the rear spar in the left and right side horizontal stabilizers from stabilizer stations −13.179 to 272.55 (for lower chords) and 92.55 to 272.55 (for upper chords), in accordance with Part 5 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014. Repeat the inspections thereafter at intervals not to exceed 1,000 flight cycles or 180 days, whichever occurs first. If any cracking is found during any inspection required by this paragraph, before further flight, do the actions specified in either paragraph (k)(3)(i) or paragraph (k)(3)(ii) of this AD.
(i) Repair any cracking, determine whether all 7079 upper and lower chord segments installed on the horizontal stabilizer have had the Part II—Preventative Modification specified in Boeing 707 Service Bulletin 3381 done, and do all applicable modifications, in accordance with the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014. Do the
(ii) Replace the chord with a new chord, in accordance with Part 6 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014.
This paragraph restates the actions required by paragraph (l) of AD 2012-17-13, Amendment 39-17176 (77 FR 55681, September 11, 2012), with revised service information. For airplanes identified in Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014, with horizontal stabilizers that have rear spar chord components made from 7079 aluminum and have not had embodied the modification of Part II of Boeing 707 Service Bulletin 3381, dated July 25, 1980; or Boeing 707 Service Bulletin 3381, Revision 1, dated July 31, 1981: Before further flight after determining the type of material in accordance with paragraph (h) of this AD, modify all 7079 chord segments installed on the horizontal stabilizer, in accordance with Part 5 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014; or replace the chord, in accordance with Part 6 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014.
This paragraph restates the actions required by paragraph (m) of AD 2012-17-13, Amendment 39-17176 (77 FR 55681, September 11, 2012). For all airplanes: Within 180 days or 1,000 flight cycles after October 16, 2012 (the effective date of AD 2012-17-13), whichever occurs first, do the inspections of the applicable structurally significant items specified in and in accordance with the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3516, dated April 4, 2008. If any cracking is found, before further flight, repair using a method approved in accordance with the procedures specified in paragraph (r) of this AD. The inspections required by AD 85-12-01 R1, Amendment 39-5439 (51 FR 36002, October 8, 1986), are still required, except, as of October 16, 2012 (the effective date of AD 2012-17-13), the flight cycle interval for the repetitive inspections specified in paragraph 1.E., “Compliance,” of Boeing 707 Alert Service Bulletin A3516, dated April 4, 2008, must be counted in accordance with the requirements of paragraph (g) of this AD.
This paragraph restates the actions required by paragraph (n) of AD 2012-17-13, Amendment 39-17176 (77 FR 55681, September 11, 2012), with revised service information. If any cracking is found during any inspection required by this AD, and Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014, specifies to contact Boeing for appropriate action: Before further flight, repair the cracking using a method approved in accordance with the procedures specified in paragraph (r) of this AD.
This paragraph restates the requirements of paragraph (o) of AD 2012-17-13, Amendment 39-17176 (77 FR 55681, September 11, 2012), with revised service information. Where Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014, specifies that operators “refer to” nondestructive test (NDT) procedures, the procedures must be done in accordance with the service information identified in paragraphs (o)(1), (o)(2), and (o)(3) of this AD, as applicable.
(1) Figure 20, “Electrical Conductivity Measurement for Aluminum,” of Subject 51-00-00, “Structures-General,” of Part 6—Eddy Current, of the Boeing 707/720 Nondestructive Test Manual, Document D6-48023, Revision 118, dated July 15, 2011.
(2) Subject 55-10-07, “Horizontal Stabilizer,” of Part 6—Eddy Current, of the Boeing 707/720 Nondestructive Test Manual, Document D6-48023, Revision 118, dated July 15, 2011.
(3) Subject 51-01-00, “Orientation and Preparation for Testing” of Part 1—General, of the Boeing 707/720 Nondestructive Test Manual, Document D6-48023, Revision 118, dated July 15, 2011.
This paragraph restates the parts installation prohibition required by paragraph (p) of AD 2012-17-13, Amendment 39-17176 (77 FR 55681, September 11, 2012), with revised service information. As of October 16, 2012 (the effective date of AD 2012-17-13, Amendment 39-17176 (77 FR 55681, September 11, 2012)), no person may install any horizontal stabilizer assembly with any chord segment having a part number other than that identified in paragraph 2.C.2. of Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007; or Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014, on any airplane.
Within 48 months after the effective date of this AD: Replace all 7079 aluminum chord segments of the upper and lower chords installed on the horizontal stabilizer with 7075 aluminum chord segments, in accordance with Part 6 of the Accomplishment Instructions of Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014. Within 4,000 flight cycles after accomplishing the replacements required by this paragraph, inspect the new chord, as required by paragraph (i) of this AD, and repeat the inspections thereafter at the times specified in paragraph (i) of this AD.
(1) The Manager, Los Angeles Aircraft Certification Office (ACO), FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the manager of the ACO, send it to the attention of the person identified in paragraph (s) of this AD. Information may be emailed to:
(2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office.
(3) An AMOC that provides an acceptable level of safety may be used for any repair, modification, or alteration required by this AD if it is approved by the Boeing Commercial Airplanes Organization Designation Authorization (ODA) that has been authorized by the Manager, Los Angeles ACO, to make those findings. To be approved, the repair method, modification deviation, or alteration deviation must meet the certification basis of the airplane, and the approval must specifically refer to this AD.
(4) AMOCs approved for AD 2012-17-13, Amendment 39-17176 (77 FR 55681, September 11, 2012), are approved as AMOCs for the corresponding provisions of this AD.
For more information about this AD, contact Chandra Ramdoss, Aerospace Engineer, Airframe Branch, ANM-120L, FAA, Los Angeles ACO, 3960 Paramount Boulevard, Lakewood, CA 90712-4137; phone: 562-627-5239; fax: 562-627-5210; email:
(1) The Director of the Federal Register approved the incorporation by reference (IBR) of the service information listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.
(2) You must use this service information as applicable to do the actions required by this AD, unless the AD specifies otherwise.
(i) Boeing 707 Alert Service Bulletin A3515, Revision 1, dated October 10, 2014.
(ii) Reserved.
(3) The following service information was approved for IBR on October 16, 2012 (77 FR 55681, September 11, 2012).
(i) Boeing 707 Alert Service Bulletin A3515, dated December 19, 2007.
(ii) Boeing 707 Alert Service Bulletin A3516, dated April 4, 2008.
(iii) Subject 51-00-00, “Structures-General,” Figure 20, “Electrical Conductivity Measurement for Aluminum,” of Part 6—Eddy Current, of the Boeing 707/720 Nondestructive Test Manual, Document D6-48023, Revision 118, dated July 15, 2011. The revision level of this document is identified on only the manual revision Transmittal Sheet.
(iv) Subject 51-01-00, “Orientation and Preparation for Testing” of Part 1—General, of the Boeing 707/720 Nondestructive Test Manual, Document D6-48023, Revision 118, dated July 15, 2011. The revision level of this document is identified on only the manual revision Transmittal Sheet.
(v) Subject 55-10-07, “Horizontal Stabilizer,” of Part 6—Eddy Current, of the Boeing 707/720 Nondestructive Test Manual, Document D6-48023, Revision 118, dated July 15, 2011. The revision level of this document is identified on only the manual revision Transmittal Sheet.
(4) For service information identified in this AD, contact Boeing Commercial Airplanes, Attention: Data & Services Management, 3855 Lakewood Boulevard, MC D800-0019, Long Beach, CA 90846-0001; telephone 206-544-5000, extension 2; fax 206-766-5683; Internet
(5) You may view this service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, WA. For information on the availability of this material at the FAA, call 425-227-1221.
(6) You may view this service information that is incorporated by reference at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to:
Federal Aviation Administration (FAA), DOT.
Final rule.
This action establishes Class E airspace in Coldwater, KS. Controlled airspace is necessary to accommodate new Standard Instrument Approach Procedures (SIAPs) at Comanche County Airport. The FAA is taking this action to enhance the safety and management of Instrument Flight Rule (IFR) operations at the airport. Additionally, to this action corrects the spelling of the airport name to Comanche County Airport, inadvertently misspelled in the proposal.
Effective 0901 UTC, July 21, 2016. The Director of the Federal Register approves this incorporation by reference action under title 1, Code of Federal Regulations, part 51, subject to the annual revision of FAA Order 7400.9 and publication of conforming amendments.
FAA Order 7400.9Z, Airspace Designations and Reporting Points, and subsequent amendments can be viewed on line at
FAA Order 7400.9, Airspace Designations and Reporting Points, is published yearly and effective on September 15.
Rebecca Shelby, Central Service Center, Operations Support Group, Federal Aviation Administration, Southwest Region, 10101 Hillwood Parkway, Fort Worth, TX 76177; telephone: (817) 222-5857.
The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part, A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of airspace necessary to ensure the safety of aircraft and the efficient use of airspace. This regulation is within the scope of that authority as it establishes controlled airspace at Comanche County Airport, Coldwater, KS.
On February 11, 2016, the FAA published in the
Class E airspace designations are published in paragraph 6005 of FAA Order 7400.9Z dated August 6, 2015, and effective September 15, 2015, which is incorporated by reference in 14 CFR part 71.1. The Class E airspace designations listed in this document will be published subsequently in the Order.
This document amends FAA Order 7400.9Z, airspace Designations and Reporting Points, dated August 6, 2015, and effective September 15, 2015. FAA Order 7400.9Z is publicly available as listed in the
This amendment to Title 14, Code of Federal Regulations (14 CFR) part 71 establishes Class E airspace extending upward from 700 feet above the surface within a 7.5-mile radius of Comanche County Airport, Coldwater, KS, to accommodate new standard instrument approach procedures. Controlled airspace is needed for the safety and management of IFR operations at the airport. Additionally, the airport name is corrected from Commanche County Airport to Comanche County Airport.
Class E airspace designations are published in Paragraph 6005 of FAA Order 7400.9Z, dated August 6, 2015, and effective September 15, 2015, which is incorporated by reference in 14 CFR 71.1. The Class E airspace designations listed in this document will be published subsequently in the Order.
The FAA has determined that this regulation only involves an established body of technical regulations for which
The FAA has determined that this action qualifies for categorical exclusion under the National Environmental Policy Act in accordance with FAA Order 1050.1F, “Environmental Impacts: Policies and Procedures,” paragraph 5-6.5. This airspace action is not expected to cause any potentially significant environmental impacts, and no extraordinary circumstances exists that warrant preparation of an environmental assessment.
Airspace, Incorporation by reference, Navigation (air).
In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:
49 U.S.C. 106(f), 106(g); 40103, 40113, 40120, E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.
That airspace extending upward from 700 feet above the surface within a 7.5-mile radius of Comanche County Airport.
Federal Aviation Administration (FAA), DOT.
Final rule.
This action establishes Class E airspace in Moriarty, NM. Controlled airspace is necessary to accommodate new Area Navigation (RNAV) Standard Instrument Approach Procedures at Moriarty Airport. The FAA is taking this action to enhance the safety and management of Instrument Flight Rule (IFR) operations at the airport.
Effective 0901 UTC, May 26, 2016. The Director of the Federal Register approves this incorporation by reference action under title 1, Code of Federal Regulations, part 51, subject to the annual revision of FAA Order 7400.9 and publication of conforming amendments.
FAA Order 7400.9Z, Airspace Designations and Reporting Points, and subsequent amendments can be viewed on line at
FAA Order 7400.9, Airspace Designations and Reporting Points, is published yearly and effective on September 15.
Raul Garza, Jr., Central Service Center, Operations Support Group, Federal Aviation Administration, Southwest Region, 10101 Hillwood Parkway, Fort Worth, TX 76177; telephone: (817) 222-5874.
The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part, A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of airspace necessary to ensure the safety of aircraft and the efficient use of airspace. This regulation is within the scope of that authority as it establishes controlled airspace at Moriarty Airport, Moriarty, NM.
On February 3, 2016, the FAA published in the
Class E airspace designations are published in paragraph 6005 of FAA Order 7400.9Z dated August 6, 2015, and effective September 15, 2015, which is incorporated by reference in 14 CFR part 71.1. The Class E airspace designations listed in this document will be published subsequently in the Order.
This document amends FAA Order 7400.9Z, airspace Designations and Reporting Points, dated August 6, 2015, and effective September 15, 2015. FAA Order 7400.9Z is publicly available as listed in the
This amendment to Title 14, Code of Federal Regulations (14 CFR) part 71 establishes Class E airspace extending upward from 700 feet above the surface within a 7.5-mile radius of Moriarty
Class E airspace designations are published in Paragraph 6005 of FAA Order 7400.9Z, dated August 6, 2015, and effective September 15, 2015, which is incorporated by reference in 14 CFR 71.1. The Class E airspace designations listed in this document will be published subsequently in the Order.
The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current, is non-controversial and unlikely to result in adverse or negative comments. It, therefore: (1) Is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a Regulatory Evaluation as the anticipated impact is so minimal. Since this is a routine matter that only affects air traffic procedures and air navigation, it is certified that this rule, when promulgated, does not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.
The FAA has determined that this action qualifies for categorical exclusion under the National Environmental Policy Act in accordance with FAA Order 1050.1F, “Environmental Impacts: Policies and Procedures,” paragraph 5-6.5. This airspace action is not expected to cause any potentially significant environmental impacts, and no extraordinary circumstances exists that warrant preparation of an environmental assessment.
Airspace, Incorporation by reference, Navigation (air).
In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:
49 U.S.C. 106(f), 106(g); 40103, 40113, 40120, E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.
That airspace extending upward from 700 feet above the surface within a 7.5-mile radius of Moriarty Airport.
Federal Aviation Administration (FAA), DOT.
Final rule.
This action establishes Class E airspace extending upward from 700 feet above the surface at Danville Municipal Airport, Danville, AR, to accommodate new Standard Instrument Approach Procedures (SIAPs) for the safety and management of Instrument flight Rules (IFR) operations at the airport.
Effective 0901 UTC, May 26, 2016. The Director of the Federal Register approves this incorporation by reference action under Title 1, Code of Federal Regulations, part 51, subject to the annual revision of FAA Order 7400.9 and publication of conforming amendments.
FAA Order 7400.9Z, Airspace Designations and Reporting Points, and subsequent amendments can be viewed on line at
FAA Order 7400.9, Airspace Designations and Reporting Points is published yearly and effective on September 15.
Rebecca Shelby, Central Service Center, Operations Support Group, Federal Aviation Administration, Southwest Region, 10101 Hillwood Parkway, Fort Worth, TX 76177; telephone: 817-222-5857.
The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part, A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of airspace necessary to ensure the safety of aircraft and the efficient use of airspace. This regulation is within the scope of that authority as it establishes Class E airspace at Danville Municipal Airport, Danville AR
On December 24, 2015, the FAA published in the
Class E airspace designations are published in paragraph 6005 of FAA Order 7400.9Z, dated August 6, 2015, and effective September 15, 2015, which is incorporated by reference in 14 CFR 71.1. The Class E airspace designations listed in this document will be published subsequently in the Order.
This document amends FAA Order 7400.9Z, Airspace Designations and Reporting Points, dated August 6, 2015, and effective September 15, 2015. FAA Order 7400.9Z is publicly available as listed in the
This action amends Title 14, Code of Federal Regulations (14 CFR), Part 71 by establishing Class E airspace extending upward from 700 feet above the surface within an 11.0-mile radius of Danville Municipal Airport, Danville, AR, to accommodate new Standard Instrument Approach Procedures for IFR operations at the airport.
The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current, is non-controversial and unlikely to result in adverse or negative comments. It, therefore: (1) Is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that only affects air traffic procedures and air navigation, it is certified that this rule, when promulgated, does not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.
The FAA has determined that this action qualifies for categorical exclusion under the National Environmental Policy Act in accordance with FAA Order 1050.1F, “Environmental Impacts: Policies and Procedures” paragraph 5-6.5a. This airspace action is not expected to cause any potentially significant environmental impacts, and no extraordinary circumstances exists that warrant preparation of an environmental assessment.
Airspace, Incorporation by reference, Navigation (air).
In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:
49 U.S.C. 106(f), 106(g),; 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.
That airspace extending upward from 700 feet above the surface within an 11.0-mile radius of Danville Municipal Airport.
Federal Aviation Administration (FAA), DOT.
Final rule.
This rule amends, suspends, or removes Standard Instrument Approach Procedures (SIAPs) and associated Takeoff Minimums and Obstacle Departure Procedures for operations at certain airports. These regulatory actions are needed because of the adoption of new or revised criteria, or because of changes occurring in the National Airspace System, such as the commissioning of new navigational facilities, adding new obstacles, or changing air traffic requirements. These changes are designed to provide for the safe and efficient use of the navigable airspace and to promote safe flight operations under instrument flight rules at the affected airports.
This rule is effective April 22, 2016. The compliance date for each SIAP, associated Takeoff Minimums, and ODP is specified in the amendatory provisions.
The incorporation by reference of certain publications listed in the regulations is approved by the Director of the Federal Register as of April 22, 2016.
Availability of matter incorporated by reference in the amendment is as follows:
1. U.S. Department of Transportation, Docket Ops-M30, 1200 New Jersey Avenue SE., West Bldg., Ground Floor, Washington, DC 20590-0001;
2. The FAA Air Traffic Organization Service Area in which the affected airport is located;
3. The office of Aeronautical Navigation Products, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 or,
4. The National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to:
All SIAPs and Takeoff Minimums and ODPs are available online free of charge. Visit the National Flight Data Center online at
Thomas J. Nichols, Flight Procedure Standards Branch (AFS-420) Flight Technologies and Procedures Division, Flight Standards Service, Federal Aviation Administration, Mike Monroney Aeronautical Center, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 (Mail Address: P.O. Box 25082 Oklahoma City, OK 73125) telephone: (405) 954-4164.
This rule amends Title 14, Code of Federal Regulations, Part 97 (14 CFR part 97) by amending the referenced SIAPs. The complete regulatory description of each SIAP is listed on the appropriate FAA
This amendment provides the affected CFR sections, and specifies the SIAPs and Takeoff Minimums and ODPs with their applicable effective dates. This amendment also identifies the airport and its location, the procedure and the amendment number.
The material incorporated by reference is publicly available as listed in the
The material incorporated by reference describes SIAPs, Takeoff Minimums and ODPs as identified in the amendatory language for part 97 of this final rule.
This amendment to 14 CFR part 97 is effective upon publication of each separate SIAP and Takeoff Minimums and ODP as amended in the transmittal. For safety and timeliness of change considerations, this amendment incorporates only specific changes contained for each SIAP and Takeoff Minimums and ODP as modified by FDC permanent NOTAMs.
The SIAPs and Takeoff Minimums and ODPs, as modified by FDC permanent NOTAM, and contained in this amendment are based on the criteria contained in the U.S. Standard for Terminal Instrument Procedures (TERPS). In developing these changes to SIAPs and Takeoff Minimums and ODPs, the TERPS criteria were applied only to specific conditions existing at the affected airports. All SIAP amendments in this rule have been previously issued by the FAA in a FDC NOTAM as an emergency action of immediate flight safety relating directly to published aeronautical charts.
The circumstances that created the need for these SIAP and Takeoff Minimums and ODP amendments require making them effective in less than 30 days.
Because of the close and immediate relationship between these SIAPs, Takeoff Minimums and ODPs, and safety in air commerce, I find that notice and public procedure under 5 U.S.C. 553(b) are impracticable and contrary to the public interest and, where applicable, under 5 U.S.C. 553(d), good cause exists for making these SIAPs effective in less than 30 days.
The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore—(1) is not a “significant regulatory action” under Executive Order 12866;(2) is not a “significant rule” under DOT regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. For the same reason, the FAA certifies that this amendment will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.
Air traffic control, Airports, Incorporation by reference, Navigation (air).
Accordingly, pursuant to the authority delegated to me, Title 14, Code of Federal regulations, Part 97, (14 CFR part 97), is amended by amending Standard Instrument Approach Procedures and Takeoff Minimums and ODPs, effective at 0901 UTC on the dates specified, as follows:
49 U.S.C. 106(f), 106(g), 40103, 40106, 40113, 40114, 40120, 44502, 44514, 44701, 44719, 44721-44722.
By amending: § 97.23 VOR, VOR/DME, VOR or TACAN, and VOR/DME or TACAN; § 97.25 LOC, LOC/DME, LDA, LDA/DME, SDF, SDF/DME; § 97.27 NDB, NDB/DME; § 97.29 ILS, ILS/DME, MLS, MLS/DME, MLS/RNAV; § 97.31 RADAR SIAPs; § 97.33 RNAV SIAPs; and § 97.35 COPTER SIAPs, Identified as follows:
* * *
Federal Aviation Administration (FAA), DOT.
Final rule.
This rule amends, suspends, or removes Standard Instrument Approach Procedures (SIAPs) and associated Takeoff Minimums and Obstacle Departure Procedures for operations at certain airports. These regulatory actions are needed because of the adoption of new or revised criteria, or because of changes occurring in the National Airspace System, such as the commissioning of new navigational facilities, adding new obstacles, or changing air traffic requirements. These changes are designed to provide for the safe and efficient use of the navigable airspace and to promote safe flight operations under instrument flight rules at the affected airports.
This rule is effective April 22, 2016. The compliance date for each SIAP, associated Takeoff Minimums, and ODP is specified in the amendatory provisions.
The incorporation by reference of certain publications listed in the regulations is approved by the Director of the Federal Register as of April 22, 2016.
Availability of matter incorporated by reference in the amendment is as follows:
1. U.S. Department of Transportation, Docket Ops-M30, 1200 New Jersey Avenue SE., West Bldg., Ground Floor, Washington, DC 20590-0001;
2. The FAA Air Traffic Organization Service Area in which the affected airport is located;
3. The office of Aeronautical Navigation Products, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 or,
4. The National Archives and Records Administration (NARA).
For information on the availability of this material at NARA, call 202-741-6030, or go to:
All SIAPs and Takeoff Minimums and ODPs are available online free of charge. Visit the National Flight Data Center online at
Thomas J. Nichols, Flight Procedure Standards Branch (AFS-420) Flight
This rule amends Title 14, Code of Federal Regulations, Part 97 (14 CFR part 97) by amending the referenced SIAPs. The complete regulatory description of each SIAP is listed on the appropriate FAA Form 8260, as modified by the National Flight Data Center (NFDC)/Permanent Notice to Airmen (P-NOTAM), and is incorporated by reference under 5 U.S.C. 552(a), 1 CFR part 51, and 14 CFR 97.20. The large number of SIAPs, their complex nature, and the need for a special format make their verbatim publication in the
This amendment provides the affected CFR sections, and specifies the SIAPs and Takeoff Minimums and ODPs with their applicable effective dates. This amendment also identifies the airport and its location, the procedure and the amendment number.
The material incorporated by reference is publicly available as listed in the
The material incorporated by reference describes SIAPs, Takeoff Minimums and ODPs as identified in the amendatory language for part 97 of this final rule.
This amendment to 14 CFR part 97 is effective upon publication of each separate SIAP and Takeoff Minimums and ODP as amended in the transmittal. For safety and timeliness of change considerations, this amendment incorporates only specific changes contained for each SIAP and Takeoff Minimums and ODP as modified by FDC permanent NOTAMs.
The SIAPs and Takeoff Minimums and ODPs, as modified by FDC permanent NOTAM, and contained in this amendment are based on the criteria contained in the U.S. Standard for Terminal Instrument Procedures (TERPS). In developing these changes to SIAPs and Takeoff Minimums and ODPs, the TERPS criteria were applied only to specific conditions existing at the affected airports. All SIAP amendments in this rule have been previously issued by the FAA in a FDC NOTAM as an emergency action of immediate flight safety relating directly to published aeronautical charts.
The circumstances that created the need for these SIAP and Takeoff Minimums and ODP amendments require making them effective in less than 30 days.
Because of the close and immediate relationship between these SIAPs, Takeoff Minimums and ODPs, and safety in air commerce, I find that notice and public procedure under 5 U.S.C. 553(b) are impracticable and contrary to the public interest and, where applicable, under 5 U.S.C. 553(d), good cause exists for making these SIAPs effective in less than 30 days.
The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore— (1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. For the same reason, the FAA certifies that this amendment will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.
Air traffic control, Airports, Incorporation by reference, Navigation (air).
Accordingly, pursuant to the authority delegated to me, Title 14, Code of Federal regulations, Part 97, (14 CFR part 97), is amended by amending Standard Instrument Approach Procedures and Takeoff Minimums and ODPs, effective at 0901 UTC on the dates specified, as follows:
49 U.S.C. 106(f), 106(g), 40103, 40106, 40113, 40114, 40120, 44502, 44514, 44701, 44719, 44721-44722.
By amending: § 97.23 VOR, VOR/DME, VOR or TACAN, and VOR/DME or TACAN; § 97.25 LOC, LOC/DME, LDA, LDA/DME, SDF, SDF/DME; § 97.27 NDB, NDB/DME; § 97.29 ILS, ILS/DME, MLS, MLS/DME, MLS/RNAV; § 97.31 RADAR SIAPs; § 97.33 RNAV SIAPs; and § 97.35 COPTER SIAPs, Identified as follows:
Federal Aviation Administration (FAA), DOT.
Final rule.
This rule establishes, amends, suspends, or removes Standard Instrument Approach Procedures (SIAPs) and associated Takeoff Minimums and Obstacle Departure Procedures (ODPs) for operations at certain airports. These regulatory actions are needed because of the adoption of new or revised criteria, or because of changes occurring in the National Airspace System, such as the commissioning of new navigational facilities, adding new obstacles, or changing air traffic requirements. These changes are designed to provide safe and efficient use of the navigable airspace and to promote safe flight operations under instrument flight rules at the affected airports.
This rule is effective April 22, 2016. The compliance date for each SIAP, associated Takeoff Minimums, and ODP is specified in the amendatory provisions.
The incorporation by reference of certain publications listed in the regulations is approved by the Director of the Federal Register as of April 22, 2016.
Availability of matters incorporated by reference in the amendment is as follows:
1. U.S. Department of Transportation, Docket Ops-M30, 1200 New Jersey Avenue SE., West Bldg., Ground Floor, Washington, DC 20590-0001.
2. The FAA Air Traffic Organization Service Area in which the affected airport is located;
3. The office of Aeronautical Navigation Products, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 or,
4. The National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to:
All SIAPs and Takeoff Minimums and ODPs are available online free of charge. Visit the National Flight Data Center at
Thomas J. Nichols, Flight Procedure Standards Branch (AFS-420), Flight Technologies and Programs Divisions, Flight Standards Service, Federal Aviation Administration, Mike Monroney Aeronautical Center, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 (Mail Address: P.O. Box 25082, Oklahoma City, OK 73125) Telephone: (405) 954-4164.
This rule amends Title 14 of the Code of Federal Regulations, Part 97 (14 CFR part 97), by establishing, amending, suspending, or removes SIAPS, Takeoff Minimums and/or ODPS. The complete regulatory description of each SIAP and its associated Takeoff Minimums or ODP for an identified airport is listed on FAA form documents which are incorporated by reference in this amendment under 5 U.S.C. 552(a), 1 CFR part 51, and 14 CFR part § 97.20. The applicable FAA forms are FAA Forms 8260-3, 8260-4, 8260-5, 8260-15A, and 8260-15B when required by an entry on 8260-15A.
The large number of SIAPs, Takeoff Minimums and ODPs, their complex nature, and the need for a special format make publication in the
The material incorporated by reference is publicly available as listed in the
The material incorporated by reference describes SIAPS, Takeoff Minimums and/or ODPS as identified in the amendatory language for part 97 of this final rule.
This amendment to 14 CFR part 97 is effective upon publication of each separate SIAP, Takeoff Minimums and ODP as Amended in the transmittal. Some SIAP and Takeoff Minimums and textual ODP amendments may have been issued previously by the FAA in a Flight Data Center (FDC) Notice to Airmen (NOTAM) as an emergency action of immediate flight safety relating directly to published aeronautical charts.
The circumstances that created the need for some SIAP and Takeoff Minimums and ODP amendments may require making them effective in less than 30 days. For the remaining SIAPs and Takeoff Minimums and ODPs, an effective date at least 30 days after publication is provided.
Further, the SIAPs and Takeoff Minimums and ODPs contained in this amendment are based on the criteria contained in the U.S. Standard for Terminal Instrument Procedures (TERPS). In developing these SIAPs and Takeoff Minimums and ODPs, the TERPS criteria were applied to the conditions existing or anticipated at the affected airports. Because of the close and immediate relationship between these SIAPs, Takeoff Minimums and ODPs, and safety in air commerce, I find that notice and public procedure under 5 U.S.C. 553(b) are impracticable and contrary to the public interest and, where applicable, under 5 U.S.C. 553(d), good cause exists for making some SIAPs effective in less than 30 days.
The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore—(1) is not a “significant regulatory action” under Executive Order 12866;(2) is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034; February 26,1979) ; and (3)does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. For the same reason, the FAA certifies that this amendment will not have a significant economic impact on a substantial
Air traffic control, Airports, Incorporation by reference, Navigation (air).
Accordingly, pursuant to the authority delegated to me, Title 14, Code of Federal Regulations, Part 97 (14 CFR part 97) is amended by establishing, amending, suspending, or removing Standard Instrument Approach Procedures and/or Takeoff Minimums and Obstacle Departure Procedures effective at 0901 UTC on the dates specified, as follows:
49 U.S.C. 106(f), 106(g), 40103, 40106, 40113, 40114, 40120, 44502, 44514, 44701, 44719, 44721-44722.
Federal Aviation Administration (FAA), DOT.
Final rule.
This rule establishes, amends, suspends, or removes Standard Instrument Approach Procedures (SIAPs) and associated Takeoff Minimums and Obstacle Departure Procedures (ODPs) for operations at certain airports. These regulatory actions are needed because of the adoption of new or revised criteria, or because of changes occurring in the National Airspace System, such as the commissioning of new navigational facilities, adding new obstacles, or changing air traffic requirements. These changes are designed to provide safe and efficient use of the navigable airspace and to promote safe flight operations under instrument flight rules at the affected airports.
This rule is effective April 22, 2016. The compliance date for each SIAP, associated Takeoff Minimums, and ODP is specified in the amendatory provisions.
The incorporation by reference of certain publications listed in the regulations is approved by the Director of the Federal Register as of April 22, 2016.
Availability of matters incorporated by reference in the amendment is as follows:
1. U.S. Department of Transportation, Docket Ops-M30, 1200 New Jersey Avenue SE., West Bldg., Ground Floor, Washington, DC 20590-0001.
2. The FAA Air Traffic Organization Service Area in which the affected airport is located;
3. The office of Aeronautical Navigation Products, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 or,
4. The National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to:
All SIAPs and Takeoff Minimums and ODPs are available online free of charge. Visit the National Flight Data Center at
Thomas J. Nichols, Flight Procedure Standards Branch (AFS-420), Flight Technologies and Programs Divisions, Flight Standards Service, Federal Aviation Administration, Mike Monroney Aeronautical Center, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 (Mail Address: P.O. Box 25082, Oklahoma City, OK 73125) Telephone: (405) 954-4164.
This rule amends Title 14 of the Code of Federal Regulations, Part 97 (14 CFR part 97), by establishing, amending, suspending, or removes SIAPS, Takeoff Minimums and/or ODPS. The complete regulatory description of each SIAP and its associated Takeoff Minimums or ODP for an identified airport is listed on FAA form documents which are incorporated by reference in this amendment under 5 U.S.C. 552(a), 1 CFR part 51, and 14 CFR part 97.20. The applicable FAA forms are FAA Forms 8260-3, 8260-4, 8260-5, 8260-15A, and 8260-15B when required by an entry on 8260-15A.
The large number of SIAPs, Takeoff Minimums and ODPs, their complex nature, and the need for a special format make publication in the
The material incorporated by reference is publicly available as listed in the
The material incorporated by reference describes SIAPS, Takeoff Minimums and/or ODPS as identified in the amendatory language for part 97 of this final rule.
This amendment to 14 CFR part 97 is effective upon publication of each separate SIAP, Takeoff Minimums and ODP as Amended in the transmittal. Some SIAP and Takeoff Minimums and textual ODP amendments may have been issued previously by the FAA in a Flight Data Center (FDC) Notice to Airmen (NOTAM) as an emergency action of immediate flight safety relating directly to published aeronautical charts.
The circumstances that created the need for some SIAP and Takeoff Minimums and ODP amendments may require making them effective in less than 30 days. For the remaining SIAPs and Takeoff Minimums and ODPs, an effective date at least 30 days after publication is provided.
Further, the SIAPs and Takeoff Minimums and ODPs contained in this amendment are based on the criteria contained in the U.S. Standard for Terminal Instrument Procedures (TERPS). In developing these SIAPs and Takeoff Minimums and ODPs, the TERPS criteria were applied to the conditions existing or anticipated at the affected airports. Because of the close and immediate relationship between these SIAPs, Takeoff Minimums and ODPs, and safety in air commerce, I find that notice and public procedure under 5 U.S.C. 553(b) are impracticable and contrary to the public interest and, where applicable, under 5 U.S.C. 553(d), good cause exists for making some SIAPs effective in less than 30 days.
The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore—(1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034; February 26,1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. For the same reason, the FAA certifies that this amendment will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.
Air traffic control, Airports, Incorporation by reference, Navigation (air).
Accordingly, pursuant to the authority delegated to me, Title 14, Code of Federal Regulations, Part 97 (14 CFR part 97) is amended by establishing, amending, suspending, or removing Standard Instrument Approach Procedures and/or Takeoff Minimums and Obstacle Departure Procedures effective at 0901 UTC on the dates specified, as follows:
49 U.S.C. 106(f), 106(g), 40103, 40106, 40113, 40114, 40120, 44502, 44514, 44701, 44719, 44721-44722.
Office of the Director of National Intelligence.
Direct final rule; withdrawal.
The Office of the Director of National Intelligence (ODNI) is withdrawing a direct final rule that would have provided procedures for members of the public to request from ODNI a Mandatory Declassification Review (MDR) of information classified under the provisions of Executive Order 13526 or predecessor orders such that the agency may retrieve it with reasonable effort.
As of April 22, 2016, the direct final rule published on February 26, 2016, at 81 FR 9768, is withdrawn.
Jennifer L. Hudson, 703-874-8085.
On February 26, 2016, the ODNI published a direct final rule providing procedures for members of the public to request from ODNI an MDR of information classified under the provisions of Executive Order 13526 or predecessor orders such that the agency may retrieve it with reasonable effort. The purpose of this rule was to assist in implementing specific sections of Executive Order 13526 concerning the MDR. In response to this direct final rule, ODNI received comments regarding the fee provisions stated in Section 1704.8 and the recommendation that those provisions be withdrawn and replaced with fee provisions comparable to those in ODNI's Freedom of Information Act program (32 CFR 1700.6). ODNI agrees and therefore is withdrawing its direct final rule. It will simultaneously issue a new direct final rule and a proposed rule reflecting that recommendation.
Coast Guard, DHS.
Notice of enforcement of regulation.
The Coast Guard will enforce the special local regulation on the South Branch of the Chicago River for the Chinatown Chamber of Commerce Dragon Boat Race in Chicago, Illinois. This regulated area will be enforced from 8 a.m. until 5 p.m. on June 25, 2016. This action is necessary and intended to ensure safety of life and property on navigable waters prior to, during, and immediately after the Dragon Boat race. During the enforcement period, no vessel may enter, transit through, or anchor within the regulated area without the approval from the Captain of the Port or a designated representative.
The regulation in 33 CFR 100.909 will be enforced from 8 a.m. until 5 p.m. on June 25, 2016.
If you have questions about this notice of enforcement, call or email LT Lindsay Cook, Waterways Management Division, Marine Safety Unit Chicago, at 630-986-2155, email address
The Coast Guard will enforce a special local regulation in 33 CFR 100.909 from 8 a.m. until 5 p.m. on June 25, 2016, for the Chinatown Chamber of Commerce Dragon Boat Race. This action is being taken to provide for the safety of life on a navigable waterway during the regatta. Our regulation for the Recurring Marine Events in Captain of the Port Lake Michigan Zone, § 100.909, specifies the location of the regulated area as all waters of the South Branch of the Chicago River from the West 18th St. Bridge at position 41°51′28″ N., 087°38′06″ W. to the Amtrak Bridge at position 41°51′20″ N., 087°38′13″ W. (NAD 83). During the enforcement period, no vessel may transit this regulated area without approval from the Captain of the Port Lake Michigan or a designated representative.
Vessels that obtain prior approval to transit the regulated area are required to operate at a no wake speed to reduce wake to a minimum, and in a manner which will not endanger participants in the event or any other craft. These rules shall not apply to participants in the event or vessels of the patrol operating in the performance of their assigned duties. The Captain of the Port or a designated representative may direct the anchoring, mooring, or movement of any boat or vessel within the regulated area.
This notice of enforcement is issued under authority of 33 CFR 100.909, Chinatown Chamber of Commerce Dragon Boat Race; Chicago, IL and 5 U.S.C. 552(a). In addition to this notice in the
Coast Guard, DHS.
Interim final rule; request for comments.
The Coast Guard is amending the regulations established for recurring marine events and fireworks displays that take place within the Fifth Coast Guard District area of responsibility. This interim rule revises the listing of events that informs the public of regularly scheduled marine parades, regattas, other organized water events, and fireworks displays that require additional safety measures provided by regulations. Through this rule, the list of recurring marine events requiring special local regulations or safety zones is updated with revisions, additional events, and removal of events that no longer take place in the Fifth Coast Guard District. When these regulations are enforced, certain restrictions are placed on marine traffic in specified areas. This rulemaking project promotes efficiency by eliminating the need to produce a separate rule for each individual recurring event, and serves to provide notice of the known recurring events requiring a special local regulation or safety zone throughout the year. We invite your comments on this rulemaking.
This rule is effective without actual notice from April 22, 2016. For the purposes of enforcement, actual notice will be used from the date the rule was signed, April 5, 2016, until April 22, 2016. Comments and related material must be received by the Coast Guard on or before July 21, 2016.
You may submit comments identified by docket number USCG-2015-0854 using the Federal eRulemaking Portal at
If you have questions about this rulemaking, call or email Dennis Sens, Fifth Coast Guard District, Prevention Division, (757) 398-6204,
The special local regulations listed in 33 CFR 100.501 and safety zones in 33 CFR 165.506 were last amended on April 16, 2015, (80 FR 20418). The Coast Guard is issuing this interim final rule without prior notice and opportunity to comment pursuant to authority under section 4(a) of the Administrative Procedure Act (APA) (5 U.S.C. 553(b)). This provision authorizes an agency to issue a rule without prior notice and opportunity to comment when the agency for good cause finds that those procedures are “impracticable, unnecessary, or contrary to the public interest.”
Under 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule because immediate action is necessary to protect the maritime public during certain marine events. The potential dangers posed by certain marine events and fireworks displays conducted on waterways in close proximity to other vessel traffic makes special local regulations and safety zones necessary to provide for the safety of participants, spectator craft, and other vessels transiting the event area. Accordingly, waiting for a comment period to run would be contrary to the public interest of protecting life and property. In addition, publishing an NPRM is impracticable because the necessary information regarding these annual recurring marine events and fireworks displays was not available in sufficient time to ensure accurate and up to date listings to allow for a comment period prior to the events.
For the same reasons, under 5 U.S.C. 553(d)(3), the Coast Guard finds that good cause exists for making this rule effective less than 30 days after publication in the
This interim rule is effective upon publication without prior notice through publication in the
This rule is prepared to provide the most up to date list of recurring marine events, special local regulations and safety zones, provides ample notice for all listed events occurring after May 2016. Additionally, these recurring events are noticed to the public through local media and planned on by the local communities in which they take place.
The current lists of annual and recurring special local regulations and safety zones for marine events and fireworks displays within the Fifth Coast Guard District area of responsibility (AOR) are published under 33 CFR part 100.501 and part 165.506, respectively. These lists were last updated April 16, 2015 through a previous rulemaking (80 FR 20418), and generated no adverse comments. Like this interim rule, the April 2015 rule added to, removed from, and amended 33 CFR 100.501 and 33 CFR 165.506 to create a comprehensive list of recurring marine events and fireworks displays requiring special local regulations and safety zones.
The Coast Guard regularly updates special local regulations and safety zones established for recurring marine events and fireworks displays that take place either on or over the navigable waters of the United States. Under that rule, the list of recurring marine events requiring special local regulations or safety zones is updated with revisions, additional events, and removal of events that no longer take place within the Fifth Coast Guard District. The Fifth Coast Guard District area of responsibility is defined in 33 CFR 3.25.
The purpose of this rulemaking is to ensure the safety of persons, vessels and the navigable waters within close proximity to marine events and or fireworks displays before, during, and after the scheduled event. Publishing these regulatory updates in a single rulemaking promotes administrative efficiency and reduces costs involved in producing a separate rule for each individual recurring event. This action also provides the public with notice through publication in the
This rule adds 4 new special local regulations for marine events, removes 7 regulations and revises 18 previously established regulations for marine events listed in the Table to § 100.501. Other than changes to the dates and locations of certain events, the other provisions in 33 CFR 100.501 remain unchanged.
This rule provides additional information about regulated areas and the restrictions that apply to mariners and new terms including “Race Area”, “Spectator Area” and “Buffer Zone”. The 24 hour contact phone numbers are updated for Coast Guard Sectors Delaware Bay and North Carolina.
The Coast Guard revises regulations at 33 CFR 100.501 by adding 4 new special local regulations. The special local regulations are listed in Table 1, including reference by section as printed in the Table to § 100.501.
The Coast Guard amends regulations at 33 CFR 100.501 by disestablishing the following 7 special local regulated areas listed in Table 2.
This rule revises 18 preexisting special local regulations that involves change to marine event date(s) and/or coordinates. These events are listed in Table 3, with reference by section as printed in the Table to § 100.501.
Based on the nature of marine events, large number of participants and spectators, and event locations, the Coast Guard has determined that the events listed in this rule could pose a risk to participants or waterway users if normal vessel traffic were to interfere with the event. Possible hazards include risks of injury or death resulting from near or actual contact among participant vessels and spectator vessels or mariners traversing through the regulated area. In order to protect the safety of all waterway users including event participants and spectators, this rule establishes special local regulations for the time and location of each marine event.
This rule provides designated spectator areas for commercial small passenger vessels at certain marine event(s). The purpose of a commercial small passenger vessel spectator area is to ensure the safe operation of commercial vessels that carry a greater number of passengers onboard and operating within the widespread, high capacity spectator fleet at marine events. These spectator areas facilitate direct and unobstructed accesses for first responders should an emergency occur aboard one of the higher capacity commercial passenger vessels. Commercial passenger vessels holding a valid Certificate of Inspection issued under 46 CFR 114.110, and 175.110, (subchapter K or T vessels) are eligible for access to the designated spectator area as directed by the marine event Patrol Commander.
Owners or operators of vessels that meet the requirements of subchapter K or T vessels may request access to the Severn River spectator area for the U.S. Naval Academy Blue Angels Air Show by contacting the City of Annapolis Harbormaster Office, at telephone (410) 263-7973 or email at
Owners or operators of vessels that meet the requirements of subchapter K or T vessels may request access to the Patapsco River spectator area for the Baltimore Air Show by contacting Sail Baltimore at telephone (410) 522-7300 or email at
This rule prevents vessels from entering, transiting, mooring or anchoring within areas specifically designated as regulated areas during the periods of enforcement unless authorized by the Captain of the Port (COTP), or designated Coast Guard Patrol Commander. The designated “Patrol Commander” includes Coast Guard commissioned, warrant, or petty officer who has been designated by the COTP to act on their behalf. On-scene patrol commander may be augmented by local, State or Federal officials authorized to act in support of the Coast Guard.
This rule adds 4 new safety zones, and revises 22 previously established safety zones listed in the Table to § 165.506. Other than changes to the dates and locations of certain safety zones, the other provisions in 33 CFR 165.506 remain unchanged.
The Coast Guard revises the regulations at 33 CFR 165.506 by adding 4 new safety zone locations to the permanent regulations listed in this section. The new safety zones are listed in Table 4, including reference by section as printed in the Table to § 165.506.
The rule revises 22 preexisting safety zones that involves change to event date(s) and coordinates. These revised safety zones are shown in Table 5, with reference by section as printed in the Table to § 165.506.
Each year, organizations in the Fifth Coast Guard District sponsor fireworks displays in the same general location and time period. Each event uses a barge or an on-shore site near the shoreline as the fireworks launch platform. A safety zone is used to control vessel movement within a specified distance surrounding the launch platforms to ensure the safety of persons and property. Coast Guard personnel on scene may allow boaters within the safety zone if conditions permit.
The enforcement period for these safety zones is from 5:30 p.m. to 1 a.m. local time. However, vessels may enter, remain in, or transit through these safety zones during this time frame if authorized by the COTP or designated Coast Guard patrol commander on scene, as provided for in 33 CFR 165.23. This rule provides for the safety of life on navigable waters during the events. The regulatory text we are proposing appears at the end of this document.
We developed this rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on a number of these statutes and executive orders, and we discuss First Amendment rights of protestors.
Executive Orders 12866 and 13563 direct agencies to assess the costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits. Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This rule has not been designated a “significant regulatory action,” under Executive Order 12866. Accordingly, the rule has not been reviewed by the Office of Management and Budget.
This regulatory action determination is based on the short amount of time that vessels will be restricted from regulated areas, and the small size of these areas that are usually positioned away from high vessel traffic zones. Generally vessels would not be precluded from getting underway, or mooring at any piers or marinas currently located in the vicinity of the regulated areas. Advance notifications would also be made to the local maritime community by issuance of Local Notice to Mariners, Broadcast Notice to Mariners, Marine information and facsimile broadcasts so mariners can adjust their plans accordingly. Notifications to the public for most events will typically be made by local newspapers, radio and TV stations. The Coast Guard anticipates that these special local regulated areas and safety zones will only be enforced one to three times per year.
The Regulatory Flexibility Act of 1980, 5 U.S.C. 601-612, as amended,
While some owners or operators of vessels intending to transit the regulated areas or safety zones may be small entities, for the reasons stated in section IV.A above this rule would not have a significant economic impact on any vessel owner or operator. However this rule will affect the following entities some of which may be small entities: The owners and operators of vessels intending to transit or anchor in these regulated areas during the times the zones are enforced.
These special local regulated areas and safety zones will not have a significant economic impact on a substantial number of small entities for the following reasons: The Coast Guard will ensure that small entities are able to operate in the areas where events are occurring to the extent possible while ensuring the safety of event participants and spectators. The enforcement period will be short in duration and, in many of the areas, vessels can transit safely around the regulated area. Generally, blanket permission to enter, remain in, or transit through these regulated areas will be given, except during the period that the Coast Guard patrol vessel is present. Before the enforcement period, we will issue maritime advisories widely.
If you think that your business, organization, or governmental jurisdiction qualifies as a small entity and that this rule would have a significant economic impact on it, please submit a comment (see
Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we want to assist small entities in understanding this rule. If the rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact the person listed in the
This rule would not call for a new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).
A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. We have analyzed this rule under that Order and have determined that it is consistent with the fundamental federalism principles and preemption requirements described in Executive Order 13132.
Also, this rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it would not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes. If you believe this rule has implications for federalism or Indian tribes, please contact the person listed in the
The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. Though this rule would not result in such an expenditure, we do discuss the effects of this rule elsewhere in this preamble.
We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (42 U.S.C. 4321-4370f), and have made a preliminary determination that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment.
This rule involves implementation of regulations within 33 CFR part 100 that apply to organized marine events on the navigable waters of the United States. Some marine events by their nature may introduce potential for adverse impact on the safety or other interest of waterway users or waterfront infrastructure within or close proximity to the event area. The category of water activities includes but is not limited to sail boat regattas, boat parades, power boat racing, swimming events, crew racing, and sail board racing. This section of the rule is categorically excluded from further review under paragraph 34(h) of Figure 2-1 of the Commandant Instruction. An environmental analysis checklist supporting this determination and a Categorical Exclusion Determination are not required for this section of the rule.
This rule involves implementation of regulations at 33 CFR part 165 that establish safety zones on navigable waters of the United States for fireworks events. These safety zones are enforced for the duration of fireworks display events. The fireworks are generally launched from or immediately adjacent to navigable waters of the United States. The category of activities includes fireworks launched from barges or at the shoreline that generally rely on the use of navigable waters as a safety buffer. Fireworks displays may introduce potential hazards such as accidental discharge of fireworks, dangerous projectiles, and falling hot embers or other debris. This section of the rule is categorically excluded from further review under paragraph 34(g) of Figure 2-1 of the Commandant Instruction. A preliminary environmental analysis checklist supporting this determination and a Categorical Exclusion Determination are available in the docket where indicated under
The Coast Guard respects the First Amendment rights of protesters. Protesters are asked to contact the person listed in the
We view public participation as essential to effective rulemaking, and will consider all comments and material received during the comment period. Your comment can help shape the outcome of this rulemaking. If you submit a comment, please include the docket number for this rulemaking, indicate the specific section of this document to which each comment applies, and provide a reason for each suggestion or recommendation.
We encourage you to submit comments through the Federal eRulemaking Portal at
We accept anonymous comments. All comments received will be posted without change to
Documents mentioned in this rule as being available in the docket, and all public comments, will be in our online docket at
Marine safety, Navigation (water), Reporting and recordkeeping requirements, Waterways.
Harbors, Marine safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, Waterways.
For the reasons discussed in the preamble, the Coast Guard amends 33 CFR parts 100 and 165 as follows:
33 U.S.C. 1233.
The following regulations apply to the marine events listed in the Table to § 100.501. These regulations will be effective annually, for the duration of each event listed in the Table to § 100.501. Annual notice of the exact dates and times of the effective period of the regulation with respect to each event, the geographical area, and details concerning the nature of the event and the number of participants and type(s) of vessels involved will be published in Local Notices to Mariners and via Broadcast Notice to Mariners over VHF-FM marine band radio.
(a)
(1)
(2)
(3)
(4)
(b)
(c)
(2) The operator of any vessel in the regulated area shall:
(i) Stop the vessel immediately when directed to do so by any Official Patrol and then proceed only as directed.
(ii) All persons and vessels shall comply with the instructions of the Official Patrol.
(iii) When authorized to transit the regulated area, all vessels shall proceed at the minimum speed necessary to maintain a safe course that minimizes wake near the race course.
(3)
(4)
(5)
(6) Spectators are only allowed inside the regulated area if they remain within a designated spectator area. Spectators may contact the Coast Guard Patrol Commander to request permission to either enter the Spectator Area or pass through the regulated area. If permission is granted, spectators may enter the Spectator Area or must pass directly through the regulated area as instructed by PATCOM at safe speed and without loitering.
(d)
(1) Coast Guard Sector Delaware Bay—Captain of the Port Zone, Philadelphia, Pennsylvania: (215) 271-4940.
(2) Coast Guard Sector Baltimore—Captain of the Port Zone, Baltimore, Maryland: (410) 576-2525.
(3) Coast Guard Sector Hampton Roads—Captain of the Port Zone, Norfolk, Virginia: (757) 483-8567.
(4) Coast Guard Sector North Carolina—Captain of the Port Zone North Carolina: (877) 229-0770 or (910) 362-4015.
(e)
(f)
(g)
(2) Marine event (b.) 24, Baltimore Air Show. Patapsco River spectator area; except for a vessel in an emergency situation, a vessel may not anchor or hold station within the spectator area described in Table to 100.501 (b.) 24 without the permission of the Captain of the Port or designated Patrol Commander. The Captain of the Port has designated this spectator area for commercial small passenger vessel use. This area is closed except for commercial small passenger vessels holding a valid Certificate of Inspection regulated under 46 CFR chapter I, subchapters K and T (46 CFR 114.110, and 175.110). Vessels that meet the requirements of this section may request access to the Patapsco River spectator area by contacting the Sail Baltimore at (410) 522-7300 or email
33 U.S.C. 1231; 50 U.S.C. 191, 33 CFR 1.05-1, 6.04-1, 6.04-6, 160.5; Department of Homeland Security Delegation No. 0170.1.
(a)
(2) The following regulations apply to the fireworks safety zones listed in the Table to § 165.506. These regulations will be enforced annually, for the duration of each fireworks event listed in the Table to § 165.506. In the case of inclement weather, the event may be conducted on the day following the date listed in the Table to § 165.506. Annual notice of the exact dates and times of the enforcement period of the regulation with respect to each safety zone, the geographical area, and other details concerning the nature of the fireworks event will be published in Local Notices to Mariners and via Broadcast Notice to Mariners over VHF-FM marine band radio.
(3) All persons and vessels shall comply with the instructions of the Coast Guard Captain of the Port, Coast Guard Patrol Commander or the designated on-scene-patrol personnel. Those personnel are comprised of commissioned, warrant, and petty officers of the U.S. Coast Guard. Other Federal, State and local agencies may assist these personnel in the enforcement of the safety zone. Upon being hailed by a U.S. Coast Guard vessel by siren, radio, flashing light or other means, the operator of a vessel shall proceed as directed.
(b)
(2) Coast Guard Captains of the Port in the Fifth Coast Guard District will notify the public of the enforcement of these safety zones by all appropriate means to affect the widest publicity among the affected segments of the public. Publication in the Local Notice to Mariners, marine information broadcasts, and facsimile broadcasts may be made for these events, beginning 24 to 48 hours before the event is scheduled to begin, to notify the public.
(c)
(1) Coast Guard Sector Delaware Bay—Captain of the Port Zone, Philadelphia, Pennsylvania: (215) 271-4940.
(2) Coast Guard Sector Baltimore—Captain of the Port Zone, Baltimore, Maryland: (410) 576-2525.
(3) Coast Guard Sector Hampton Roads—Captain of the Port Zone, Norfolk, Virginia: (757) 483-8567.
(4) Coast Guard Sector North Carolina—Captain of the Port Zone, Wilmington, North Carolina: (877) 229-0770 or (910) 362-4015.
(d)
Coast Guard, DHS.
Notice of deviation from drawbridge regulation.
The Coast Guard has issued a temporary deviation from the operating schedule that governs the Lehigh Valley Drawbridge across the Newark Bay, mile 4.3, at Jersey City, New Jersey. This deviation is necessary to allow the bridge owner to replace rails and ties at the bridge. This deviation allows the bridge to remain closed for 26 hours for two days.
This deviation is effective from 7 a.m. on June 5, 2016 to 7 p.m. on June 13, 2016.
The docket for this deviation, [USCG-2016-0187] is available at
If you have questions on this temporary deviation, call or email Joe M. Arca, Project Officer, First Coast Guard District, telephone (212) 514-4336, email
The Lehigh Valley Drawbridge across Newark Bay, mile 4.3, at Jersey City, New Jersey, has a vertical clearance in the closed position of 35 feet at mean high water and 39 feet at mean low water. The existing bridge operating regulations are found at 33 CFR 117.5.
The waterway is transited by seasonal recreational vessels and commercial vessels of various sizes.
The bridge owner, Consolidated Rail Corporation (CONRAIL), requested a temporary deviation from the normal operating schedule to facilitate replacement of the rails and ties at the bridge.
Under this temporary deviation, the Lehigh Valley Drawbridge may remain in the closed position for 26 hours, from 7 a.m. to 9 p.m. on June 5, 2016 and from 7 a.m. to 7 p.m. on June 6, 2016, and a rain date from 7 a.m. to 9 p.m. on June 12, 2016 and from 7 a.m. to 7 p.m. on June 13, 2016.
Vessels able to pass under the bridge in the closed position may do so at any time. The bridge will not be able to open for emergencies and there is no immediate alternate route for vessels to pass.
The Coast Guard will inform the users of the waterways through our Local Notice and Broadcast to Mariners of the change in operating schedule for the bridge so that vessel operations can arrange their transits to minimize any impact caused by the temporary deviation.
In accordance with 33 CFR 117.35(e), the drawbridge must return to its regular operating schedule immediately at the end of the effective period of this temporary deviation. This deviation from the operating regulations is authorized under 33 CFR 117.35.
Coast Guard, DHS.
Notice of deviation from drawbridge regulation.
The Coast Guard has issued a temporary deviation from the operating schedule that governs the Arthur Kill (AK) Railroad Bridge across Arthur Kill, mile 11.6, between Staten Island, New York and Elizabeth, New Jersey. This deviation allows the bridge to remain in the closed position to facilitate bridge inspection.
This deviation is effective from 7:28 a.m. on July 16, 2016, to 5:41 p.m. July 24, 2016.
The docket for this deviation [USCG-2016-0309] is available at
If you have questions on this temporary deviation, call or email Mr. Joe Arca, Project Officer, First Coast Guard District, telephone (212) 514-4336, email
The AK Railroad Bridge, across Arthur Kill, mile 11.6, between Staten Island, New York and Elizabeth, New Jersey has a vertical clearance in the closed position of 31 feet at Mean High Water and 35 feet at Mean Low Water. The existing drawbridge operation regulations are listed at 33 CFR 117.702.
The waterway supports both commercial and recreational navigation of various vessel sizes. The operator of the bridge, Consolidated Rail Corporation (Conrail), requested a temporary deviation to facilitate scheduled bridge inspection of the movable span of the bridge. The bridge must remain in the closed position to perform this inspection.
Under this temporary deviation, the AK Railroad Bridge may remain in the closed position as follows:
Vessels able to pass through the bridge in the closed positions may do so at anytime. There are no alternate routes for vessel traffic. The bridge can be opened in an emergency. The Coast Guard will also inform the users of the waterway through our Local and Broadcast Notices to Mariners of the change in operating schedule for the bridge so that vessels can arrange their transits to minimize any impact caused by the temporary deviation.
In accordance with 33 CFR 117.35(e), the drawbridge must return to its regular operating schedule immediately at the end of the effective period of this temporary deviation. This deviation from the operating regulations is authorized under 33 CFR 117.35.
Coast Guard, DHS.
Temporary final rule.
The Coast Guard is establishing a temporary safety zone on the waters of the Intracoastal Waterway in Myrtle Beach, South Carolina on Sunday, April 24, 2016 for the Xterra Swim. The temporary safety zone is necessary for the safety of the swimmers, participant vessels, spectators, and the general public during the event. The temporary safety zone will restrict vessel traffic in a portion of the Intracoastal Waterway, preventing non-participant vessels from entering, transiting through, anchoring in, or remaining within the regulated area unless authorized by the Captain of the Port Charleston or a designated representative.
This rule is effective on April 24, 2016.
To view documents mentioned in this preamble as being available in the docket, go to
If you have questions on this rule, call or email Lieutenant John Downing, Sector Charleston Office of Waterways Management, Coast Guard; telephone (843) 740-3184, email
On February 8, 2016, Set Up Events notified the Coast Guard that it will sponsor the Xterra Myrtle Beach Swim from 7:15 a.m. to 9:15 a.m. on April 24, 2016. In response, on March 3, 2016, the Coast Guard published a notice of proposed rulemaking (NPRM) titled, Safety Zone; Xterra Swim, Myrtle Beach, SC Intracoastal Waterway; Myrtle Beach, SC [2016 FR 04664]. There we stated why we issued the NPRM, and invited comments on our proposed regulatory action related to this special local regulation. During the comment period that ended April 4, 2016, we received no comments.
Under good cause provisions in 5 U.S.C. 553(d)(3), we are making this rule effective less than 30 days after its publication in the
The legal basis for this rule is the Coast Guard's Authority to establish a safety zone: 33 U.S.C. 1231. The purpose of the proposed rule is to ensure safety of life on the navigable water of the United States during the swim portion of the Xterra Myrtle Beach Triathlon
As noted above, we received no comments on our NPRM published March 3, 2016. There are no changes in the regulatory text of this rule from the proposed rule in the NPRM. This rule establishes a safety zone from 7:15 to 9:15 a.m. on April 24, 2016. The safety zone will cover a portion of Atlantic Intracoastal Waterway in Myrtle Beach, South Carolina. Approximately 75 swimmers are anticipated to participate in the race. Persons and vessels desiring to enter, transit through, anchor in, or remain within the regulated area may contact the Captain of the Port Charleston by telephone at (843) 740-7050, or a designated representative via VHF radio on channel 16, to request authorization. If authorization to enter, transit through, anchor in, or remain within the regulated area is granted, all persons and vessels receiving such authorization must comply with the instructions of the Captain of the Port Charleston or a designated representative. The Coast Guard will provide notice of the safety zone by Local Notice to Mariners, Broadcast Notice to Mariners, and on-scene designated representatives.
We developed this rule after considering numerous statutes and Executive orders related to rulemaking. Below we summarize our analyses based on a number of these statutes and Executive orders, and we discuss First Amendment rights of protestors.
Executive Orders 12866 and 13563 direct agencies to assess the costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits. Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This rule has not been designated a “significant regulatory action,” under Executive Order 12866. Accordingly, it has not been reviewed by the Office of Management and Budget.
The economic impact of this rule is not significant for the following reasons: (1) The temporary safety zone would be enforced for only two hours; (2) although persons and vessels would not be able to enter, transit through, anchor in, or remain within the regulated area without authorization from the Captain of the Port Charleston or a designated representative, they would be able to operate in the surrounding area during the enforcement periods; (3) persons and vessels would still be able to enter, transit through, anchor in, or remain within the regulated area if authorized by the Captain of the Port Charleston or a designated representative; and (4) the Coast Guard would provide advance notification of the regulated area to the local maritime community by Local Notice to Mariners and Broadcast Notice to Mariners.
The Regulatory Flexibility Act of 1980, 5 U.S.C. 601-612, as amended, requires Federal agencies to consider the potential impact of regulations on small entities during rulemaking. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000. The Coast Guard received no comments from the Small Business Administration on this rulemaking. The Coast Guard certifies under 5 U.S.C. 605(b) that this
Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we want to assist small entities in understanding this rule. If the rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact the person listed in the
Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.
This rule will not call for a new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).
A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. We have analyzed this rule under that Order and have determined that it is consistent with the fundamental federalism principles and preemption requirements described in Executive Order13132.
Also, this rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes. If you believe this rule has implications for federalism or Indian tribes, please contact the person listed in the
The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. Though this rule will not result in such expenditure, we do discuss the effects of this rule elsewhere in this preamble.
We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (42 U.S.C. 4321-4370f), and have made a preliminary determination that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment. This rule involves a temporary safety zone issued in conjunction with a regatta or marine parade. This rule is categorically excluded from further review under paragraph 34(g) of Figure 2-1 of the Commandant Instruction.
The Coast Guard respects the First Amendment rights of protesters. Protesters are asked to contact the person listed in the
Marine safety, Navigation (water), Reporting and recordkeeping requirements, Waterways.
For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165 as follows:
33 U.S.C. 1226, 1231; 50 U.S.C. 191; 33 CFR 1.05-1(g), 6.04-1, and 160.5; Department of Homeland Security Delegation No. 0170.1.
(a)
(b)
(c)
(2) Persons and vessels desiring to enter, transit through, anchor in, or remain within the regulated area may contact the Captain of the Port Charleston by telephone at (843) 740-7050, or a designated representative via VHF radio on channel 16, to request authorization. If authorization to enter, transit through, anchor in, or remain within the regulated area is granted, all persons and vessels receiving such authorization must comply with the instructions of the Captain of the Port Charleston or a designated representative.
(3) The Coast Guard will provide notice of the regulated area by Marine Safety Information Bulletins, Local Notice to Mariners, Broadcast Notice to Mariners, and on-scene designated representatives.
(d)
Postal Service
Final rule.
The Postal Service is revising
The effective date of this rule is June 3, 2016.
Paula Rabkin at 202-268-2537.
New classification changes are available under Docket Number MC2016-118 on the Postal Regulatory Commission's Web site at
This final rule describes the international classification changes and the corresponding mailing standards changes for the following Competitive Service:
Priority Mail International® service provides reliable and affordable international delivery service to more than 180 countries. The price for Priority Mail International service is unchanged. The following classification changes are made to support the shift of certain volumes to the air parcel stream:
Currently, the Postal Service dispatches Priority Mail International Flat Rate Envelopes and Small Flat Rate Priced Boxes in the letter post stream, while all other Priority Mail International items are dispatched in the air parcel stream. We are moving the Priority Mail International Flat Rate Envelopes and Small Flat Rate Priced Boxes to the air parcel stream so that these items can receive the expanded access to tracking and insurance available to all other Priority Mail International items.
Foreign relations, International postal services.
The Postal Service hereby adopts the following changes to
5 U.S.C. 552(a); 13 U.S.C. 301-307; 18 U.S.C. 1692-1737; 39 U.S.C. 101, 401, 403, 404, 407, 414, 416, 3001-3011, 3201-3219, 3403-3406, 3621, 3622, 3626, 3632, 3633, and 5001.
[Revise the second sentence of item c to read as follows:]
c. * * * In certain circumstances, this might require the mailer to send the mailpiece via Priority Mail Express International service or Priority Mail International service.
Exhibit 123.61
Customs Declaration Form Usage by Mail Category
[
b. Priority Mail International service.
[
Priority Mail International is subject to the provisions of the Universal Postal Union Parcel Convention. This classification is primarily designed to accommodate larger and heavier shipments whose size and/or weight exceeds the limits for First-Class Mail International Service or First-Class Package International Service. For countries that offer parcel service, maximum weight limits range from 22 pounds to 70 pounds. To determine the maximum weight limit for each country, see the Individual Country Listings. At the sender's option, extra services, such as additional merchandise insurance coverage and return receipt service, may be added on a country-specific basis.
Priority Mail International Flat Rate Envelopes and Small Flat Rate Priced Boxes provide customers with an economical means of sending correspondence, documents, printed matter, and lightweight merchandise items to foreign destinations. The maximum weight limit is 4 pounds. Registered Mail service is not available for Priority Mail International Flat Rate Envelopes and Small Flat Rate Priced Boxes. At the sender's option, extra services, such as additional merchandise insurance coverage and return receipt service, may be added to Priority Mail International Flat Rate Envelopes and Small Flat Rate Priced Boxes on a country-specific basis.
[
Priority Mail International service is considered a parcel stream for mail exchange purposes.
[
Correspondence, negotiable and nonnegotiable documents, printed matter, and lightweight merchandise items may be sent in Priority Mail International Flat Rate Envelopes or Small Flat Rate Priced Boxes provided the contents are mailable, they fit securely in the envelope or box, and they are entirely confined within the container with the provided adhesive as the means of closure. The flap must close within the prefabricated fold. Tape may be applied to the flap and seams for closure or for reinforcement, provided the design of the container is not enlarged by opening the sides and taping or reconstructing the container in any way. Refer to the Individual Country Listings for additional prohibitions for each country. Priority Mail International Flat Rate Envelopes and Small Flat Rate Priced Boxes containing merchandise are insured against loss, damage, or missing contents up to $200 at no additional charge. Additional merchandise insurance may be available, depending on country and value. Priority Mail International Flat Rate Envelopes and Small Flat Rate Priced Boxes containing only nonnegotiable documents are insured against loss, damage, or missing contents up to $100 for document reconstruction at no additional charge. See Exhibit 322.2 and the Individual Country Listings for insurance availability, limitations, and coverage. Registered Mail service is not available.
[
Each Priority Mail International Flat Rate Envelope and each Priority Mail International Small Flat Rate Priced Box must bear a properly completed PS Form 2976-A.
[
No Priority Mail International items (USPS-produced Flat Rate Boxes, Flat Rate Envelopes, and Small Flat Rate Priced Boxes; USPS-produced Tyvek envelopes; or customer-supplied boxes and envelopes) are sealed against inspection. Regardless of physical closure, the mailing of Priority Mail International items constitutes consent by the mailer to inspection of the contents.
[
Priority Mail International items containing merchandise are insured against loss, damage, or missing contents up to $200 at no additional charge.* * *
232.91 Merchandise Insurance
Merchandise insurance that provides coverage greater than the included $200 merchandise insurance is available for Priority Mail International items to many countries. * * *
Return receipt service is available for purchase to certain destinations (see the Individual Country Listings for availability) for Priority Mail International items, including Priority Mail International Small Flat Rate Priced Boxes, and Priority Mail International Flat Rate Envelopes. See 340 for preparation procedures.
The following conditions apply to dutiable merchandise mailed with First-Class Mail International service:
d. The maximum value for dutiable merchandise is $400. Items exceeding $400 must be mailed using Global Express Guaranteed service, Priority Mail Express International service, or Priority Mail International service.
* * * Items exceeding $400 must be mailed using Global Express Guaranteed service, Priority Mail Express International service, or Priority Mail International service.
a. Registered Mail service for First-Class Mail International items and First-Class Package International Service items.
b. Additional merchandise insurance service for Priority Mail International Flat Rate Envelopes and Small Flat Rate Priced Boxes up to 4 pounds and Priority Mail International items up to 15 pounds.
Priority Mail International shipments containing merchandise are insured against loss, damage, or missing contents up to $200 at no additional charge. Priority Mail International shipments containing only nonnegotiable documents are insured against loss, damage, or missing contents up to $100 for document reconstruction at no additional charge. Indemnity is paid by the U.S. Postal Service as provided in 933. For a fee, the sender may purchase additional insurance to protect against loss, damage, or missing contents for Priority Mail International items containing merchandise, subject to individual country limitations. Additional document reconstruction insurance may not be purchased. If the item has been lost, or if it has been delivered to the addressee in damaged condition or with missing contents, payment is made to the sender unless the sender waives the right to payment, in writing, in favor of the addressee.
Merchandise insurance above the included $200 amount is available for all Priority Mail International items, to certain countries. See Exhibit 322.2.
Customers may purchase Registered Mail service for items that weigh up to 4 pounds. Registered Mail service is not available with Global Express Guaranteed, Priority Mail Express International, or Priority Mail International service or any type of M-bag service. See Individual Country Listings for additional country-specific prohibitions and restrictions. Registered Mail service is available for the following types of mail:
a. First-Class Mail International items, including Free Matter for the Blind items.
b. First-Class Package International Service items, including Free Matter for the Blind items.
PS Form 2865,
Return receipts can be purchased only at the time of mailing and are available only for a registered item or a Priority Mail International item. * * *
Regardless of the amount of deficiency, consider as paid in full each shortpaid Priority Mail International item that is paid with a permit imprint or USPS-produced postage validation imprinter (PVI) label, and dispatch it to the appropriate International Service Center (ISC).
The disposition of a shortpaid Priority Mail International item paid with a postage payment method other than a permit imprint or USPS-produced PVI label is based on the amount of the deficiency, as follows: * * *
Regardless of the amount of deficiency, consider as paid in full each shortpaid First-Class Mail International item (including a postcard), First-Class Package International Service item, and Airmail M-bag that is paid with a permit imprint or USPS-produced postage validation imprinter (PVI) label, and dispatch it to the appropriate International Service Center (ISC).
The disposition of a shortpaid First-Class Mail International item (including a postcard), First-Class Package International Service item, and Airmail M-bag that is paid with a postage payment method other than a permit imprint or USPS-produced PVI label is based on the amount of the deficiency, as follows: * * *
Inquiries can be initiated for Global Express Guaranteed (GXG) items, Priority Mail Express International items, Priority Mail International items, and registered items. Inquiries are not accepted for ordinary letters or M-bags. * * *
Exhibit 921.2
* * * For inquiries on Priority Mail International items or Registered Mail items, customers must allow foreign posts approximately 60 days to research and respond to the International Research Group. * * *
The U.S. Postal Service will initiate an inquiry within the time frames
Available for Priority Mail International merchandise only (see 323.72 for markings)
All Priority Mail International items:
PS Form 2976-A inside PS Form 2976-E (envelope)
Free when sent as Priority Mail International parcels. Weight limit: 15 pounds.
First-Class Mail International items or First-Class Package International Service items:
PS Form 2976 as required (see 123.61)
Priority Mail International items (including Priority Mail International Flat Rate Envelopes and Priority Mail International Small Flat Rate Priced Boxes):
PS Form 2976-A inside PS Form 2976-E (envelope)
Available only for First-Class Mail International, including postcards, First-Class Package International Service, and Free Matter for the Blind sent as First-Class Mail International and First-Class Package International Service.
Available for Registered Mail and Priority Mail International only.
Not Available.
Not Available.
Not Available.
Not Available.
We will publish an appropriate amendment to 39 CFR part 20 to reflect these changes.
Environmental Protection Agency.
Direct final rule.
The Environmental Protection Agency (EPA) is taking direct final action to approve a portion of a revision to the Tennessee State Implementation Plan (SIP) submitted on March 14, 2014, by the State of Tennessee, through the Tennessee Department of Environmental Conservation (TDEC) on behalf of the Knox County Department of Air Quality Management (Knox County) to address changes to a Knox County regulation regarding permits. EPA has determined that Tennessee's requested SIP revision is consistent with the applicable provisions of the Clean Air Act (CAA or Act).
This direct final rule is effective June 21, 2016 without further notice, unless EPA receives adverse comment by May 23, 2016. If EPA receives such comments, it will publish a timely withdrawal of the direct final rule in the
Submit your comments, identified by Docket ID No. EPA-R04-OAR-2015-0618 at
Zuri Farngalo or D. Brad Akers, Air Regulatory Management Section, Air Planning and Implementation Branch, Air, Pesticides and Toxics Management Division, U.S. Environmental Protection Agency, Region 4, 61 Forsyth Street SW., Atlanta, Georgia 30303-8960. Mr. Farngalo can be reached at (404) 562-9152 and via electronic mail at
On March 14, 2014, TDEC submitted to EPA several revisions to the Knox County portion of the Tennessee SIP. At this time, EPA is acting on one portion of the submittal: Section 25 of the Knox County Air Quality Management Regulations,
The portion of Tennessee's March 14, 2014, SIP submittal that EPA is approving today is the addition to the Knox County Air Quality Management Regulations of section 25.11,
In this rule, EPA is finalizing regulatory text that includes incorporation by reference. In accordance with requirements of 1 CFR 51.5, EPA is finalizing the incorporation by reference of Knox County Air Quality Management Regulations section 25.11,
EPA is approving a portion of Tennessee's March 14, 2014, SIP revision addressing changes to a Knox County regulation regarding permits. EPA is publishing this rule without prior proposal because the Agency views this as a noncontroversial submittal and anticipates no adverse comments. However, in the proposed rules section of this
If EPA receives such comments, then EPA will publish a document withdrawing the final rule and informing the public that the rule will not take effect. All public comments received will then be addressed in a subsequent final rule based on the proposed rule. EPA will not institute a second comment period. Parties interested in commenting should do so at this time. If no such comments are received, the public is advised that this rule will be effective on June 21, 2016 and no further action will be taken on the proposed rule.
Under the CAA, the Administrator is required to approve a SIP submission that complies with the provisions of the Act and applicable federal regulations.
• Is not a significant regulatory action subject to review by the Office of Management and Budget under Executive Orders 12866 (58 FR 51735, October 4, 1993) and 13563 (76 FR 3821, January 21, 2011);
• Does not impose an information collection burden under the provisions of the Paperwork Reduction Act(44 U.S.C. 3501
• Is certified as not having a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601
• Does not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4);
• Does not have Federalism implications as specified in Executive Order 13132 (64 FR 43255, August 10, 1999);
• Is not an economically significant regulatory action based on health or safety risks subject to Executive Order 13045 (62 FR 19885, April 23, 1997);
• Is not a significant regulatory action subject to Executive Order 13211 (66 FR 28355, May 22, 2001);
• Is not subject to requirements of Section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) because application of those requirements would be inconsistent with the CAA; and
• Does not provide EPA with the discretionary authority to address, as appropriate, disproportionate human health or environmental effects, using practicable and legally permissible methods, under Executive Order 12898 (59 FR 7629, February 16, 1994).
The SIP is not approved to apply on any Indian reservation land or in any other area where EPA or an Indian tribe has demonstrated that a tribe has jurisdiction. In those areas of Indian country, the rule does not have tribal implications as specified by Executive Order 13175 (65 FR 67249, November 9, 2000), nor will it impose substantial direct costs on tribal governments or preempt tribal law.
The Congressional Review Act, 5 U.S.C. 801
Under section 307(b)(1) of the CAA, petitions for judicial review of this action must be filed in the United States Court of Appeals for the appropriate circuit by June 21, 2016. Filing a petition for reconsideration by the Administrator of this final rule does not affect the finality of this action for the purposes of judicial review nor does it extend the time within which a petition for judicial review may be filed, and shall not postpone the effectiveness of such rule or action. Parties with objections to this direct final rule are encouraged to file a comment in response to the parallel notice of proposed rulemaking for this action published in the proposed rules section of today's
Environmental protection, Air pollution control, Incorporation by reference, Intergovernmental relations, Reporting and recordkeeping requirements, Volatile organic compounds.
40 CFR part 52 is amended as follows:
42 U.S.C. 7401
(c) * * *
Environmental Protection Agency (EPA).
Final rule.
The Environmental Protection Agency (EPA) is taking final action on technical corrections and clarifications withdrawn from a previous direct final rule that amended provisions from the April 2014 Tier 3 final rulemaking and the July 2014 Quality Assurance Program final rulemaking. The regulatory changes being finalized in this final rule correct errors identified by the commenters and provide more clarity in the regulations to ensure that the regulations properly reflect the requirements established in those rules.
This final rule is effective on June 21, 2016.
The EPA has established a docket for this action under Docket ID No. EPA-HQ-OAR-2011-0135. All documents in the docket are listed on the
Julia MacAllister, Office of Transportation and Air Quality, Assessment and Standards Division (ASD), Environmental Protection Agency, 2000 Traverwood Drive, Ann Arbor MI 48105; Telephone number: (734) 214-4131;
Entities potentially affected by this rule include gasoline refiners and importers, ethanol producers, ethanol denaturant producers, butane and pentane producers, gasoline additive manufacturers, transmix processors, terminals, and fuel distributors.
Potentially regulated categories include:
This table is not intended to be exhaustive, but rather provides a guide for readers regarding entities likely to be regulated by this action. This table lists the types of entities that EPA is now aware could potentially be regulated by this action. Other types of entities not listed in the table could also be regulated. To determine whether your activities are regulated by this action, you should carefully examine the applicability criteria in the referenced regulations. If you have any questions regarding the applicability of this action to a particular entity, consult the person listed in the preceding
In this action we are finalizing amendments withdrawn from a February 2015 direct final rule and parallel Notice of Proposed Rulemaking (80 FR 9078 and 80 FR 8826, February 19, 2015). Both of those actions were initiated to correct and clarify various provisions of the Tier 3 Motor Vehicle Emission and Fuel Standards (“Tier 3”) rule without either expanding or making substantive changes to the applicable provisions. We also stated that if we received adverse comment by April 6, 2015, as to any part of the direct final rule, those parts would be withdrawn by publishing a timely notice in the
In the final QAP rule (79 FR 42078, July 18, 2014), the EPA added additional product transfer document (PTD) requirements for renewable fuels that informed parties who took ownership of renewable fuel that they would need to (a) use the fuel as it was intended,
The February 2015 direct final rule and parallel proposal also included an amendment to the introductory text of 40 CFR 80.1453(a)(12) to remove an extraneous reference to § 80.1433, as this section does not exist in the regulations (80 FR 9084, February 19, 2015). We did not receive any adverse comments on this amendment.
In this action, we are finalizing the originally intended changes to 40 CFR 80.1453: In the introductory text of paragraph (a), we are providing downstream end-user exemptions to the PTD requirements in the RFS program similar to other EPA fuels programs, without the “custody or” language that was inadvertently added in the February 2015 direct final rule and parallel proposal; and, in the introductory text of paragraph (a)(12), we are deleting the extraneous reference to § 80.1433.
After promulgation of the Tier 3 final rulemaking (79 FR 23414, April 28, 2014), we discovered some typographical errors and other imprecise language in the fuels regulations of 40 CFR part 80 that we believed would benefit from additional clarity. Subsequently, we published amendments to certain provisions, including 40 CFR 80.1616 and 80.1621 in the February 2015 direct final rule and parallel proposal (80 FR 9078 and 80 FR 8826, February 19, 2015). We explained that these amendments would correct and/or clarify various provisions of the Tier 3 rule without either expanding or making substantive changes to the applicable provisions. We received adverse comment on the amendments to 40 CFR 80.1616 and 80.1621. We are responding to those comments and finalizing changes to these provisions in this action, as described further below.
In the parallel proposal, we proposed to amend 40 CFR 80.1616(a) to correct a numbering error. The regulations currently jump from paragraph (a)(3) to (a)(5), so we added a “Reserved” paragraph (a)(4) for continuity in the February direct final rule. We did not receive adverse comment on this amendment. We are now finalizing this amendment in this action.
We also proposed a clarifying amendment to 40 CFR 80.1616(b)(2). In the April 2014 Tier 3 final rule, we finalized language in paragraph (b)(2) specifying that credits generated relative to the Tier 2 gasoline sulfur standard of 30 parts per million (ppm) will expire “after March 31, 2020, when the 2019 annual compliance report is due.” The intent of this language was to state that unused credits (that are still valid for use) that were generated relative to the 30 ppm Tier 2 gasoline sulfur standard would expire at the end of the 2019 compliance year (December 31, 2019), and must be reconciled in the 2019 annual compliance report. Refiners and importers are required to submit their annual compliance reports for the 2019 compliance year by March 31, 2020. (Compliance reports for a given year are due on March 31 of the following year.) We also note that in the Tier 3 final rule preamble we specified that all credits generated relative to the Tier 2 30 ppm sulfur standard prior to January 1, 2017 would be valid for five years or through December 31, 2019, whichever is earlier. (79 FR 23547, April 28, 2014.) In the Tier 3 Gasoline Sulfur program, as with all of our 40 CFR part 80 fuels programs, credits that expire on December 31 of a given year must be retired and reconciled in that year's annual compliance report, which is due on March 31 of the following year. The language we finalized in the Tier 3 final rule regulations was intended to express this. However, following promulgation of the Tier 3 final rule, we were contacted by regulated entities who believed that the language was confusing and suggested that we should edit the language to clarify that the credits themselves expire on December 31, 2019 and must be reconciled in the 2019 annual compliance report (due on March 31, 2020). We proposed to amend the language of 40 CFR 80.1616(b)(2) in the proposal accompanying the February 2015 direct final rule to make this clarification.
We received adverse comments on the clarifying amendment regarding the expiration of the credits on December 31, 2019. These comments advocated for small refiners and small volume refineries to be allowed to use credits for five years in all cases (
The proposed amendment to 40 CFR 80.1616(b)(2) was simply intended to ensure that the regulations clearly reflected EPA's interpretation of the applicable requirement,
Following publication of the April 2014 Tier 3 Final Rule, we were contacted by some refiners to clarify if or when small volume refineries could be disqualified from receiving small volume refinery status. At that time, we learned that a provision providing the disqualification criteria for small volume refineries had been inadvertently deleted from the regulatory text of the Tier 3 final rule.
We received adverse comment on the amendments to 40 CFR 80.1621 arguing that:
• EPA neither proposed nor finalized disqualification criteria for small volume refineries for the April 2014 Tier 3 rule, and thus did not provide regulated entities the opportunity to comment on the 20-day notification requirement following disqualification, and further that the restoration of 40 CFR 80.1621(d) was not a technical amendment.
• The wording of the February 2015 direct final rule and parallel proposal is confusing because it does not explicitly state exactly when and under which circumstances disqualification could occur.
• Small volume refineries should not be constrained or treated differently than small refiners regarding disqualification, including in the case of growth or mergers.
• The term “small refinery” was used instead of the correct term “small volume refinery.”
• EPA did not clarify if credits could continue to be generated during the 30-month grace period allowed for a disqualified small volume refinery to come into compliance.
• 40 CFR 80.1621 should be reorganized—disqualification criteria should not appear in this section of the regulations.
Our intent in the February 2015 direct final rule and parallel proposal was to correct an inadvertent omission of regulatory text for the disqualification of small volume refineries as discussed in the Tier 3 final rule preamble. (This discussion can be found at 79 FR 23552-53, April 28, 2014.) We explained (in both the April 2014 Tier 3 final rule, and in the February 2015 actions) that the application process for qualification for small volume refinery status was similar to the process for small refiner status. We further explained that a small refiner that owned and operated a small volume refinery would only need to apply for small refiner status. As explained above, the fact that the deletion of 40 CFR 80.1621(d) was inadvertent can be seen from the cross-reference to this provision in 40 CFR 80.1622(e) in both the proposed and final Tier 3 rule regulations. Thus, as previously explained, the amendment was intended to fix an omission, which was merely to restore 40 CFR 80.1621(d).
The inadvertent deletion of 40 CFR 80.1621(d) can be seen from the reference in 40 CFR 80.1622(e) in both the proposed and final regulations, which states that “A refiner who qualifies as a small refiner or small volume refinery under this subpart and subsequently fails to meet all the qualifying criteria as set out in §§ 80.1620 and 80.1621 will be disqualified pursuant to § 80.1620(f) or § 80.1621(d).” (79 FR 23662, April 28, 2014.) Further, the Tier 3 final rule preamble reflected our discussion of the similar treatment of both small volume refineries and small refiners, as evidenced by 40 CFR 80.1622. (79 FR 23549-23550, 23552-23553; April 28, 2014.) Moreover, the current small refiner disqualification provision at 40 CFR 80.1620(f), which contains both disqualification criteria and 20-day notification requirements, is analogous to the 40 CFR 80.1621(d) small volume refinery disqualification provision. Again, the April 2014 final Tier 3 rule intended for small refiner and small volume refinery qualification and disqualification for the Tier 3 program to be similar.
Regarding the comments that EPA should clarify when a disqualifying event occurs, we note that this would not be retroactive. Rather, such disqualification would occur after the effective date of the amended 40 CFR 80.1621(d), which is being amended in this regulatory action. For example, a refiner whose refinery was approved as a small volume refinery in 2015 prior to the restoration of 40 CFR 80.1621(d) would not be disqualified before the effective date of this final rulemaking. As such, the 30-month grace period afforded to small refiners and small volume refineries to come into compliance with the Tier 3 sulfur standards would not begin until the point that the refiner or its refinery is disqualified.
With regard to comments about the treatment of small volume refineries and small refiners with regard to growth or merger, we note that this is outside the scope of the rulemaking. While our intent with the Tier 3 program is to treat small refiners and small volume refineries similarly, there are some differences between small refiners and small volume refineries that require separate treatment, such as in the case of mergers.
As explained in the Tier 3 final rule, the Regulatory Flexibility Act (RFA) generally requires an agency to prepare a regulatory flexibility analysis of any rule subject to notice and comment rulemaking requirements under the Administrative Procedure Act or any other statute unless the agency certifies that the rule will not have a significant economic impact on a substantial number of small entities. Small entities include small businesses, small organizations, and small governmental jurisdictions. As also explained in the preamble to the Tier 3 final rule, in accordance with the Regulatory Flexibility Act, as amended by the Small Business Regulatory Enforcement Fairness Act (RFA/SBREFA), we assessed the impacts of the rule on small entities. For refiners, a small entity is defined in the Small Business Administration's size standards
Further, we finalized a “small volume refinery” definition in the Tier 3 program because, as stated in the preambles to both the proposed and final rulemakings, our modeling during the development of the Tier 3 program showed that the cost of compliance could be higher for certain facilities. We explained that some of these facilities, which may be owned by refiners that would not qualify as small entities, could potentially benefit from additional time for compliance with the Tier 3 program. Thus, we included flexibilities for small volume refineries that are similar to those for small refiners.
We note that the Tier 3 program's
Regarding comments requesting more clarity in the language of 40 CFR 80.1621(d), we note that the February 2015 direct final rule and parallel proposal used the imprecise term “small refinery” in place of the correct term “small volume refinery,” and we are correcting this language in this action. As disqualification is not meant to disallow the generation and use of credits during the 30-month period that is afforded to small refiners and small volume refineries to come into compliance with the Tier 3 program following a disqualifying event, clarifying language is also being added with this action. Lastly, we believe the comments regarding organization of this section of the regulations are outside of the scope. We also note that this organization is used in both the small refiner and small volume refinery provisions, to ensure that aspects of small refiner and small volume refinery qualification and related requirements were intentionally contained in the same sections of the regulations to provide a more streamlined approach for these parties to locate this information.
Thus, in this action, we are finalizing the restoration of 40 CFR 80.1621(d), with changes to ensure that the correct terminology (“small volume refinery”) is used, and to clarify when a disqualifying event could occur and that credits can be generated during the 30-month period following disqualification.
Additional information about these statutes and Executive Orders can be found at
This action is a significant regulatory action that was submitted to the Office of Management and Budget (OMB) for review. Any changes made in response to OMB recommendations have been documented in the docket.
This action does not impose any new information collection burden under the PRA, since it merely clarifies and corrects existing regulatory language. OMB has previously approved the information collection activities contained in the existing regulations and has assigned OMB control numbers as noted in the table below.
I certify that this action will not have a significant economic impact on a substantial number of small entities under the RFA. In making this determination, the impact of concern is any significant adverse economic impact on small entities. An agency may certify that a rule will not have a significant economic impact on a substantial number of small entities if the rule relieves regulatory burden, has no net burden or otherwise has a positive economic effect on the small entities subject to the rule. This rule merely clarifies and corrects existing regulatory language. We therefore anticipate no costs and therefore no regulatory burden associated with this rule. We have therefore concluded that this action will have no net regulatory burden for all directly regulated small entities.
This action does not contain any unfunded mandate as described in UMRA, 2 U.S.C. 1531-1538, and does not significantly or uniquely affect small governments. The action imposes no enforceable duty on any state, local or tribal governments. Requirements for the private sector do not exceed $100 million in any one year.
This action does not have federalism implications. It will not have substantial direct effects on the states, on the relationship between the national government and the states, or on the distribution of power and responsibilities among the various levels of government.
This action does not have tribal implications as specified in Executive Order 13175. This rule merely corrects and clarifies regulatory provisions. Tribal governments would be affected only to the extent they purchase and use regulated vehicles or engines. Thus, Executive Order 13175 does not apply to this action.
EPA interprets Executive Order 13045 as applying only to those regulatory actions that concern environmental health or safety risks that the EPA has reason to believe may disproportionately affect children, per the definition of “covered regulatory action” in section 2-202 of the Executive Order. This action is not subject to Executive Order 13045 because it does not concern an environmental health risk or safety risk.
This action is not a “significant energy action” because it is not likely to have a significant adverse effect on the supply, distribution or use of energy.
This rulemaking does not involve technical standards.
This action is not expected to have any adverse human health or environmental impacts; as a result, the human health or environmental risk addressed by this action will not have potential disproportionately high and adverse human health or environmental effects on minority, low-income or indigenous populations.
This action is subject to the CRA, and EPA will submit a rule report to each House of the Congress and to the Comptroller General of the United States. This action is not a “major rule” as defined by 5 U.S.C. 804(2).
Environmental protection, Administrative practice and procedure, Air pollution control, Confidential business information, Diesel fuel, Fuel additives, Gasoline, Imports, Penalties, Petroleum, Reporting and recordkeeping requirements.
For the reasons set forth in the preamble, EPA amends 40 CFR part 80 as follows:
42 U.S.C. 7414, 7521, 7542, 7545, and 7601(a).
(a) On each occasion when any party transfers ownership of neat and/or blended renewable fuels, except when such fuel is dispensed into motor vehicles or nonroad vehicles, engines, or equipment, or separated RINs subject to this subpart, the transferor must provide to the transferee documents that include all of the following information, as applicable:
(12) For the transfer of renewable fuel for which RINs were generated, an accurate and clear statement on the product transfer document of the fuel type from Table 1 to § 80.1426, and designation of the fuel use(s) intended by the transferor, as follows:
(a) * * *
(4) [Reserved]
(b) * * *
(2) Credits generated under § 80.1615(b) through (d) are valid for use for five years after the year in which they are generated, except that any CR
(c) [Reserved]
(d)(1) A refinery approved as a small volume refinery under § 80.1622 that subsequently ceases production of gasoline from processing crude oil through refinery processing units or exceeds the 75,000 barrel average aggregate daily crude oil throughput limit is disqualified as a small volume refinery. If such disqualification occurs, the refinery shall notify EPA in writing no later than 20 days following the disqualifying event.
(2) Any refinery whose status changes under this paragraph (d) shall meet the applicable standards of § 80.1603 within a period of up to 30 months from the disqualifying event.
National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.
Final rule.
NMFS issues regulations to revise the authorized methods for payment of cost recovery fees for the Halibut and Sablefish Individual Fishing Quota Program and the Bering Sea and Aleutian Islands Crab Rationalization Program. These regulations are necessary to improve data security procedures and to reduce administrative costs of processing cost recovery fee payments. This final rule is intended to promote the goals and objectives of the Magnuson-Stevens Fishery Conservation and Management Act, the Northern Pacific Halibut Act of 1982, the Fishery Management Plan for Groundfish of the Bering Sea and Aleutian Islands Management Area, the Fishery Management Plan for Groundfish of the Gulf of Alaska, the Fishery Management Plan for Bering Sea/Aleutian Islands King and Tanner Crabs, and other applicable laws.
Effective May 23, 2016.
Electronic copies of the following documents are available from
• The Regulatory Impact Review/Initial Regulatory Flexibility Analysis (RIR/IRFA), the final Regulatory Impact Review (RIR), and the Categorical Exclusion prepared for this action.
Written comments regarding the burden-hour estimates or other aspects of the collection-of-information requirements contained in this rule may be submitted by mail to NMFS Alaska Region, P.O. Box 21668, Juneau, AK 99802-1668, Attn: Ellen Sebastian, Records Officer; in person at NMFS Alaska Region, 709 West 9th Street, Room 420A, Juneau, AK; by email to
Keeley Kent, 907-586-7228.
NMFS published a proposed rule to revise the authorized methods for payment of cost recovery fees for the Halibut and Sablefish Individual Fishing Quota Program (IFQ Program) and the Bering Sea and Aleutian Islands Crab Rationalization Program (CR Program) on December 31, 2015 (80 FR 81798). The comment period on the proposed rule ended on February 1, 2016.
The following is a brief description of the IFQ Program and CR Program cost recovery and the authorized payment methods. For a more detailed description, please see Section 1.2 of the RIR (see
Section 304(d) of the Magnuson-Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act) specifies that the Secretary of Commerce is authorized, and shall collect a fee, to recover the actual costs directly related to the management, data collection, and enforcement of any limited access privilege program (LAPP) and community development quota program (CDQ) that allocates a percentage of the total allowable catch of a fishery to such program. Section 304(d) also specifies that such fee shall not exceed three percent of the ex-vessel value of fish harvested under any such program.
The IFQ Program is a LAPP as defined in the Magnuson-Stevens Act. NMFS implemented cost recovery for the IFQ Program in 2000 (65 FR 14919, March 20, 2000). Regulations implementing IFQ Program cost recovery are located at § 679.45. The CR Program is also a LAPP as defined in section 304(d) of the Magnuson-Stevens Act. Section 313(j) of the Magnuson-Stevens Act provides supplementary authority to section 304(d) and additional detail for cost recovery provisions specific to the CR Program. NMFS implemented cost recovery with the final rule to implement the CR Program in 2005 (70 FR 10174, March 2, 2005). Regulations implementing CR Program cost recovery are located at § 680.44.
NMFS recovers the incremental costs of managing and enforcing the IFQ Program and CR Program annually through a fee paid by persons who hold a permit granting an exclusive access privilege to a portion of the total allowable catches in IFQ Program and CR Program fisheries. NMFS calculates cost recovery fees for fish (including crab) that are landed and deducted from the total allowable catch in the fisheries subject to cost recovery. NMFS annually calculates the cost recovery fee percentage for the halibut and sablefish IFQ Program and for the CR Program by dividing the total program costs for each program by the total ex-vessel value of the catch subject to the cost recovery fee for the current year. Section 1.2 of the RIR and the preamble of the proposed rule (80 FR 81798, December 31, 2015) for this action describe these processes in greater detail.
The method used by NMFS to calculate the IFQ cost recovery fee percentage is described at § 679.45(d)(2)(ii). The IFQ permit holder is responsible for submitting their cost recovery payment to NMFS on or before the due date of January 31 following the year in which the IFQ halibut and sablefish landings were made. Additional information on the administration of IFQ Program cost recovery is provided in Section 3.5.1.1 of the RIR.
The method used by NMFS to calculate the CR Program cost recovery fee percentage is described at § 680.44(c)(2). The Registered Crab Receiver (RCR) is responsible for submitting payment to NMFS on or before the due date of July 31, following the crab fishing year in which payment for the crab is made. Additional information on the administration of CR Program cost recovery is provided in Section 3.5.2.2 of the RIR.
This final rule revises the authorized cost recovery fee payment methods for the IFQ and CR Programs by revising regulations at § 679.45(a)(4)(ii) through (iv), § 680.5(g)(3)(iii), and § 680.44(a)(4)(iii) and (iv), and eliminates the option for IFQ permit holders and CR Program RCRs to submit credit card payment information by mail or facsimile upon the effective date of this final rule. Prior to this final rule, cost recovery regulations for the IFQ Program and CR Program (§ 679.45(a)(4)(iv) and § 680.44(a)(4)(iv), respectively) allowed permit holders to pay their fee electronically or non-electronically in U.S. dollars by personal check drawn on a U.S. bank account, money order, bank-certified check, or credit card. Electronic payments could be made using credit card or electronic check via the pay.gov web-based system, or by wiring payment directly from the permit holder's financial institution via the Fedwire Funds Service (Fedwire) funds transfer system. Non-electronic payments could be made by submitting a paper form to NMFS with credit card information via mail or facsimile, or by submitting a paper check or money order via mail.
Non-electronic submission of payment information to NMFS via mail or facsimile is less secure and results in higher administrative costs than electronic payments because it results in transmission of permit holders' financial information over the NMFS information network and requires NMFS to manually process payments. Before this final rule, permit holders could pay a cost recovery fee with a credit card by submitting a form via mail or facsimile with their credit card information to NMFS. Manual credit card processing results in the possession and transmission of IFQ Program and CR Program permit holders' credit card information over the NMFS information network. Manual credit card processing is a less secure method of payment than the permit holder directly entering their credit card information into pay.gov, and results in higher administrative costs for NMFS. Administrative costs to collect fees are subject to cost recovery. Therefore, the higher administrative costs to process credit cards manually results in an increased fee liability for the IFQ and CR Programs relative to electronic payments.
This final rule also eliminates paper checks, money orders, and bank-certified checks as authorized payment methods beginning with the 2020 cost recovery fee payment billing cycle. Payment with a paper check, money order, or bank-certified check can also increase administrative costs. Payment with paper check, money order, or bank certified check requires NMFS to manually update the internal cost recovery payment tracking system to reflect the payment. Discrepancies or errors between the cost recovery amount owed and the amount paid by check must be addressed by NMFS. Payment with paper check, money order, or bank-certified check results in higher administrative costs for NMFS, and those additional costs increase the fee liability for the IFQ and CR Programs relative to electronic payments.
This final rule requires all permit holders to submit payments through pay.gov or Fedwire beginning with the IFQ Program cost recovery fee payment due by January 31, 2020, and beginning with the CR Program cost recovery fee payment due by July 31, 2020. All cost recovery fee payments must be made electronically for any payment made on or after the first day of the billing cycle for IFQ Program and CR Program cost recovery fee payments that will be due in 2020. NMFS will allow non-electronic payments via paper check or money order until the 2020 cost recovery fee billing cycle to provide a transition period for permit holders to become familiar with, and begin transitioning to, electronic payment methods.
Electronic payments via the pay.gov system and the Fedwire system are the most secure methods of transmitting financial information and result in the lowest administrative costs for NMFS. IFQ Program and CR Program permit holders can access pay.gov through the NMFS Alaska Region online system called eFISH. Pay.gov is operated by the U.S. Department of the Treasury (Treasury) and offers the highest level of
Through pay.gov, permit holders can make cost recovery payments using a credit card, debit card, or direct debit (electronic check). Due to the transaction fee incurred by the Treasury, there is a payment limit of $24,999.99 on credit card transactions through pay.gov (see notice online at:
Permit holders may also make cost recovery fee payments through Fedwire. Fedwire is a real-time transfer system that allows financial institutions to electronically transfer funds. Fedwire allows wire transfers of fee payments from any bank or wire transfer service to NMFS to fulfill cost recovery fee obligations. Payments are processed individually through Fedwire, which uses a highly secure electronic network.
Table 1 contains the implementation schedule for this final rule to revise authorized cost recovery fee payment methods.
NMFS received no public comments on the proposed rule for this action.
This final rule includes a change to the regulatory text and amendatory instructions published in the proposed rule. This final rule modifies amendatory instructions and removes § 680.5(g)(3)(iii), which describes the requirement for RCRs to submit the fee submission form, includes a description of the authorized payment methods for RCRs, and includes a reference to payment methods that are modified by this final rule in § 680.44(a)(4)(iv). Although the proposed rule did not include the removal of § 680.5(g)(3)(iii), NMFS has determined that it would be inconsistent with the objectives of this action to include duplicative descriptions of the authorized payment methods for CR Program cost recovery within the regulations.
Pursuant to section 305(d) of the Magnuson-Stevens Act, the NMFS Assistant Administrator has determined this final rule is consistent with the fishery management plans, other provisions of the Magnuson-Stevens Act, and other applicable law.
This final rule has been determined to be not significant for purposes of Executive Order 12866.
Section 212 of the Small Business Regulatory Enforcement Fairness Act of 1996 states that, for each rule or group of related rules for which an agency is required to prepare a final regulatory flexibility analysis, the agency shall publish one or more guides to assist small entities in complying with the rule, and shall designate such publications as “small entity compliance guides.” The agency shall explain the actions a small entity is required to take to comply with a rule or group of rules. NMFS has posted a small entity compliance guide on the NMFS Alaska Region Web site (
Section 604 of the Regulatory Flexibility Act requires an agency to prepare a FRFA after being required by that section or any other law to publish a general notice of proposed rulemaking and when an agency promulgates a final rule under section 553 of Title 5 of the U.S. Code. The following paragraphs constitute the FRFA for this action. Section 604 describes the required contents of a FRFA: (1) A statement of the need for, and objectives of, the rule; (2) a statement of the significant issues raised by the public comments in response to the initial regulatory flexibility analysis, a statement of the assessment of the agency of such issues, and a statement of any changes made in the proposed rule as a result of such comments; (3) the response of the agency to any comments filed by the Chief Counsel for Advocacy of the Small Business Administration in response to the proposed rule, and a detailed statement of any change made to the proposed rule in the final rule as a result of the comments; (4) a description of and an estimate of the number of small entities to which the rule will apply or an explanation of why no such estimate is available; (5) a description of the projected reporting, recordkeeping and other compliance requirements of the rule, including an estimate of the classes of small entities which will be subject to the requirement and the type of professional skills necessary for preparation of the report or record; and (6) a description of the steps the agency has taken to minimize the significant economic impact on small entities consistent with the stated objectives of applicable statutes, including a statement of the factual, policy, and legal reasons for selecting the alternative adopted in the final rule and why each one of the other significant alternatives to the rule considered by the agency which affect the impact on small entities was rejected.
The purpose of this rule is to improve security procedures for protecting financial information and to reduce costs associated with administering cost recovery. The current regulations for IFQ Program and the CR Program cost recovery allow permit holders to submit credit card information for manual credit card processing by NMFS. This results in the possession and electronic transmission of financial information on the NMFS information network, which
This rule also reduces administrative costs for the IFQ Program and CR Program by eliminating other non-electronic payment methods that require manual processing. Manual processing of cost recovery fee payments made by check and money order generates significant costs for the administration of these programs. Eliminating these non-electronic payment methods from authorized payment method options reduces the staffing burden for processing cost recovery fee payments and further reduces the costs of administering cost recovery. Reduced administrative costs will result in lower overall fee liabilities for the IFQ and CR Programs.
NMFS published a proposed rule to revise the authorized methods for payment of cost recovery fees for the IFQ Program and the CR Program on December 31, 2015 (80 FR 81798). The comment period on the proposed rule ended on February 1, 2016. An IRFA was prepared and summarized in the Classification section of the preamble to the proposed rule. NMFS received no comments on this proposed rule, the IRFA, or the economic impacts of this action generally. The Chief Counsel for Advocacy of the Small Business Administration did not file any comments on the proposed rule.
The entities directly regulated by this rule are permit holders who make halibut and sablefish landings in the IFQ Program fisheries and RCRs who receive landings of crab in the CR Program fisheries. The universe of entities was defined based on who is directly billed by NMFS for cost recovery fees, and therefore who will be directly impacted by a change in the authorized payment methods.
The Small Business Administration (SBA) defines a small commercial finfish fishing entity as one that has annual gross receipts, from all activities of all affiliates, of less than $20.5 million (79 FR 33647, June 12, 2014). All of the IFQ permit holders are considered to be commercial finfish fishing entities. Based upon available data, and more general information concerning the probable economic activity of vessels in the IFQ Program fisheries, no entity could have landed more than $20.5 million in combined gross receipts in 2014. Therefore, all 2,038 IFQ permit holders are classified as small entities.
For the CR Program, 18 RCRs were directly billed for cost recovery fee liabilities in the crab fishing year 2014/2015. These 18 RCRs include persons who operate as non-profit entities, seafood dealers that receive but do not process crab, shellfish harvesters, and seafood processors. Section 4.6 of the RIR/IRFA prepared for this rule describes how RCRs operating in these different categories were assessed under the SBA business size criteria (see
At the time that NMFS conducted the analysis for the IRFA, the SBA defined a seafood processor as a small entity if that entity was independently owned and operated, not dominant in its field of operation, and had a combined annual employment of fewer than 500 employees. On January 26, 2016, the SBA issued a final rule revising the small business size standards for several industries, effective February 26, 2016 (81 FR 4469). SBA's final rule modified the size standard for “seafood product preparation and packaging” (NAICS code 311710) that applies to seafood processors. SBA's final rule modified the definition of a small entity operating as a seafood processor to include all entities that are independently owned and operated, not dominant in their field of operation, and have a combined annual employment of fewer than 750 employees. In this FRFA, NMFS has analyzed the nine RCRs operating as seafood processors using the revised definition of a small entity. The new definition of a small entity did not change the number of seafood processors classified as small. NMFS estimates that three of the nine RCRs classified as seafood processors are small entities. Cumulatively, NMFS estimates that 11 of the 18 RCRs operating across all of the business size categories are small entities.
This rule requires modifications to the current recordkeeping and reporting requirements for IFQ Program and CR Program cost recovery in the Alaska Cost Recovery and Observer Fee collection (OMB Control Number 0648-0727). Specifically, this rule eliminates the option for payment by credit card using the paper fee submission form submitted to NMFS by mail or facsimile. Beginning with the 2020 cost recovery fee billing cycle, the paper fee submission form will be eliminated completely for the CR Program as permit holders will be required to submit all cost recovery fee payments electronically through the pay.gov or Fedwire systems. For the IFQ Program, beginning in 2020, the paper fee submission form will be revised to specify that all fee payments must be made electronically through pay.gov or the Fedwire systems.
The Magnuson-Stevens Act requires that participants in LAPP and CDQ programs pay up to three percent of the ex-vessel value of the fish they are allocated to cover specific costs that are incurred by the management agencies as a direct result of implementing the programs. NMFS has identified this rule as necessary to improve data security procedures for permit holders' financial information and to reduce administrative costs of processing cost recovery payments. There are no alternatives that, consistent with applicable law, will accomplish the objectives of this rule and result in lower adverse economic impacts on directly regulated small entities.
NMFS considered eliminating the submission of credit card payment information by phone, in person, facsimile, and mail and retaining the use of paper checks and money orders as authorized payment methods under Alternative 2 in the RIR. However, Alternative 2 failed to meet the objective of reducing administrative costs associated with administering cost recovery because processing these payments results in a greater staff burden than processing payments made by the pay.gov or Fedwire systems (see Section 3.7 of the RIR). NMFS also considered Alternative 3, which would have simultaneously implemented both the elimination of credit card payment by phone, in person, facsimile, and mail, and the elimination of paper check and money order payment (see Section 3.8 of the RIR). However, NMFS rejected Alternative 3 in favor of Alternative 3 Option 1, which provided accommodation for the transition costs to permit holders in complying with the
This final rule contains collection-of-information requirements subject to the Paperwork Reduction Act (PRA) and which have been approved by the Office of Management and Budget (OMB) under control number 0648-0727. Public reporting burden per response is estimated to average one minute for electronic fee submission and 30 minutes for non-electronic fee submission. Estimates for public reporting burden include the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information.
Send comments regarding these burden estimates or any other aspect of this data collection, including suggestions for reducing the burden, to NMFS (see
Alaska, Fisheries, Reporting and recordkeeping requirements.
For the reasons set out in the preamble, NMFS amends 50 CFR parts 679 and 680 as follows:
16 U.S.C. 773
(a) * * *
(4) * * *
(ii)
(iii)
(iv)
(B) On or after December 1, 2019, payment must be made electronically in U.S. dollars by automated clearing house, credit card, or electronic check drawn on a U.S. bank account.
16 U.S.C. 1862; Pub. L. 109-241; Pub. L. 109-479.
(a) * * *
(4) * * *
(iii)
(iv)
(B) On or after June 1, 2020, payment must be made electronically in U.S. dollars by automated clearing house, credit card, or electronic check drawn on a U.S. bank account.
Agricultural Marketing Service, USDA.
Notice of hearing on proposed rulemaking.
Notice is hereby given of a public hearing to receive evidence on proposed amendments to Marketing Order No. 989 (order) that regulates the handling of raisins grown in California. Five amendments are proposed by the Raisin Administrative Committee (Committee), which is responsible for local administration of the order. These proposed amendments would: Authorize production research; establish new nomination procedures for independent grower member and alternate member seats; add authority to regulate quality; add authority to establish different regulations for different markets; and add a continuance referenda requirement.
In addition, the Agricultural Marketing Service (AMS) proposes two amendments. These amendments would remove order language pertaining to volume regulation and reserve pool authority and would establish term limits for Committee members. In addition, AMS proposes to make any such changes as may be necessary to the order to conform to any amendment that may result from the hearing. These proposed amendments are intended to update the order to reflect past changes in the industry and potential future changes, and to improve the operation and administration of the order.
The hearing dates are May 3 and 4, 2016, 9:00 a.m. to 5:00 p.m.; and continuing on May 5, 2016, at 9:00 a.m., if necessary, in Clovis, California.
The hearing will be held at the Hilton Garden Inn Clovis, 520 W Shaw Ave., Clovis, CA 93612.
Melissa Schmaedick, Marketing Order and Agreement Division, Specialty Crops Program, AMS, USDA, Post Office Box 952, Moab, UT 84532; Telephone: (202) 557-4783, Fax: (435) 259-1502, or Michelle Sharrow, Marketing Order and Agreement Division, Specialty Crops Program, AMS, USDA, 1400 Independence Avenue SW., Stop 0237, Washington, DC 20250-0237; Telephone: (202) 720-2491, Fax: (202) 720-8938, or Email:
Small businesses may request information on this proceeding by contacting Antoinette Carter, Marketing Order and Agreement Division, Specialty Crops Program, AMS, USDA, 1400 Independence Avenue SW., Stop 0237, Washington, DC 20250-0237; Telephone: (202) 720-2491, Fax: (202) 720-8938, or Email:
This administrative action is instituted pursuant to the Agricultural Marketing Agreement Act of 1937, as amended (7 U.S.C. 601-674), hereinafter referred to as the “Act.” This action is governed by the provisions of sections 556 and 557 of title 5 of the United States Code and, therefore, is excluded from the requirements of Executive Order 12866.
The Regulatory Flexibility Act (5 U.S.C. 601-612) seeks to ensure that within the statutory authority of a program, the regulatory and informational requirements are tailored to the size and nature of small businesses. Interested persons are invited to present evidence at the hearing on the possible regulatory and informational impacts of the proposals on small businesses.
The amendments proposed herein have been reviewed under Executive Order 12988, Civil Justice Reform. They are not intended to have retroactive effect.
The Act provides that administrative proceedings must be exhausted before parties may file suit in court. Under section 608c(15)(A) of the Act, any handler subject to an order may file with USDA a petition stating that the order, any provision of the order, or any obligation imposed in connection with the order is not in accordance with law and request a modification of the order or to be exempted therefrom. A handler is afforded the opportunity for a hearing on the petition. The Act provides that the district court of the United States in any district in which the handler is an inhabitant, or has his or her principal place of business, has jurisdiction to review the USDA's ruling on the petition, provided an action is filed not later than 20 days after the date of the entry of the ruling.
The hearing is called pursuant to the provisions of the Act and the applicable rules of practice and procedure governing the formulation of marketing agreements and orders (7 CFR part 900).
The proposed amendments were recommended by the Committee on January 27, 2016, and submitted to USDA on February 2, 2016. After reviewing the proposals and other information submitted by the Committee, USDA made a determination to schedule this matter for hearing.
The proposed amendments to the order recommended by the Committee are summarized as follows:
1. Amend § 989.53 to authorize production research.
2. Amend §§ 989.29 and 989.129 to authorize separate nominations for independent grower member and independent grower alternate member seats.
3. Amend §§ 989.58, 989.59 and 989.61 to add authority to regulate quality. A corresponding change would also revise the heading prior to § 989.58 to include quality.
4. Amend § 989.59 to add authority to establish different regulations for different markets.
5. Amend § 989.91 to require continuance referenda.
6. Amend the order to remove volume regulation and reserve pool authority. This would include: Removing §§ 989.55 and 989.56, §§ 989.65 through 989.67, §§ 989.71, 989.72, 989.82, 989.154, 989.156, 989.166, 989.167, 989.221, 989.257 and 989.401; revising §§ 989.11, 989.53, 989.54, 989.58, 989.59, 989.60, 989.73, 989.79, 989.80, 989.84, 989.158, 989.173 and 989.210; and, redesignating § 989.70 as § 989.96. Corresponding changes would also remove the following headings:
7. Amend § 989.28 to establish term limits.
The Committee works with USDA in administering the order. These proposals submitted by the Committee have not received the approval of USDA. The Committee believes that its proposed amendments would update the order to address changes that have occurred in the industry and potential changes that could occur in the future. The amendments are intended to improve the operation and administration of the order.
In addition to the proposed amendments to the order, AMS proposes to make any such changes as may be necessary to the order to conform to any amendment that may result from the hearing or to correct minor inconsistencies and typographical errors.
The public hearing is held for the purpose of: (i) Receiving evidence about the economic and marketing conditions which relate to the proposed amendments of the order; (ii) determining whether there is a need for the proposed amendments to the order; and (iii) determining whether the proposed amendments or appropriate modifications thereof will tend to effectuate the declared policy of the Act.
Testimony is invited at the hearing on all the proposals and recommendations contained in this notice, as well as any appropriate modifications or alternatives.
All persons wishing to submit written material as evidence at the hearing should be prepared to submit four copies of such material at the hearing. Four copies of prepared testimony for presentation at the hearing should also be made available. To the extent practicable, eight additional copies of evidentiary exhibits and testimony prepared as an exhibit should be made available to USDA representatives on the day of appearance at the hearing. Any requests for preparation of USDA data for this rulemaking hearing should be made at least 10 days prior to the beginning of the hearing.
From the time the notice of hearing is issued and until the issuance of a final decision in this proceeding, USDA employees involved in the decisional process are prohibited from discussing the merits of the hearing issues on an
Procedural matters are not subject to the above prohibition and may be discussed at any time.
Raisins, Marketing agreements, Reporting and recordkeeping requirements.
7 U.S.C. 601-674.
Proposals submitted by the Raisin Administrative Committee:
(a)
The revisions and addition read as follows:
(b) * * *
(2) * * *
(i) * * *
(ii) Each such producer whose name is offered in nomination for producer member positions to represent on the committee independent producers or producers who are affiliated with cooperative marketing association(s) handling less than 10 percent of the total raisin acquisitions during the preceding crop year shall be given the opportunity to provide the committee a short statement outlining qualifications and desire to serve if selected. Similarly, each such producer whose name is offered in nomination for producer alternate member positions to represent on the committee independent producers or producers who are affiliated with cooperative marketing association(s) handling less than 10 percent of the total raisin acquisitions during the preceding crop year shall be given the opportunity to provide the committee a short statement outlining qualifications and desire to serve if selected. These brief statements, together with a ballot and voting instructions, shall be mailed to all independent producers and producers who are affiliated with cooperative marketing associations handling less than 10 percent of the total raisin acquisitions during the preceding crop year of record with the committee in each district. The producer member candidate receiving the highest number of votes shall be designated as the first member nominee, the second highest shall be designated as the second member nominee until nominees for all producer member positions have been filled. Similarly, the producer alternate member candidate receiving the highest number of votes shall be designated as the first alternate member nominee, the second highest shall be designated as the second alternate member nominee until nominees for all member positions have been filled.
(iii) In the event that there are more producer member nominees than positions to be filled and not enough producer alternate member nominees to fill all positions, producer member nominees not nominated for a member seat may be nominated to fill vacant alternate member seats. Member seat nominees shall indicate, prior to the nomination vote, whether they are willing to accept nomination for an alternate seat in the event they are not nominated for a member seat and there are vacant alternate member seats. Member seat nominees that do not indicate willingness to be considered for vacant alternate member seats shall not be considered.
(iv) Each independent producer or producer affiliated with cooperative marketing association(s) handling less than 10 percent of the total raisin acquisitions during the preceding crop year shall cast only one vote with respect to each position for which nominations are to be made. Write-in candidates shall be accepted. The person receiving the most votes with respect to each position to be filled, in
Any person (defined in § 989.3 as an individual, partnership, corporation, association, or any other business unit) who is engaged, in a proprietary capacity, in the production of grapes which are sun-dried or dehydrated by artificial means to produce raisins and who qualifies under the provisions of § 989.29(b)(2) shall be eligible to cast one ballot for a nominee for each producer member position and one ballot for a nominee for each producer alternate member position on the committee which is to be filled for his district. Such person must be the one who or which: Owns and farms land resulting in his or its ownership of such grapes produced thereon; rents and farms land, resulting in his or its ownership of all or a portion of such grapes produced thereon; or owns land which he or it does not farm and, as rental for such land, obtains the ownership of a portion of such grapes or the raisins. In this connection, a partnership shall be deemed to include two or more persons (including a husband and wife) with respect to land the title to which, or leasehold interest in which, is vested in them as tenants in common, joint tenants, or under community property laws, as community property. In a landlord-tenant relationship, wherein each of the parties is a producer, each such producer shall be entitled to one vote for a nominee for each producer member position and one vote for each producer alternate member position. Hence, where two persons operate land as landlord and tenant on a share-crop basis, each person is entitled to one vote for each such position to be filled. Where land is leased on a cash rental basis, only the person who is the tenant or cash renter (producer) is entitled to vote. A partnership or corporation, when eligible, is entitled to cast only one vote for a nominee for each producer position to be filled in its district.
The revisions read as follows:
(a)
(b)
(d) * * *
(1) Each handler shall cause an inspection and certification to be made of all natural condition raisins acquired or received by him, except with respect to:
(i) An interplant or interhandler transfer of offgrade raisins as described in paragraph (e)(2) of this section, unless such inspection and certification are required by rules and procedures made effective pursuant to this amended subpart;
(ii) An interplant or interhandler transfer of free tonnage raisins as described in § 989.59(e);
(iii) Raisins received from a dehydrator which have been previously inspected pursuant to paragraph (d)(2) of this section;
(iv) Any raisins for which minimum grade, quality, and condition standards are not then in effect;
(v) Raisins received from a cooperative bargaining association which have been inspected and are in compliance with requirements established pursuant to paragraph (d)(3) of this section; and
(vi) Any raisins, if permitted in accordance with such rules and procedures as the committee may establish with the approval of the Secretary, acquired or received for disposition in eligible nonnormal outlets. The handler shall be reimbursed by the committee for inspection costs incurred by him and applicable to pool tonnage held for the account of the committee. Except as otherwise provided in this section, prior to blending raisins, acquiring raisins, storing raisins, reconditioning raisins, or acquiring raisins which have been reconditioned, each handler shall obtain an inspection certification showing whether or not the raisins meet the applicable grade, quality, and condition standards:
(e) * * *
(1) Any natural condition raisins tendered to a handler which fail to meet the applicable minimum grade, quality, and condition standards may:
(i) Be received or acquired by the handler for disposition, without further inspection, in eligible non-normal outlets;
(ii) Be returned unstemmed to the person tendering the raisins; or
(iii) Be received by the handler for reconditioning. Off-grade raisins received by a handler under any one of the three described categories may be changed to any other of the categories under such rules and procedures as the committee, with the approval of the Secretary, shall establish. No handler shall ship or otherwise dispose of off-grade raisins which he does not return to the tenderer, transfer to another handler as provided in paragraph (e)(2) of this section, or recondition so that they at least meet the minimum standards prescribed in or pursuant to this amended subpart, except into eligible non-normal outlets.
(a)
(1) Ship or otherwise make final disposition of natural condition raisins unless they at least meet the effective and applicable minimum grade, quality, and condition standards for natural condition raisins; or
(2) Ship or otherwise make final disposition of packed raisins unless they at least meet such minimum grade, quality, and condition standards established by the committee, with the approval of the Secretary, in applicable rules and regulations or as later changed or prescribed pursuant to the provisions of paragraph (b) of this section:
(b) The committee may recommend changes in the minimum grade, quality, or condition standards for packed raisins of any varietal type and may recommend to the Secretary that minimum grade, quality, or condition standards for any varietal type be added or deleted. The committee shall submit with its recommendation all data and information upon which it acted in making its recommendation, and such other information as the Secretary may request. The Secretary shall approve any such change if he finds, upon the basis of data submitted to him by the committee or from other pertinent information available to him, that to do so would tend to effectuate the declared policy of the act.
(d)
(e)
(g)
The provisions of this part relating to minimum grade, quality, and condition standards and inspection requirements, within the meaning of section 2(3) of the Act, and any other provisions pertaining to the administration and enforcement of the order, shall continue in effect irrespective of whether the estimated season average price to producers for raisins is in excess of the parity level specified in section 2(1) of the act.
(a)
(1) Ship or otherwise make final disposition of natural condition raisins unless they at least meet the effective and applicable minimum grade, quality, and condition standards for natural condition raisins; or
(2) Ship or otherwise make final disposition of packed raisins unless they at least meet such minimum grade, quality, and condition standards established by the committee, with the approval of the Secretary, in applicable rules and regulations or as later changed or prescribed pursuant to the provisions of paragraph (b) of this section:
The addition to read as follows:
(c) No less than two crop years and no later than six crop years after the effective date of this amendment, the Secretary shall conduct a referendum to ascertain whether continuance of this part is favored by producers. Subsequent referenda to ascertain continuance shall be conducted every six crop years thereafter. The Secretary may terminate the provisions of this part at the end of any crop year in which the Secretary has found that continuance of this part is not favored by a two-thirds majority of voting producers, or a two-thirds majority of volume represented thereby, who, during a representative period determined by the Secretary, have been engaged in the production for market of grapes used in the production of raisins in the State of California. Such termination shall be announced on or before the end of the crop year.
Proposals submitted by USDA:
Producer means any person engaged in a proprietary capacity in the production of grapes which are sun-dried or dehydrated by artificial means until they become raisins.
The revisions read as follows:
(a) Each crop year, the Committee shall prepare and submit to the Secretary a report setting forth its recommended marketing policy, including quality regulations for the pending crop. In developing the marketing policy, the Committee may give consideration to the production, harvesting, processing, and storage conditions of that crop, as well as the following factors:
(1) The estimated tonnage held by producers and handlers at the beginning of the crop year;
(4) An estimated desirable carryout at the end of the crop year;
(5) The estimated market demand for raisins, considering the estimated world raisin supply and demand situation;
(c)
(d) * * *
(1) Each handler shall cause an inspection and certification to be made of all natural condition raisins acquired or received by him, except with respect to:
(i) An interplant or interhandler transfer of offgrade raisins as described in paragraph (e)(2) of this section, unless such inspection and certification are required by rules and procedures made effective pursuant to this amended subpart;
(ii) An interplant or interhandler transfer of natural condition raisins as described in § 989.59(e);
(iii) Raisins received from a dehydrator which have been previously inspected pursuant to paragraph (d)(2) of this section;
(iv) Any raisins for which minimum grade, quality, and condition standards are not then in effect;
(v) Raisins received from a cooperative bargaining association which have been inspected and are in compliance with requirements established pursuant to paragraph (d)(3) of this section; and
(vi) Any raisins, if permitted in accordance with such rules and procedures as the committee may establish with the approval of the Secretary, acquired or received for disposition in eligible nonnormal outlets. Except as otherwise provided in this section, prior to blending raisins, acquiring raisins, storing raisins, reconditioning raisins, or acquiring raisins which have been reconditioned, each handler shall obtain an inspection certification showing whether or not the raisins meet the applicable grade, quality, and condition standards:
(e) * * *
(4) If the handler is to acquire the raisins after they are reconditioned, his obligation with respect to such raisins shall be based on the weight of the raisins (if stemmed, adjusted to natural condition weight) after they have been reconditioned.
(e)
(a) Notwithstanding any other provisions of this amended subpart, the committee may establish, with the approval of the Secretary, such rules and procedures as may be necessary to permit the acquisition and disposition of any off-grade raisins, free from any or all regulations, for uses in non-normal outlets.
(b)
(1) The total quantity of standard raisins acquired;
(2) The total quantity of off-grade raisins acquired pursuant to § 989.58(e)(1)(i); and
(3) Cumulative totals of such acquisitions from the beginning of the then current crop year to and including the end of the period for which the report is made. Upon written application made to the committee, a handler may be relieved of submitting such reports after completing his packing operations for the season. Upon request of the committee, each handler shall furnish to the committee, in such manner and at such times as it may require, the name and address of each person from whom he acquired raisins and the quantity of each varietal type of raisins acquired from each such person.
The committee is authorized to incur such expenses as the Secretary finds are reasonable and likely to be incurred by it during each crop year, for the maintenance and functioning of the committee and for such purposes as he may, pursuant to this subpart, determine to be appropriate. The funds to cover such expenses shall be obtained levying assessments as provided in § 989.80. The committee shall file with the Secretary for each crop year a proposed budget of these expenses and a proposal as to the assessment rate to be fixed pursuant to § 989.80, together with a report thereon. Such filing shall be not later than October 5 of the crop year, but this date may be extended by the committee not more than 5 days if warranted by a late crop.
(a) Each handler shall pay to the committee, upon demand, his pro rata share of the expenses which the Secretary finds will be incurred, as aforesaid, by the committee during each crop year less any amounts credited pursuant to § 989.53. Such handler's pro rata share of such expenses shall be equal to the ratio between the total raisin tonnage acquired by such handler during the applicable crop year and the total raisin tonnage acquired by all handlers during the same crop year.
(b) Each handler who reconditions off-grade raisins but does not acquire the standard raisins recovered therefrom shall, with respect to his assessable portion of all such standard raisins, pay to the committee, upon demand, his pro rata share of the expenses which the Secretary finds will be incurred by the committee each crop year. Such handler's pro rata share of such expenses shall be equal to the ratio between the handler's assessable portion (which shall be a quantity equal to such handler's standard raisins which are acquired by some other handler or handlers) during the applicable crop year and the total raisin tonnage acquired by all handlers.
(c) The Secretary shall fix the rate of assessment to be paid by all handlers on the basis of a specified rate per ton. At any time during or after a crop year, the Secretary may increase the rate of assessment to obtain sufficient funds to cover any later finding by the Secretary relative to the expenses of the committee. Each handler shall pay such additional assessment to the committee upon demand. In order to provide funds to carry out the functions of the committee, the committee may accept advance payments from any handler to be credited toward such assessments as may be levied pursuant to this section against such handler during the crop year. The payment of assessments for the maintenance and functioning of the committee, and for such purposes as the Secretary may pursuant to this subpart determine to be appropriate, may be required under this part throughout the period it is in effect, irrespective of whether particular provisions thereof are suspended or become inoperative.
No handler shall dispose of standard raisins, off-grade raisins, or other failing raisins, except in accordance with the provisions of this subpart or pursuant to regulations issued by the committee.
(c) * * *
(4) * * *
(i) The handler shall notify the inspection service at least one business day in advance of the time such handler plans to begin reconditioning each lot of raisins, unless a shorter period is acceptable to the inspection service. Such notification shall be provided verbally or by other means of communication, including email. Natural condition raisins which have been reconditioned shall continue to be considered natural condition raisins for purposes of reinspection (inspection pursuant to § 989.58(d)) after such reconditioning has been completed, if no water or moisture has been added; otherwise, such raisins shall be considered as packed raisins. The weight of the raisins reconditioned successfully shall be determined by reweighing, except where a lot, before reconditioning, failed due to excess moisture only. The weight of such raisins resulting from reconditioning a lot failing account excess moisture may be determined by deducting 1.2 percent of the weight for each percent of moisture in excess of the allowable tolerance. When necessary due to the presence of sand, as determined by the inspection service, the requirement for deducting sand tare and the manner of its determination, as prescribed in paragraph (a)(1) of this section, shall apply in computing the net weight of any such successfully reconditioned natural condition raisins. The weight of the reconditioned raisins acquired as packed raisins shall be adjusted to
The revisions read as follows:
(a)
(b) * * *
(2) * * *
(i) The total net weight of the standard raisins acquired during the reporting period; and
(ii) The cumulative totals of such acquisitions from the beginning of the then current crop year.
(c) * * *
(1) Each month each handler who is not a processor shall furnish to the Committee, on an appropriate form provided by the Committee and so that it is received by the Committee not later than the seventh day of the month, a report showing the aggregate quantity of each varietal type of packed raisins and standard natural condition raisins which were shipped or otherwise disposed of by such handler during the preceding month (exclusive of transfers within the State of California between plants of any such handler and from such handler to other handlers):
(d) * * *
(1) Any handler who transfers raisins to another handler within the State of California shall submit to the Committee not later than five calendar days following such transfer a report showing:
(v) If packed, the transferring handler shall certify that such handler is transferring only acquired raisins that meet all applicable marketing order requirements, including reporting, incoming inspection, and assessments.
(f) * * *
(1) * * *
(i) The quantity of raisins, segregated as to locations where they are stored and whether they are natural condition or packed;
(ii) * * *
(2) * * *
(i) The total net weight of the standard raisins acquired during the reporting period; and
(3) Disposition report of organically-produced raisins. No later than the seventh day of each month, handlers who are not processors shall submit to the Committee, on an appropriate form provided by the Committee, a report showing the aggregate quantity of packed raisins and standard natural condition raisins which were shipped or otherwise disposed of by such handler during the preceding month (exclusive of transfer within the State of California between the plants of any such handler and from such handler to other handlers). Such information shall include:
The revisions read as follows:
(b)
The revisions and addition read as follows:
(a) The term of office of all representatives serving on the Committee shall be for two years and shall end on April 30 of even numbered calendar years;
(b) Representatives may serve up to four consecutive, two-year terms of office. In no event shall any representative serve more than eight consecutive years on the Committee. For purposes of determining when a representative has served four consecutive terms, the accrual of terms shall begin following any period of at least twelve consecutive months out of office. This limitation on tenure shall not include service on the Committee prior to implementation of this amendment.
Make other such changes as may be necessary to the order to conform with any amendment thereto that may result from the hearing.
Federal Aviation Administration (FAA), DOT.
Notice of proposed rulemaking (NPRM).
We propose to adopt a new airworthiness directive (AD) for certain Airbus Helicopters Deutschland GmbH (Airbus Helicopters) Model MBB-BK 117 C-2 helicopters. This proposed AD would require inspecting each terminal lug and replacing any lug that has discoloration, corrosion, incorrect crimping, or incorrect installation. This proposed AD is prompted by the discovery that terminal lugs with incorrect crimping may have been installed on these helicopters. The proposed actions are intended to detect incorrectly installed or crimped terminal lugs and prevent contact resistance and reduced gastightness between the wire and terminal lug, subsequent loss of electrical power, and an electrical fire.
We must receive comments on this proposed AD by June 21, 2016.
You may send comments by any of the following methods:
•
•
•
•
You may examine the AD docket on the Internet at
For service information identified in this proposed rule, contact Airbus Helicopters, 2701 N. Forum Drive, Grand Prairie, TX 75052; telephone (972) 641-0000 or (800) 232-0323; fax (972) 641-3775; or at
George Schwab, Aviation Safety Engineer, Safety Management Group, Rotorcraft Directorate, FAA, 10101 Hillwood Pkwy, Fort Worth, TX 76177; telephone (817) 222-5110; email
We invite you to participate in this rulemaking by submitting written comments, data, or views. We also invite comments relating to the economic, environmental, energy, or federalism impacts that might result from adopting the proposals in this document. The most helpful comments reference a specific portion of the proposal, explain the reason for any recommended change, and include supporting data. To ensure the docket does not contain duplicate comments, commenters should send only one copy of written comments, or if comments are filed electronically, commenters should submit only one time.
We will file in the docket all comments that we receive, as well as a report summarizing each substantive public contact with FAA personnel concerning this proposed rulemaking. Before acting on this proposal, we will consider all comments we receive on or before the closing date for comments. We will consider comments filed after the comment period has closed if it is possible to do so without incurring expense or delay. We may change this proposal in light of the comments we receive.
EASA, which is the Technical Agent for the Member States of the European Union, has issued AD No. 2015-0044, dated March 13, 2015, to correct an unsafe condition for certain serial-numbered Airbus Helicopters Model MBB-BK117 C-2 helicopters. EASA advises that terminal lugs with incorrect crimping may have been installed on some helicopters in production, and that an incorrect crimping die or crimp tool setting may have been used to terminate the lugs. According to EASA, incorrect crimping may adversely affect contact resistance and gastightness of the contact between the wire and the terminal lug. EASA further advises that this condition, if not detected and corrected, could lead to the loss of electrical power during flight. Because of this, the EASA AD requires a one-time visual inspection of the terminal lugs and replacement of affected lugs if incorrect crimping is found.
These helicopters have been approved by the aviation authority of Germany and are approved for operation in the United States. Pursuant to our bilateral agreement with Germany, EASA, its technical representative, has notified us of the unsafe condition described in its AD. We are proposing this AD because we evaluated all known relevant information and determined that an unsafe condition is likely to exist or develop on other products of the same type design.
We reviewed Airbus Helicopters Alert Service Bulletin ASB MBB-BK117 C-2-24A-013, Revision 1, dated November 25, 2014 (ASB). The ASB specifies a visual inspection of the terminal lugs in the distribution and diode boxes for correct crimping, damage, discoloration, corrosion, and correct installation. If any deviation is detected, the terminal lug must be replaced. The ASB also specifies reporting certain information to Airbus Helicopters.
This service information is reasonably available because the interested parties have access to it through their normal course of business or by the means identified in the
This proposed AD would require, within 100 hours time-in-service or 12 months, whichever occurs first, inspecting each terminal lug for discoloration and corrosion, and for correct crimping and correct installation. If a terminal lug is not correctly crimped or installed or if it has any discoloration or corrosion, this proposed AD would require replacing it before further flight.
We estimate that this proposed AD would affect 183 helicopters of U.S. Registry.
We estimate that operators may incur the following costs in order to comply with this AD. Labor costs are estimated at $85 per work-hour. We estimate about 9 work-hours to inspect the terminal lugs for a cost of $765 per helicopter and $139,995 for the U.S. operator fleet. The cost to replace a lug is minimal.
Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. “Subtitle VII: Aviation Programs,” describes in more
We are issuing this rulemaking under the authority described in “Subtitle VII, Part A, Subpart III, Section 44701: General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.
We determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government.
For the reasons discussed, I certify this proposed regulation:
1. Is not a “significant regulatory action” under Executive Order 12866;
2. Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979);
3. Will not affect intrastate aviation in Alaska to the extent that it justifies making a regulatory distinction; and
4. Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.
We prepared an economic evaluation of the estimated costs to comply with this proposed AD and placed it in the AD docket.
Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.
Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows:
49 U.S.C. 106(g), 40113, 44701.
This AD applies to Model MBB-BK 117 C-2 helicopters, certificated in any category, with a serial number as listed in the Planning Information, paragraph 1.A.1, of Airbus Helicopters Alert Service Bulletin ASB MBB-BK117 C-2-24A-013, Revision 1, dated November 25, 2014 (ASB).
This AD defines the unsafe condition as a terminal lug with incorrect crimping. This condition could result in contact resistance and reduced gastightness between the wire and terminal lug and a subsequent loss of electrical power, which could cause an electrical fire.
We must receive comments by June 21, 2016.
You are responsible for performing each action required by this AD within the specified compliance time unless it has already been accomplished prior to that time.
Within 100 hours time-in-service or 12 months, whichever occurs first:
(1) Using a mirror, inspect each terminal lug for discoloration and corrosion, and for correct crimping and correct installation in accordance with the Accomplishment Instructions, Table 1, and the examples in Figure 1 through Figure 5 of the ASB.
(2) If a terminal lug is not correctly crimped or installed or if it has any discoloration or corrosion, replace it before further flight.
(1) The Manager, Safety Management Group, FAA, may approve AMOCs for this AD. Send your proposal to: George Schwab, Aviation Safety Engineer, Safety Management Group, Rotorcraft Directorate, FAA, 10101 Hillwood Pkwy, Fort Worth, TX 76177; telephone (817) 222-5110; email
(2) For operations conducted under a 14 CFR part 119 operating certificate or under 14 CFR part 91, subpart K, we suggest that you notify your principal inspector, or lacking a principal inspector, the manager of the local flight standards district office or certificate holding district office before operating any aircraft complying with this AD through an AMOC.
(1) You may review the referenced service information at the FAA, Office of the Regional Counsel, Southwest Region, 10101 Hillwood Pkwy, Room 6N-321, Fort Worth, TX 76177.
(2) The subject of this AD is addressed in European Aviation Safety Agency (EASA) AD No. 2015-0044, dated March 13, 2015. You may view the EASA AD on the Internet at
Joint Aircraft Service Component (JASC) Code: 24 Electrical Power.
Federal Aviation Administration (FAA), DOT.
Supplemental notice of proposed rulemaking (SNPRM).
This supplemental notice of proposed rulemaking would establish Class E surface area airspace within a 4.2-mile radius of Truckee-Tahoe Airport, Truckee, CA, to increase safety and enhance existing instrument flight rules (IFR) procedures in the immediate vicinity of Truckee-Tahoe Airport, Truckee, CA. In an NPRM published in the
Comments must be received on or before June 6, 2016.
Send comments on this proposal to the U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC 20590; telephone (202) 366-9826. You must identify Docket No. FAA-2015-4074/Airspace Docket No. 15-AWP-16, at the beginning of your comments. You may also submit comments through the Internet at
FAA Order 7400.9Z, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at
FAA Order 7400.9, Airspace Designations and Reporting Points, is published yearly and effective on September 15.
Tom Clark, Federal Aviation Administration, Operations Support Group, Western Service Center, 1601 Lind Avenue SW., Renton, WA 98057; telephone (425) 203-4511.
The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of airspace necessary to ensure the safety of aircraft and the efficient use of airspace. This regulation is within the scope of that authority as it would amend Class E airspace at Truckee-Tahoe Airport, Truckee, CA.
Interested parties are invited to participate in this supplemental proposed rulemaking by submitting such written data, views, or arguments, as they may desire. Comments that provide the factual basis supporting the views and suggestions presented are particularly helpful in developing reasoned regulatory decisions on the proposal. Comments are specifically invited on the overall regulatory, aeronautical, economic, environmental, and energy-related aspects of the proposal.
Communications should identify both docket numbers (Docket No. FAA-2015-4074/Airspace Docket No. 15-AWP-16) and be submitted in triplicate to the Docket Management System (see
Commenters wishing the FAA to acknowledge receipt of their comments on this action must submit with those comments a self-addressed stamped postcard on which the following statement is made: “Comments to Docket No. FAA-2015-4074/Airspace Docket No. 15-AWP-16”. The postcard will be date/time stamped and returned to the commenter.
All communications received on or before the specified closing date for comments will be considered before taking action on the proposed rule. The proposal contained in this action may be changed in light of comments received. All comments submitted will be available for examination in the public docket both before and after the closing date for comments. A report summarizing each substantive public contact with FAA personnel concerned with this rulemaking will be filed in the docket.
An electronic copy of this document may be downloaded through the Internet at
You may review the public docket containing the proposal, any comments received, and any final disposition in person in the Dockets Office (see the
Persons interested in being placed on a mailing list for future NPRMs should contact the FAA's Office of Rulemaking, (202) 267-9677, for a copy of Advisory Circular No. 11-2A, Notice of Proposed Rulemaking Distribution System, which describes the application procedure.
On December 18, 2015, the FAA published in the
The FAA is proposing an amendment to Title 14 Code of Federal Regulations (14 CFR) Part 71 by establishing Class E surface airspace extending upward from the surface within a 4.2-mile radius of Truckee-Tahoe Airport, Truckee, CA. This supplemental proposal adds to the NPRM amending Class E airspace extending upward from 700 feet above the surface, published in the
Class E airspace designated as surface areas are published in paragraph 6002 of FAA Order 7400.9Z, dated August 6, 2015, and effective September 15, 2015, which is incorporated by reference in 14 CFR 71.1. The Class E airspace designations listed in this document will be published subsequently in the Order.
The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current, is non-controversial and unlikely to result in adverse or negative comments. It, therefore: (1) Is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3)
This proposal will be subject to an environmental analysis in accordance with FAA Order 1050.1F, “Environmental Impacts: Policies and Procedures” prior to any FAA final regulatory action.
Airspace, Incorporation by reference, Navigation (air).
Accordingly, pursuant to the authority delegated to me, the Federal Aviation Administration proposes to amend 14 CFR part 71 as follows:
49 U.S.C. 106(f), 106(g); 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.
That airspace extending upward from the surface within a 4.2-mile radius of Truckee-Tahoe Airport.
Federal Aviation Administration (FAA), DOT.
Notice of proposed rulemaking (NPRM).
This action proposes to remove Class E airspace extending upward from 700 feet above the surface at Byerley Airport, Lake Providence, LA. The decommissioning of non-directional radio beacons (NDB) and cancellation of Standard Instrument Approach Procedures (SIAPs) have made this action necessary for continued safety and management within the National Airspace System.
Comments must be received on or before June 6, 2016.
Send comments on this proposal to the U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC 20590; telephone (202) 366-9826. You must identify FAA Docket No. FAA-2016-4236; Airspace Docket No. 16-ASW-5, at the beginning of your comments. You may also submit comments through the Internet at
FAA Order 7400.9Z, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at
FAA Order 7400.9, Airspace Designations and Reporting Points, is published yearly and effective on September 15.
Rebecca Shelby, Federal Aviation Administration, Operations Support Group, Central Service Center, 10101 Hillwood Parkway, Fort Worth, TX 76177; telephone (817) 222-5857.
The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part, A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of airspace necessary to ensure the safety of aircraft and the efficient use of airspace. This regulation is within the scope of that authority as it would remove Class E airspace at Byerley Airport, Lake Providence, LA.
Interested parties are invited to participate in this proposed rulemaking by submitting such written data, views, or arguments, as they may desire. Comments that provide the factual basis supporting the views and suggestions presented are particularly helpful in developing reasoned regulatory decisions on the proposal. Comments are specifically invited on the overall regulatory, aeronautical, economic, environmental, and energy-related aspects of the proposal. Communications should identify both docket numbers and be submitted in triplicate to the address listed above. Commenters wishing the FAA to acknowledge receipt of their comments on this notice must submit with those comments a self-addressed, stamped postcard on which the following statement is made: “Comments to Docket No. FAA-2016-4236/Airspace Docket No. 16-ASW-5.” The postcard will be date/time stamped and returned to the commenter.
An electronic copy of this document may be downloaded through the Internet at
You may review the public docket containing the proposal, any comments received, and any final disposition in person in the Dockets Office (see the
Persons interested in being placed on a mailing list for future NPRMs should contact the FAA's Office of Rulemaking, (202) 267-9677, for a copy of Advisory Circular No. 11-2A, Notice of Proposed Rulemaking Distribution System, which describes the application procedure.
This document proposes to amend FAA Order 7400.9Z, Airspace Designations and Reporting Points, dated August 6, 2015, and effective September 15, 2015. FAA Order 7400.9Z is publicly available as listed in the
The FAA is proposing an amendment to Title 14 Code of Federal Regulations (14 CFR) Part 71 by removing Class E airspace extending upward from 700 feet above the surface within a 6.3 mile radius of Byerley Airport, Lake Providence, LA, and within 2.5 miles each side of the 004° bearing from the Lake Providence RBN extending from the 6.3 mile radius to 7.1 miles north of the airport at Lake Providence, LA. This action is necessary due to the cancellation of Standard Instrument Approach Procedures (SIAPs), and controlled airspace is no longer necessary due to the decommissioning of the NDB and cancellation of the NDB approach at Byerley Airport, Lake Providence, LA.
Class E airspace designations are published in paragraph 6005 of FAA Order 7400.9Z, dated August 6, 2015, and effective September 15, 2015, which is incorporated by reference in 14 CFR 71.1. The Class E airspace designations listed in this document will be published subsequently in the Order.
The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current, is non-controversial and unlikely to result in adverse or negative comments. It, therefore: (1) Is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that will only affect air traffic procedures and air navigation, it is certified that this rule, when promulgated, would not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.
This proposal will be subject to an environmental analysis in accordance with FAA Order 1050.1F, “Environmental Impacts: Policies and Procedures” prior to any FAA final regulatory action.
Airspace, Incorporation by reference, Navigation (air).
Accordingly, pursuant to the authority delegated to me, the Federal Aviation Administration proposes to amend 14 CFR part 71 as follows:
49 U.S.C. 106(f), 106(g); 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.
Food and Drug Administration, HHS.
Notification of rescheduling of public hearing; request for comments.
The Food and Drug Administration (FDA or Agency) is announcing a 2-day public hearing to obtain input on four draft guidance documents relating to the regulation of human cells, tissues, and cellular and tissue-based products (HCT/Ps). FDA had announced a 1-day public hearing for April 13, 2016, to obtain input on the guidances, but on February 29, 2016, announced that due to considerable interest in the public hearing and to give stakeholders additional time to provide comments to the Agency, the hearing was postponed. FDA also stated its intent to extend the comment period for the four draft guidance documents and to schedule a scientific workshop to identify and discuss the scientific considerations and challenges to help inform the development of HCT/Ps subject to premarket approval, including stem cell-based products. FDA will consider information it obtains from the public hearing in the finalization of the four draft guidance documents.
The public hearing will be held on September 12 and 13, 2016, from 9 a.m. to 5 p.m. The hearing on September 13 may be extended or end early depending on the number of speakers scheduled. Persons (including FDA employees) seeking to view the hearing via a live Webcast are not required to register. Persons (including FDA employees) seeking to attend in person or to attend and speak at the public hearing must register by June 1, 2016.
The public hearing will be held at the National Institutes of Health (NIH), 9000 Rockville Pike, Bldg. 10, Masur Auditorium, Bethesda, MD 20892. Entrance for the public hearing attendees and speakers (non-FDA employees) is through Bldg. 66 (Gateway Center), where routine security check procedures will be performed. For parking and security information, please refer to
You may submit comments as follows:
Submit electronic comments in the following way:
•
• If you want to submit a comment with confidential information that you do not wish to be made available to the public, submit the comment as a written/paper submission and in the manner detailed (see “Written/Paper Submissions” and “Instructions”).
Submit written/paper submissions as follows:
•
• For written/paper comments submitted to the Division of Dockets Management, FDA will post your comment, as well as any attachments, except for information submitted, marked and identified, as confidential, if submitted as detailed in “Instructions.”
• Confidential Submissions—To submit a comment with confidential information that you do not wish to be made publicly available submit your comments only as a written/paper submission. You should submit two copies total. One copy will include the information you claim to be confidential with a heading or cover note that states “THIS DOCUMENT CONTAINS CONFIDENTIAL INFORMATION.” The Agency will review this copy, including the claimed confidential information, in its consideration of comments. The second copy, which will have the claimed confidential information redacted/blacked out, will be available for public viewing and posted on
A link to the live Webcast of this public hearing will be available at
Lori Jo Churchyard, Center for Biologics Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 71, Rm. 7301, Silver Spring, MD 20993, 240-402-7911,
HCT/Ps are defined in § 1271.3(d) (21 CFR 1271.3(d)) as articles containing or consisting of human cells or tissues that are intended for implantation, transplantation, infusion, or transfer into a human recipient. FDA has implemented a risk-based approach to the regulation of HCT/Ps. Under the authority of section 361 of the Public Health Service (PHS) Act (42 U.S.C. 264), FDA established regulations for all HCT/Ps to prevent the introduction, transmission, and spread of communicable diseases. These regulations can be found in part 1271. HCT/Ps are regulated solely under section 361 of the PHS Act and part 1271, if they meet all of the following criteria (§ 1271.10(a)):
• The HCT/P is minimally manipulated;
• The HCT/P is intended for homologous use, as reflected by the labeling, advertising, or other indications of the manufacturer's objective intent;
• The manufacture of the HCT/P does not involve the combination of the cells or tissues with another article, except for water, crystalloids, or a sterilizing, preserving or storage agent, provided that the addition of water, crystalloids, or the sterilizing, preserving, or storage
• Either
○ The HCT/P does not have a systemic effect and is not dependent upon the metabolic activity of living cells for its primary function, or
○ The HCT/P has a systemic effect or is dependent upon the metabolic activity of living cells for its primary function, and is for the following uses:
Autologous,
Allogeneic, in a first-degree or second-degree blood relative, or
Reproductive.
If an HCT/P does not meet all of the criterial set forth under § 1271.10(a), the HCT/P will be regulated as a drug, device, and/or biological product under the Federal Food, Drug, and Cosmetic Act, and/or section 351 of the PHS Act (42 U.S.C. 262).
In certain circumstances as provided in § 1271.15, an establishment may not be required to comply with some or all of the requirements in part 1271. For example, an establishment is excepted from the requirements in part 1271 if it “removes HCT/P's from an individual and implants such HCT/P's into the same individual during the same surgical procedure” (§ 1271.15(b)).
As part of its commitment to public outreach and to explain the Agency's current thinking on the regulatory framework for HCT/Ps, FDA has issued the following four draft guidances:
• Same Surgical Procedure Exception under 21 CFR 1271.15(b): Questions and Answers Regarding the Scope of the Exception; Draft Guidance for Industry (Same Surgical Procedure Exception Draft Guidance);
• Minimal Manipulation of Human Cells, Tissues, and Cellular and Tissue-Based Products; Draft Guidance for Industry and Food and Drug Administration Staff (Minimal Manipulation Draft Guidance);
• Human Cells, Tissues, and Cellular and Tissue-Based Products (HCT/Ps) from Adipose Tissue: Regulatory Considerations; Draft Guidance for Industry (Adipose Tissue Draft Guidance); and
• Homologous Use of Human Cells, Tissues, and Cellular and Tissue-Based Products; Draft Guidance for Industry and FDA Staff (Homologous Use Draft Guidance).
The Same Surgical Procedure Exception Draft Guidance was announced in the
The Minimal Manipulation Draft Guidance was announced in the
The Adipose Tissue Draft Guidance was announced in the
The Homologous Use Draft Guidance was announced in the
In the
On February 29, 2016, FDA postponed the public hearing to give stakeholders additional time to provide comments to the Agency. FDA also stated its intent to extend the comment period for the four draft guidance documents and to schedule a scientific workshop to identify and discuss the scientific considerations and challenges to help inform the development of HCT/Ps subject to premarket approval, including stem cell-based products.
Elsewhere in this issue of the
The purpose of this public hearing is to obtain comments on the four draft guidances. FDA is seeking feedback on the four draft guidances, both general and specific, from a broad group of stakeholders, including tissue establishments, biological and device product manufacturers, health care professionals, clinicians, biomedical researchers, and the public. For example, FDA would like comments on the scope of the four draft guidances, including the particular topics covered, the particular questions posed, whether there are additional issues for which guidance would be helpful, and whether FDA's recommendations for each topic are sufficiently clear and consistent within and across documents to provide meaningful guidance to stakeholders. In addition, FDA welcomes comments that will enhance the usefulness and clarity of these documents.
FDA recommends that comments exclude discussion of products that do not meet the definition of an HCT/P, such as platelet-rich plasma and other blood products. FDA also recommends that stakeholders coordinate comments when possible, in order to allow for presentation of a wide range of perspectives within the allotted time of the hearing.
The NIH campus is a Federal facility with security procedures and limited seating. Attendance is free.
Persons (including FDA employees) seeking to view the hearing via a live Webcast are not required to register.
Persons (including FDA employees) who wish to attend in person, but not speak at the public hearing, must register at
Persons (including FDA employees) who wish to attend and speak at the
FDA will do its best to accommodate requests to speak at the public hearing and will determine the amount of time allotted for each oral presentation, and the approximate time that each oral presentation will be scheduled to begin. Multiple speakers from the same organization will be given one presentation slot for that organization. If the number of persons or organizations requesting to speak is greater than can be reasonably accommodated, FDA will close registration for speakers. FDA will notify registered speakers of their scheduled times, and make available an agenda at
If you need special accommodations because of a disability, please contact Sherri Revell or Loni Warren Henderson at 240-402-8010 at least 7 days before the hearing.
A link to the live Webcast of this public hearing will be available at
The Commissioner of Food and Drugs is announcing that the public hearing will be held in accordance with part 15 (21 CFR part 15). The hearing will be conducted by a presiding officer, who will be accompanied by FDA senior management from the Office of the Commissioner and the Center for Biologics Evaluation and Research.
Under § 15.30(f), the hearing is informal and the rules of evidence do not apply. No participant may interrupt the presentation of another participant. Only the presiding officer and panel members may question any person during or at the conclusion of each presentation. Public hearings under part 15 are subject to FDA's policy and procedures for electronic media coverage of FDA's public administrative proceedings (21 CFR part 10, subpart C). Under § 10.205, representatives of the electronic media may be permitted, subject to certain limitations, to videotape, film, or otherwise record FDA's public administrative proceedings, including presentations by participants. The hearing will be transcribed as stipulated in § 15.30(b) (see section VI of this document). To the extent that the conditions for the hearing, as described in this notice, conflict with any provisions set out in part 15, this notice acts as a waiver of those provisions as specified in § 15.30(h).
Please be advised that as soon as a transcript is available, it will be accessible at
Food and Drug Administration, HHS.
Notification; extension of comment periods.
The Food and Drug Administration (FDA or the Agency) is extending the comment period for the draft guidance documents entitled “Same Surgical Procedure Exception: Questions and Answers Regarding the Scope of the Exception; Draft Guidance for Industry”; “Minimal Manipulation of Human Cells, Tissues, and Cellular and Tissue-Based Products; Draft Guidance for Industry and Food and Drug Administration Staff”; “Human Cells, Tissues, and Cellular and Tissue-Based Products from Adipose Tissue: Regulatory Considerations; Draft Guidance for Industry”; and ”Homologous Use of Human Cells, Tissues, and Cellular and Tissue-Based Products; Draft Guidance for Industry and FDA Staff.” The Agency is taking this action to allow interested persons additional time to submit comments and any new information.
FDA is extending the comment period on the four draft guidances announced in the
You may submit comments as follows:
Submit electronic comments in the following way:
•
• If you want to submit a comment with confidential information that you do not wish to be made available to the public, submit the comment as a written/paper submission and in the manner detailed (see “Written/Paper Submissions” and “Instructions”).
Submit written/paper submissions as follows:
•
• For written/paper comments submitted to the Division of Dockets Management, FDA will post your comment, as well as any attachments, except for information submitted, marked and identified, as confidential, if submitted as detailed in “Instructions.”
• Confidential Submissions—To submit a comment with confidential information that you do not wish to be made publicly available, submit your comments only as a written/paper submission. You should submit two copies total. One copy will include the information you claim to be confidential with a heading or cover note that states “THIS DOCUMENT CONTAINS CONFIDENTIAL INFORMATION.” The Agency will review this copy, including the claimed confidential information, in its consideration of comments. The second copy, which will have the claimed confidential information redacted/blacked out, will be available for public viewing and posted on
Lori Jo Churchyard, Center for Biologics Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 71, Rm. 7301, Silver Spring, MD 20993, 240-402-7911,
In the
In the
In the
Following publication of these three notices of availability, FDA received requests to allow interested persons additional time to comment.
In the
In the
The draft guidances on same surgical procedure, minimal manipulation, adipose tissue, and homologous use provide recommendations for complying with the regulatory framework for human cells, tissues, and cellular and tissue based products under 21 CFR part 1271 that were to be discussed during the part 15 (21 CFR part 15) hearing. In conjunction with the part 15 hearing and announcement of availability of the homologous use draft guidance, in the
Elsewhere in this issue of the
Environmental Protection Agency.
Proposed rule.
The Environmental Protection Agency (EPA) is proposing to approve a portion of a State Implementation Plan (SIP) revision submitted by the State of Tennessee, submitted on March 14, 2014, through the Tennessee Department of Environmental Conservation on behalf of the Knox County Department of Air Quality Management (Knox County) to address changes to a Knox County regulation regarding permits. EPA is proposing to approve this SIP revision because the State has demonstrated that it is consistent with the Clean Air Act.
Written comments must be received on or before May 23, 2016.
Submit your comments, identified by Docket ID No. EPA-R04-OAR-2015-0618 at
Zuri Farngalo or D. Brad Akers, Air Regulatory Management Section, Air Planning and Implementation Branch, Air, Pesticides and Toxics Management Division, U.S. Environmental Protection Agency, Region 4, 61 Forsyth Street SW., Atlanta, Georgia 30303-8960. Mr. Farngalo can be reached at (404) 562-9152 and via electronic mail at
In the Rules and Regulations section of this issue of the
Bureau of Land Management, Interior.
Proposed rule; extension of public comment period.
On February 25, 2016, the Bureau of Land Management (BLM) published in the
Send your comments on this proposed rule to the BLM on or before May 25, 2016. The BLM need not consider, or include in the administrative record for the final rule, comments that the BLM receives after the close of the comment period or comments delivered to an address other than those listed below (see
Leah Baker, Division Chief, Decision Support, Planning and NEPA, at 202-912-7282, for information relating to the BLM's national planning program or the substance of this proposed rule. For information on procedural matters or the rulemaking process, you may contact Charles Yudson at 202-912-7437. Persons who use a telecommunications device for the deaf (TDD) may call the Federal Information Relay Service (FIRS) at 1-800-877-8339 to contact the above individuals during normal business hours. FIRS is available 24 hours a day, 7 days a week to leave a message or question with the above individuals. You will receive a reply during normal business hours.
If you wish to comment, you may submit your comments by any one of several methods listed in the
1. Those supported by quantitative information or studies; and
2. Those that include citations to, and analyses of, the applicable laws and regulations.
The BLM is not obligated to consider or include in the Administrative Record for the rule comments received after the close of the comment period (see
Comments, including names and street addresses of respondents, will be available for public review at the address listed under
Before including your address, telephone number, email address, or other personal identifying information in your comment, be advised that your entire comment—including your personal identifying information—may be made publicly available at any time. While you can ask in your comment to withhold from public review your personal identifying information, we cannot guarantee that we will be able to do so.
The proposed rule was published on February 25, 2016 (81 FR 9674), with a 60-day comment period closing on April 25, 2016. Since publication, the BLM has received requests to extend the comment period on the proposed rule. After considering these requests, the BLM determined that it is appropriate to grant the requests to extend the comment period, and the BLM is hereby extending the comment period on the rule for 30 days. The closing date of the extended comment period is May 25, 2016.
National Aeronautics and Space Administration.
Proposed rule.
NASA is proposing to amend the NASA Federal Acquisition Regulation Supplement (NFS) to clarify NASA's award fee process by incorporating terms used in award fee contracting; guidance relative to final award fee evaluations; release of source selection information; and the calculation of the provisional award fee payment percentage in NASA end-item award fee contracts.
Comments on the proposed rule should be submitted in writing to the address shown below on or before June 21, 2016, to be considered in the formation of a final rule.
Submit comments identified by NFS Case 2016-N008, using any of the following methods:
○
○
○
○
Mr. William Roets, NASA HQ, Office of Procurement, Contract and Grant Policy Division, Suite 5M18, 300 E Street SW., Washington, DC 20456-0001. Telephone 202-358-4483; facsimile 202-358-3082.
NASA is proposing to revise the NFS to clarify NASA's award fee process. As part of the NASA Office of Procurement internal reviews and the NASA Office of the Inspector General (OIG) audit entitled “NASA's Use of Award Fee Contracts,” Report Number IG-14-003, NASA is implementing revisions to NFS 1816.4 and 1852.216-77 to clarify NASA's award fee evaluation and payment processes.
NASA is proposing the following revisions to clarify NASA's award fee process:
• Add new definitions section at NFS 1816.001. Definitions for Earned Award Fee and Unearned Award Fee are being added to provide clarity and consistency in how these terms are utilized in NASA's award fee evaluation process.
• Revise NFS 1816.405-273(b) to provide further management review for final award fee determinations that meet certain criteria as outlined in this rule's revised NFS text.
• Revise NFS 1816.405-273(c) to provide clarification regarding the release of source selection information that is included in the Contractor Performance Assessment Reporting System (CPARS).
• Revise NFS 1816.405-276(b) and 1852.216-77(c)(3) to clarify how provisional award fee payments are calculated in NASA end-item award fee contracts. The current NFS text describes this calculation as “limited to a percentage not to exceed 80 percent of the prior interim period's evaluation score” and yet does not address how the first award fee evaluation period should be handled. To address this issue, NFS is being revised to read: “limited to a percentage not to exceed 80 percent of the prior interim period's evaluation score, except for the first evaluation period, which is limited to 80 percent of the available award fee for that evaluation period.”
• In addition, since the FAR removed clause 52.216-13 in Federal Acquisition Circular (FAC) 2005-17, NASA is removing references to this clause contained in NFS 1816.307, 1816.307-70, and 1852.216-89.
Executive Orders (E.O.s) 12866 and 13563 direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). E.O. 13563 emphasizes the importance of quantifying both costs
NASA does not expect this rule to have a significant economic impact on a substantial number of small entities within the meaning of the Regulatory Flexibility Act, 5 U.S.C. 601,
An analysis of data in the Federal Procurement Data System (FPDS) revealed that award fee contracts are primarily awarded to large businesses with large dollar contracts. An analysis of FPDS data over the past three years (Fiscal Year (FY)2013 through FY2015) showed that an average of 157 award fee contracts were awarded at NASA per year, of which 33 (approximately 20%) were awarded to small businesses. Thus, the application of the award fee revisions contained in this rule do not apply to a substantial number of small entities.
The rule imposes no reporting, recordkeeping, or other information collection requirements. The rule does not duplicate, overlap, or conflict with any other Federal rules, and there are no known significant alternatives to the rule.
NASA invites comments from small business concerns and other interested parties on the expected impact of this rule on small entities.
NASA will also consider comments from small entities concerning the existing regulations in subparts affected by this rule in accordance with 5 U.S.C. 610. Interested parties shall submit such comments separately and should cite 5 U.S.C. 610 (NFS Case 2016-N008), in correspondence.
The rule does not contain any information collection requirements that require the approval of the Office of Management and Budget under the Paperwork Reduction Act (44 U.S.C. chapter 35).
Government procurement.
Accordingly, 48 CFR parts 1816 and 1852 are proposed to be amended as follows:
51 U.S.C. 20113(a) and 48 CFR chapter 1.
As used in this part—
(f) When FAR clause 52.216-7, Allowable Cost and Payment, is included in the contract, as prescribed at FAR 16.307(a), the contracting officer should include the clause at 1852.216-89, Assignment and Release Forms.
(b)
(c)
(b) * * * For an end item contract, the total amount of provisional payments in a period is limited to a percentage not to exceed 80 percent of the prior interim period's evaluation score, except for the first evaluation period which is limited to 80 percent of the available award fee for that evaluation period.
Award Fee for End Item Contracts (Date)
(c)(1) * * *
(3) Provisional award fee payments will [insert “not” if applicable] be made under this contract pending each interim evaluation. If applicable, provisional award fee payments will be made to the Contractor on a [
The Contractor shall use the following forms to fulfill the assignment and release requirements of FAR clause 52.216-7, Allowable Cost and Payment:
National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.
Proposed rule; request for comments.
NMFS proposes regulations under the Tuna Conventions Act to implement Resolution C-15-04 (
Comments on the proposed rule and supporting documents must be submitted in writing by May 23, 2016.
You may submit comments on this document, identified by NOAA-NMFS-2016-0035, by any of the following methods:
•
•
Copies of the draft Regulatory Impact Review and other supporting documents are available via the Federal eRulemaking Portal:
Rachael Wadsworth, NMFS, West Coast Region, 562-980-4036.
The United States is a member of the IATTC, which was established under the 1949 Convention for the Establishment of an Inter-American Tropical Tuna Commission. In 2003, the IATTC adopted the Convention for the Strengthening of the IATTC Established by the 1949 Convention between the United States of America and the Republic of Costa Rica (Antigua Convention). The Antigua Convention entered into force in 2010. The United States acceded to the Antigua Convention on February 24, 2016. The full text of the Antigua Convention is available at:
The IATTC consists of 21 member nations and four cooperating non-member nations and facilitates scientific research into, as well as the conservation and management of, tuna and tuna-like species in the IATTC Convention Area. The IATTC Convention Area is defined as waters of
As a Party to the Antigua Convention and a member of the IATTC, the United States is legally bound to implement certain decisions of the IATTC. The Tuna Conventions Act (16 U.S.C. 951
The IATTC adopted Resolution C-15-04 at its 89th meeting in July 2015 in response to the IATTC scientific staff's conservation recommendations related to requirements for release of mobulid rays and concern for the mortality of mobulid rays caught in the IATTC Convention Area. The main objective of Resolution C-15-04 is to promote conservation of mobulid rays by reducing incidental catch mortalities in IATTC fisheries in the EPO.
U.S. commercial fishing vessels in the EPO do not target mobulid rays or commonly catch mobulid rays incidentally. Five species of mobulid rays are typically caught in the EPO: The giant manta ray (
The Resolution calls for IATTC members and cooperating non-members (CPCs) to prohibit any part or whole carcass of mobulid rays (
The Resolution also requires that any mobulid ray (whether live or dead) caught in the IATTC Convention Area be promptly released unharmed, to the extent practicable, as soon as it is seen in the net, on the hook, or on the deck, without compromising the safety of any persons. Per the Resolution, the requirements for release include prohibitions on the gaffing of mobulid rays, the lifting of mobulid rays by the gill slits or spiracles, and the punching of holes through the bodies of mobulid rays (
The Resolution requires the number of discards and releases of mobulid rays, indicating the status (dead or alive) to be recorded, through observer programs. Any mobulid ray disposed of, at the direction of the responsible governmental authority, must also be recorded. Observers on U.S. commercial fishing vessels for drift gillnet and longline gear in the IATTC Convention Area already record the catch and release status of mobulid rays. However, observers on purse seine vessels have only been recording the release of dead mobulid rays and will now be required to record the release of live mobulid rays.
The requirements of the Resolution do not apply to small-scale and artisanal fisheries that fish exclusively for domestic consumption and are flagged/registered by a developing CPC. Because the United States is not a developing nation, this exclusion need not be implemented in U.S. regulations.
This proposed rule would implement Resolution C-15-04, described above, for U.S. commercial fishing vessels used in the IATTC Convention Area. First, the proposed rule would prohibit any part or whole carcass of a mobulid ray caught by vessels owners or operators in the IATTC Convention Area from being retained on board, transshipped, landed, stored, sold, or offered for sale. Second, the proposed rule would require that the crew, operator, and owner of a U.S. commercial fishing vessel must promptly release unharmed, to the extent practicable, any mobulid ray (whether live or dead) caught in the IATTC Convention Area as soon as it is seen in the net, on the hook, or on the deck, without compromising the safety of any persons. If a mobulid ray is live
Third, the proposed rule would provide an exemption in the case of any mobulid ray caught in the IATTC Convention Area on an observed purse seine vessel that is not seen during fishing operations and is delivered into the vessel hold. In this circumstance, the mobulid ray may be stored on board and landed, but the vessel owner or operator must show the whole mobulid ray to the observer at the point of landing, and then dispose of the mobulid ray at the direction of the responsible government authority. In U.S. ports the responsible governmental authority is NOAA Office of Law Enforcement, Western Division or Pacific Islands Division, or other authorized personnel. Mobulid rays that are caught and landed in this manner may not be sold or bartered, but may be donated for purposes of domestic human consumption consistent with relevant laws and policies. NMFS is soliciting public comment on other possible methods of use for mobulid rays, including donation for scientific purposes or discard.
In addition, this proposed rule would also revise related codified text for consistency with the recent amendments to the Tuna Conventions Act (16 U.S.C. 951
The NMFS Assistant Administrator has determined that this proposed rule is consistent with the Tuna Conventions Act and other applicable laws, subject to further consideration after public comment.
This proposed rule has been determined to be not significant for purposes of Executive Order 12866.
There are no new collection-of-information requirements associated with this action that are subject to the Paperwork Reduction Act (PRA), and existing collection-of-information requirements still apply under the following Control Numbers: 0648-0148, 0648-0214, and 0648-0593. Notwithstanding any other provision of the law, no person is required to respond to, and no person shall be subject to penalty for failure to comply with, a collection-of-information subject to the requirements of the PRA, unless that collection-of-information displays a currently valid Office of Management and Budget control number.
Pursuant to the Regulatory Flexibility Act, 5 U.S.C. 605(b), the Chief Counsel for Regulation of the Department of Commerce certified to the Chief Counsel for Advocacy of the Small Business Administration that this proposed rule, if adopted, would not have a significant economic impact on a substantial number of small entities. The rationale for the certification is provided in the following paragraphs.
As described previously in the
On June 12, 2014, the Small Business Administration issued an interim final rule revising the small business size standards for several industries effective July 14, 2014 (79 FR 33467). The rule increased the size standard for Finfish Fishing from $19.0 million to $20.5 million, Shellfish Fishing from $5.0 million to $5.5 million, and Other Marine Fishing from $7.0 million to $7.5 million. NMFS conducted its analysis for this action in light of the new size standards. NMFS considers all entities subject to this action to be small entities as defined by both the former, lower size standards and the revised size standards. The small entities that would be affected by the proposed action are all U.S. commercial fishing vessels that may be used for IATTC fisheries in the IATTC Convention Area (
There are two components to the U.S. tuna purse seine fishery in the EPO: (1) Purse seine vessels with at least 363 metric tons (mt) of fish hold volume (size class 6 vessels) that typically have been based in the western and central Pacific Ocean (WCPO), and (2) coastal purse seine vessels with smaller fish hold volume that are based on the U.S. West Coast. As of March 10, 2016, there are 15 size class 6 purse seine vessels on the IATTC Regional Vessel Register. The number of size class 6 purse seine vessels on the IATTC Regional Vessel Register has increased substantially in the past two years, due in part to uncertainty regarding fishing access pursuant to the Treaty on Fisheries between the Governments of Certain Pacific Island States and the Government of the United States of America (aka the South Pacific Tuna Treaty). In recent years, size class 6 purse seine vessels have landed most of the yellowfin, skipjack, and bigeye tuna catch in the EPO. Estimates of ex-vessel revenues for size class 6 purse seine vessels in the IATTC Convention Area since 2005 are confidential and may not be publicly disclosed because of the small number of vessels in the fishery. Since 2010, fewer than three coastal purse seine vessels targeted tunas; therefore, their landings and revenue are confidential. In 2014, eight coastal purse seine vessels landed 1,413 mt of tuna (ex-vessel value of about $1,535,000) in west coast ports.
Participation in the large-mesh DGN fishery has declined significantly over the years, from 78 vessels in 2000 to 18 in 2013. The large-mesh DGN fishery primarily targets swordfish and to a lesser extent common thresher shark. During 2003 to 2014, the average ex-vessel value of the landings by the large
U.S. West Coast vessels with deep-set longline gear primarily target tuna species with a small percentage of swordfish and other highly migratory species taken incidentally. U.S. West Coast-based longline vessels fish primarily in the EPO and are currently restricted to fishing with deep-set longline gear outside of the U.S. West Coast EEZ. Given this restriction, there has been fewer than three west coast-based vessels operating out of southern California ports since 2005; therefore, landings and ex-vessel revenue are confidential. Recently, the number of Hawaii-permitted longline vessels that have landed in west coast ports has increased from one vessel in 2006 to 14 vessels in 2014. In 2014, 621 mt of highly migratory species were landed by Hawaii permitted longline vessels with an average ex-vessel revenue of approximately $247,857 per vessel.
The available logbook data from 2005 to 2014 does not show a record of mobulid rays caught in fisheries without observers. In fisheries with observers only a few interactions have been recorded over that same time frame. Since at least 2005, the observer coverage rates on class size 6 vessels, large mesh DGN vessels, and deep-set longline vessels in the EPO have been a minimum of 100, 20, and 20 percent, respectfully. In addition, since 2005 the following interactions have been recorded on vessels with observers: three mobulid rays were caught on size class 6 purse seine vessels, all of which were discarded dead because the observers do not record the discard of mobulid rays that are alive when released; two
The proposed action is not expected to have a significant economic impact on a substantial number of small entities. This action is not expected to change the typical fishing practices of affected vessels or the income of U.S. vessels because these vessels do not target mobulid rays, and do not commonly catch mobulid rays, even incidentally. In those rare situations when vessels owners and operators do catch mobulid rays, there would be some additional time burden for releasing them by implementing the release requirements. NMFS considers all entities subject to this action to be small entities as defined by both the former, lower size standards and the revised size standards. Because each affected vessel is a small business, this proposed action is considered to equally affect all of these small entities in the same manner. This action is not likely to increase the economic or record keeping and reporting burden on U.S. vessel owners and operators. Accordingly, vessel income is not expected to be altered as a result of this rule. As a result, an Initial Regulatory Flexibility Analysis is not required, and was not prepared for this proposed rule.
Fish, Fisheries, Fishing, Fishing vessels, International organizations, Marine resources, Reporting and recordkeeping requirements, Treaties.
For the reasons set out in the preamble, 50 CFR part 300 is proposed to be amended as follows:
16 U.S.C. 951
The regulations in this subpart are issued under the authority of the Tuna Conventions Act of 1950, as amended, (Act) and apply to persons and vessels subject to the jurisdiction of the United States. The regulations implement recommendations and other decisions of the Inter-American Tropical Tuna Commission (IATTC) for the conservation and management of stocks of tunas and tuna-like species and other species of fish taken by vessels fishing for tunas and tuna-like species in the IATTC Convention Area.
In addition to the terms defined in § 300.2, the Act, and the Convention for the Strengthening of the Inter-American Tropical Tuna Commission Established by the 1949 Convention between the United States of America and the Republic of Costa Rica (Antigua Convention), the terms used in this subpart have the following meanings. If a term is defined differently in § 300.2, in the Act, or in the Antigua Convention, the definition in this section shall apply.
(e) Fail to retain any bigeye, skipjack, or yellowfin tuna caught by a fishing vessel of the United States of class size 4-6 using purse seine gear in the Convention Area as required under § 300.27(a).
(f) When using purse seine gear to fish for tuna in the Convention Area, fail to release any non-tuna species as soon as practicable after being identified on board the vessel during the brailing operation as required in § 300.27(b).
(h) Fail to use the sea turtle handling, release, and resuscitation procedures in § 300.27(c).
(t) Use a U.S. fishing vessel to fish for HMS in the Convention Area and retain on board, transship, land, store, sell, or offer for sale any part or whole carcass of an oceanic whitetip shark (
(w) Set or attempt to set a purse seine on or around a whale shark (
(x) Fail to release a whale shark encircled in a purse seine net of a fishing vessel as required in § 300.27(f).
(cc) To retain on board, transship, store, land, sell, or offer for sale any part or whole carcass of a mobulid ray, as described in § 300.27(g).
(dd) Fail to handle or release a mobulid ray as required in § 300.27(h).
(a)
(a)
(b)
(c)
(1) Whenever a sea turtle is sighted in the net, a speedboat shall be stationed close to the point where the net is lifted out of the water to assist in release of the sea turtle;
(2) If a sea turtle is entangled in the net, net roll shall stop as soon as the sea turtle comes out of the water and shall not resume until the sea turtle has been disentangled and released;
(3) If, in spite of the measures taken under paragraphs (c)(1) and (2) of this section, a sea turtle is accidentally brought on board the vessel alive and active, the vessel's engine shall be disengaged and the sea turtle shall be released as quickly as practicable;
(4) If a sea turtle brought on board under paragraph (c)(3) of this section is alive but comatose or inactive, the resuscitation procedures described in § 223.206(d)(1)(i)(B) of this title shall be used before release of the turtle.
(d)
(e)
(f)
(g)
(h)
(1) No mobulid ray may be gaffed, no mobulid ray may be lifted by the gill slits or spiracles or by using bind wire against or inserted through the body, and no holes may be punched through the bodies of mobulid ray (
(2) Applicable to purse seine operations, large mobulid rays must be brailed out of the net by directly releasing the mobulid ray from the brailer into the ocean. Large mobulid rays that cannot be released without compromising the safety of persons or the mobulid ray before being landed on deck, must be returned to the water as soon as possible, either utilizing a ramp from the deck connecting to an opening on the side of the boat, or lowered with a sling or net, using a crane if available. The minimum size for the sling or net must be at least 25 feet in diameter.
Forest Service, USDA.
Notice of meeting.
The Fishlake Resource Advisory Committee (RAC) will meet in Richfield, Utah. The committee is authorized under the Secure Rural Schools and Community Self-Determination Act (the Act) and operates in compliance with the Federal Advisory Committee Act. The purpose of the committee is to improve collaborative relationships and to provide advice and recommendations to the Forest Service concerning projects and funding consistent with Title II of the Act. RAC information can be found at the following Web site:
The meeting will be held May 18, 2016 at 6 p.m. (MDT).
All RAC meetings are subject to cancellation. For status of meeting prior to attendance, please contact the person listed under
The meeting will be held at the Fishlake National Forest Supervisor's Office, 115 E 900 N, Richfield, Utah.
Written comments may be submitted as described under
John Zapell, RAC Coordinator by phone at (435) 896-1070 or via email at
Individuals who use telecommunication devices for the deaf (TDD) may call the Federal Information Relay Service (FIRS) at 1-800-877-8339 between 8:00 a.m. and 8:00 p.m., Eastern Standard Time, Monday through Friday.
The purpose of the meeting is to:
1. Review, prioroitze and recommend projects for funding.
The meeting is open to the public. The agenda will include time for people to make oral statements of three minutes or less. Individuals wishing to make an oral statement should request in writing by May 6, 2016 to be scheduled on the agenda. Anyone who would like to bring related matters to the attention of the committee may file written statements with the committee staff before or after the meeting. Written comments and requests for time to make oral comments must be sent to John Zapell, Designated Federal Officer, 115 E. 900 N., Richfield, Utah 84701; or by email to
Forest Service, USDA.
Notice of meeting.
The Fishlake Resource Advisory Committee (RAC) will meet in Richfield, Utah. The committee is authorized under the Secure Rural Schools and Community Self-Determination Act (the Act) and operates in compliance with the Federal Advisory Committee Act. The purpose of the committee is to improve collaborative relationships and to provide advice and recommendations to the Forest Service concerning projects and funding consistent with Title II of the Act. RAC information can be found at the following Web site:
The meeting will be held May 11, 2016 at 6 p.m. (MDT).
All RAC meetings are subject to cancellation. For status of meeting prior to attendance, please contact the person listed under
The meeting will be held at the Fishlake National Forest Supervisor's Office, 115 E 900 N, Richfield, Utah.
Written comments may be submitted as described under
John Zapell, RAC Coordinator by phone at (435) 896-1070 or via email at
Individuals who use telecommunication devices for the deaf (TDD) may call the Federal Information Relay Service (FIRS) at 1-800-877-8339 between 8:00 a.m. and 8:00 p.m., Eastern Standard Time, Monday through Friday.
The purpose of the meeting is to:
1. Welcome new members;
2. discuss reauthorization of the Act;
3. review roles and responsibilties;
4. review current members' status and the recruitment of new members;
5. elect a chairperson; and
6. schedule future meeting dates.
The meeting is open to the public. The agenda will include time for people to make oral statements of three minutes or less. Individuals wishing to make an oral statement should request in writing by May 2, 2016 to be scheduled on the
Forest Service, USDA.
Notice of meeting.
The Del Norte County Resource Advisory Committee (RAC) will meet in Crescent City, California. The committee is authorized under the Secure Rural Schools and Community Self-Determination Act (the Act) and operates in compliance with the Federal Advisory Committee Act. The purpose of the committee is to improve collaborative relationships and to provide advice and recommendations to the Forest Service concerning projects and funding consistent with Title II of the Act. RAC information can be found at the following Web site:
The meeting will be held May 17, 2016, at 6:00 p.m.
All RAC meetings are subject to cancellation. For status of meeting prior to attendance, please contact the person listed under
The meeting will be held at the Del Norte County Unified School District, Boardroom, 301 West Washington Boulevard, Crescent City, California.
Written comments may be submitted as described under
Lynn Wright, RAC Coordinator, by phone at 707-441-3562 or via email at
Individuals who use telecommunication devices for the deaf (TDD) may call the Federal Information Relay Service (FIRS) at 1-800-877-8339 between 8:00 a.m. and 8:00 p.m., Eastern Standard Time, Monday through Friday.
The purpose of the meeting is to:
1. Provide updates regarding the status of Secure Rural Schools Program and Title II funding; and
2. Review and recommend potential projects eligible for funding.
The meeting is open to the public. The agenda will include time for people to make oral statements of three minutes or less. Individuals wishing to make an oral statement should request in writing by May 12, 2016, to be scheduled on the agenda. Anyone who would like to bring related matters to the attention of the committee may file written statements with the committee staff before or after the meeting. Written comments and requests for time to make oral comments must be sent to Lynn Wright, RAC Coordinator, Six Rivers NF Office, 1330 Bayshore Way, Eureka, California 95501; by email to
Enforcement and Compliance, International Trade Administration, Department of Commerce.
Kristen Johnson or Samuel Brummitt, AD/CVD Operations, Office III, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue NW., Washington, DC 20230; telephone: (202) 482-4793 or (202) 482-7851, respectively.
On November 3, 2015, the Department of Commerce (the Department) published a notice of opportunity to request an administrative review of the countervailing duty (CVD) order on steel concrete reinforcing bar (rebar) from the Republic of Turkey (Turkey) for the period September 15, 2014, through December 31, 2014.
Between January 13, 2016, and February 8, 2016, the following companies notified the Department that they had no exports, sales, shipments, or entries of subject merchandise to the United States during the period of review (POR): Ege Celik Endustrisi Sanayi ve Ticaret A.S. (Ege Celik), Ekinciler Demir ve Celik Sanayi A.S. (Ekinciler Demir), Mettech Metalurji Madencilik Muhendislik Uretim Danismanlik ve Ticaret Limited Sirketi (Mettech), Asil Celik Sanayi ve Ticaret A.S. (Asil Celik),
On April 6, 2016, Petitioner submitted a timely withdrawal of its request for review of Ege Celik, Ekinciler Demir, Mettech, Asil Celik, Duferco Celik, and DufEnergy.
Pursuant to 19 CFR 351.213(d)(1), the Secretary will rescind an administrative review, in whole or in part, if the parties that requested a review withdraw the request within 90 days of the date of publication of the notice of initiation. The Department published the
The Department will instruct U.S. Customs and Border Protection (CBP) to assess countervailing duties on all appropriate entries at a rate equal to the cash deposit of estimated countervailing duties required at the time of entry, or withdrawal from warehouse, for consumption, during the period September 15, 2014, through December 31, 2014, in accordance with 19 CFR 351.212(c)(1)(i).
The Department intends to issue appropriate assessment instructions directly to CBP 15 days after publication of this notice.
This notice serves as a final reminder to parties subject to administrative protective orders (APOs) of their responsibility concerning the disposition of proprietary information disclosed under an APO in accordance with 19 CFR 351.305(a)(3), which continues to govern business proprietary information in this segment of the proceeding. Timely written notification of the return or destruction of APO materials or conversion to judicial protective order is hereby requested. Failure to comply with the regulations and terms of an APO is a violation which is subject to sanction.
This notice is issued and published in accordance with sections 751(a)(1) and 777(i)(1) of the Tariff Act of 1930, as amended, and 19 CFR 351.213(d)(4).
Enforcement and Compliance, International Trade Administration, Department of Commerce.
The Department of Commerce (the Department) is rescinding its administrative review in part on diamond sawblades and parts thereof (diamond sawblades) from the People's Republic of China (the PRC) for the period of review (POR) November 1, 2014, through October 31, 2015.
Yang Jin Chun, AD/CVD Operations, Office I, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW., Washington, DC 20230; telephone: (202) 482-5760.
On November 3, 2015, we published a notice of opportunity to request an administrative review of the antidumping duty order on diamond sawblades from the PRC for the POR November 1, 2014, through October 31, 2015.
On January 27, 2016, the Department exercised its discretion to toll its administrative deadlines due to the closure of the Federal Government.
Pursuant to 19 CFR 351.213(d)(1), the Department will rescind an administrative review, “in whole or in part, if a party that requested a review withdraws the request within 90 days of the date of publication of notice of initiation of the requested review.” Because the petitioner and Husqvarna withdrew their review requests in a timely manner, and because no other party requested a review of Husqvarna, we are rescinding the administrative review in part with respect to Husqvarna.
The Department will instruct U.S. Customs and Border Protection (CBP) to assess antidumping duties on all appropriate entries. For Husqvarna, for which the review is rescinded, antidumping duties shall be assessed at the rate equal to the cash deposit of estimated antidumping duties required at the time of entry, or withdrawal from warehouse, for consumption, in accordance with 19 CFR 351.212(c)(1)(i). The Department intends to issue appropriate assessment instructions to CBP within 15 days after publication of this notice.
This notice serves as a final reminder to importers of their responsibility under 19 CFR 351.402(f)(2) to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during this review period. Failure to comply with this requirement may result in the Department's presumption that reimbursement of antidumping duties occurred and the subsequent assessment of doubled antidumping duties.
This notice also serves as a reminder to parties subject to administrative protective order (APO) of their responsibility concerning the disposition of proprietary information disclosed under APO, in accordance with 19 CFR 351.305(a)(3). Timely written notification of the return or destruction of APO materials or conversion to judicial protective order is hereby requested. Failure to comply with the regulations and the terms of an APO is a sanctionable violation.
This notice is issued and published in accordance with sections 751(a)(1) and 777(i)(1) of the Act and 19 CFR 351.213(d)(4).
National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.
Notice; receipt of application for Letters of Authorization; request for comments and information.
NMFS' Office of Protected Resources has received a request from the NMFS Southeast Fisheries Science Center (SEFSC) for authorization to take small numbers of marine mammals incidental to conducting fisheries research, over the course of five years from the date of issuance. Pursuant to regulations implementing the Marine Mammal Protection Act (MMPA), NMFS is announcing receipt of the SEFSC's request for the development and implementation of regulations governing the incidental taking of marine mammals. NMFS invites the public to provide information, suggestions, and comments on the SEFSC's application and request.
Comments and information must be received no later than May 23, 2016.
Comments on the applications should be addressed to Jolie Harrison, Chief, Permits and Conservation Division, Office of Protected Resources, National Marine Fisheries Service. Physical comments should be sent to 1315 East-West Highway, Silver Spring, MD 20910 and electronic comments should be sent to
Ben Laws, Office of Protected Resources, NMFS, (301) 427-8401.
An electronic copy of the SEFSC's application may be obtained by visiting the Internet at:
Section 101(a)(5)(A) of the MMPA (16 U.S.C. 1361
Incidental taking shall be allowed if NMFS finds that the taking will have a
NMFS has defined “negligible impact” in 50 CFR 216.103 as “an impact resulting from the specified activity that cannot be reasonably expected to, and is not reasonably likely to, adversely affect the species or stock through effects on annual rates of recruitment or survival.” Except with respect to certain activities not pertinent here, the MMPA defines “harassment” as: “any act of pursuit, torment, or annoyance which (i) has the potential to injure a marine mammal or marine mammal stock in the wild [Level A harassment]; or (ii) has the potential to disturb a marine mammal or marine mammal stock in the wild by causing disruption of behavioral patterns, including, but not limited to, migration, breathing, nursing, breeding, feeding, or sheltering [Level B harassment].”
On April 6, 2016, NMFS received an adequate and complete application from the SEFSC requesting authorization for take of marine mammals incidental to fisheries research conducted by the SEFSC. The requested regulations would be valid for five years from the date of issuance. The SEFSC plans to conduct fisheries research surveys in multiple geographic regions within the Atlantic Ocean, including the Gulf of Mexico and Caribbean Sea. It is possible that marine mammals may interact with fishing gear (
The Federal Government has a responsibility to conserve and protect living marine resources in U.S. federal waters and has also entered into a number of international agreements and treaties related to the management of living marine resources in international waters outside the United States. NOAA has the primary responsibility for managing marine fin and shellfish species and their habitats, with that responsibility delegated within NOAA to NMFS.
In order to direct and coordinate the collection of scientific information needed to make informed management decisions, Congress created six Regional Fisheries Science Centers, each a distinct organizational entity and the scientific focal point within NMFS for region-based federal fisheries-related research. This research is aimed at monitoring fish stock recruitment, abundance, survival and biological rates, geographic distribution of species and stocks, ecosystem process changes, and marine ecological research. The SEFSC is the research arm of NMFS in the southeast U.S., including the Caribbean.
Research is aimed at monitoring fish stock recruitment, survival and biological rates, abundance and geographic distribution of species and stocks, and providing other scientific information needed to improve our understanding of complex marine ecological processes. The SEFSC proposes to administer and conduct these survey programs over the five-year period.
Interested persons may submit information, suggestions, and comments concerning the SEFSC's request (see
National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.
Notice of correction of a public meeting notice.
The South Atlantic Fishery Management Council, in conjunction with the Mid-Atlantic Fishery Management Council, will hold a Question and Answer (Q&A) public meeting to address cobia management issues in Kill Devil Hills, NC.
The Cobia Q&A public meeting will be held beginning at 6 p.m. on May 9, 2016.
Kim Iverson, Public Information Officer, SAFMC; phone: (843) 571-4366 or toll free: (866) SAFMC-10; fax: (843) 769-4520; email:
The original notice published in the
The Department of Commerce will submit to the Office of Management and Budget (OMB) for clearance the following proposal for collection of information under the provisions of the
The National Marine Fisheries Service (NMFS) proposes to collect economic and attitudinal data from hired captains and crew regarding the performance of the GOM Grouper-Tilefish IFQ Program five years after its implementation. These data will be used to estimate the effects of the GT-IFQ Program on these stakeholders for the five-year program review mandated by the Magnuson-Stevens Fishery Conservation and Management Act (U.S.C. 1801
This information collection request may be viewed at reginfo.gov. Follow the instructions to view Department of Commerce collections currently under review by OMB.
Written comments and recommendations for the proposed information collection should be sent within 30 days of publication of this notice to
The Department of Commerce will submit to the Office of Management and Budget (OMB) for clearance the following proposal for collection of information under the provisions of the Paperwork Reduction Act (44 U.S.C. Chapter 35).
The National Marine Fisheries Service (NMFS) manages fishing activities in the Rose Atoll Marine, Marianas Trench, and Pacific Remote Islands Marine National Monuments. Regulations at 50 CFR part 665 require the owner and operator of a vessel used to non-commercially fish for, take, retain, or possess any management unit species in these monuments to hold a valid permit.
Regulations also require the owner and operator of a vessel that is chartered to fish recreationally for, take, retain, or possess, any management unit species in these monuments to hold a valid permit. The fishing vessel must be registered to the permit. The charter business must be established legally in the permit area where it will operate. Charter vessel clients are not required to have a permit.
The permit application collects basic information about the permit applicant, type of operation, vessel, and permit area. NMFS uses this information to determine permit eligibility. The information is important for understanding the nature of the fishery and provides a link to participants. It also aids in the enforcement of Fishery Ecosystem Plan measures.
Regulations also require the vessel operator to report a complete record of catch, effort, and other data on a NMFS logsheet. The vessel operator must record all requested information on the logsheet within 24 hours of the completion of each fishing day. The vessel operator also must sign, date, and submit the form to NMFS within 30 days of the end of each fishing trip.
This information collection request may be viewed at reginfo.gov. Follow the instructions to view Department of Commerce collections currently under review by OMB.
Written comments and recommendations for the proposed information collection should be sent within 30 days of publication of this notice to
National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.
Notice of public meeting.
The North Pacific Fishery Management Council (Council)
The meeting will be held on Monday May 9, 2016, through Thursday May 12, 2016, from 9 a.m. to 4:30 p.m.
The meeting will be held in the Birch/Willow room at the Hilton Hotel, 500 W. 3rd Ave., Anchorage, Alaska 99501.
Diana Stram, Council staff; telephone: (907) 271-2809.
The agenda includes final assessment on OFL (over fishing limit) and ABC (acceptable biological catch) catch for PIGKC (Pribilof Islands
The Agenda is subject to change, and the latest version will be posted at
These meetings are physically accessible to people with disabilities. Requests for sign language interpretation or other auxiliary aids should be directed to Shannon Gleason at (907) 271-2809 at least 7 working days prior to the meeting date.
16 U.S.C. 1801
National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.
Notice; public meeting.
The Pacific Fishery Management Council's (Pacific Council) Highly Migratory Species Advisory Subpanel (HMSAS) and Highly Migratory Species Management Team (HMSMT) will hold a joint meeting by webinar, which is open to the public.
The HMSAS and HMSMT will meet by webinar on Thursday, May 12, 2016, from 1:30 to 3:30 p.m. Pacific Time, or when business for the day is complete.
To attend the HMSMT/HMSAS webinar visit this link:
Kit Dahl, Pacific Council, 503-820-2422.
The HMSMT and HMSAS will provide advice to Pacific Council-sponsored attendees to the Second North Pacific Albacore Management Strategy Evaluation Workshop sponsored by the International Scientific Committee for Tuna and Tuna-Like Species in the North Pacific Ocean (ISC). The workshop will be held May 24-25, 2016, in Yokohama, Japan. In January 2016, the Secretariat of the Western and Central Pacific Fisheries Commission (WCPFC) circulated a list of management objectives and related questions compiled by Dr. John Holmes, Chair of the ISC's Albacore Working Group based on input from members of the WCPFC's Northern Committee. (This document may be accessed at
Although nonemergency issues not contained in the meeting agenda may be discussed, those issues may not be the subject of formal action during this meeting. Action will be restricted to those issues specifically listed in this document and any issues arising after publication of this document that require emergency action under section 305(c) of the Magnuson-Stevens Fishery Conservation and Management Act, provided the public has been notified of the intent to take final action to address the emergency.
PC-based attendees: Windows® 7, Vista, or XP operating system required. Mac®-based attendees: Mac OS® X 10.5 or newer required. Mobile attendees: iPhone®, iPad®, Android
The meeting is physically accessible to people with disabilities. Requests for sign language interpretation or other auxiliary aids should be directed to Mr. Kris Kleinschmidt at (503) 820-2280 at least 5 days prior to the meeting date.
Committee for Purchase From People Who Are Blind or Severely Disabled.
Additions to and deletions from the Procurement List.
This action adds products and a service to the Procurement List that will be furnished by nonprofit agencies employing persons who are blind or have other severe disabilities, and deletes products and services from the Procurement List previously furnished by such agencies.
Committee for Purchase From People Who Are Blind or Severely Disabled, 1401 S. Clark Street, Suite 715, Arlington, Virginia, 22202-4149.
Barry S. Lineback, Telephone: (703) 603-7740, Fax: (703) 603-0655, or email
On 2/19/2016 (81 FR 8486) and 3/4/2016 (81 FR 11520), the Committee for Purchase From People Who Are Blind or Severely Disabled published notices of proposed additions to the Procurement List.
After consideration of the material presented to it concerning capability of qualified nonprofit agencies to provide the products and service and impact of the additions on the current or most recent contractors, the Committee has determined that the products and service listed below are suitable for procurement by the Federal Government under 41 U.S.C. 8501-8506 and 41 CFR 51-2.4.
I certify that the following action will not have a significant impact on a substantial number of small entities. The major factors considered for this certification were:
1. The action will not result in any additional reporting, recordkeeping or other compliance requirements for small entities other than the small organizations that will furnish the products and service to the Government.
2. The action will result in authorizing small entities to furnish the products and service to the Government.
3. There are no known regulatory alternatives which would accomplish the objectives of the Javits-Wagner-O'Day Act (41 U.S.C. 8501-8506) in connection with the products and service proposed for addition to the Procurement List.
Accordingly, the following products and service are added to the Procurement List:
On 3/18/2016 (81 FR 14837-14838), the Committee for Purchase From People Who Are Blind or Severely Disabled published notice of proposed deletions from the Procurement List.
After consideration of the relevant matter presented, the Committee has determined that the products and services listed below are no longer suitable for procurement by the Federal Government under 41 U.S.C. 8501-8506 and 41 CFR 51-2.4.
I certify that the following action will not have a significant impact on a substantial number of small entities. The major factors considered for this certification were:
1. The action will not result in additional reporting, recordkeeping or other compliance requirements for small entities.
2. The action may result in authorizing small entities to furnish the products and services to the Government.
3. There are no known regulatory alternatives which would accomplish the objectives of the Javits-Wagner-O'Day Act (41 U.S.C. 8501-8506) in connection with the products and services deleted from the Procurement List.
Accordingly, the following products and services are deleted from the Procurement List:
Committee for Purchase From People Who Are Blind or Severely Disabled.
Proposed deletions from the Procurement List.
The Committee is proposing to delete products and a service from the Procurement List that was previously furnished by nonprofit agencies employing persons who are blind or have other severe disabilities.
Committee for Purchase From People Who Are Blind or Severely Disabled, 1401 S. Clark Street, Suite 715, Arlington, Virginia, 22202-4149.
Barry S. Lineback, Telephone: (703) 603-7740, Fax: (703) 603-0655, or email
This notice is published pursuant to 41 U.S.C. 8503 (a)(2) and 41 CFR 51-2.3. Its purpose is to provide interested persons an opportunity to submit comments on the proposed actions.
The following products and service are proposed for deletion from the Procurement List:
Department of the Army, DoD.
Notice to delete a system of records.
The Department of the Army is deleting a system of records notice from its existing inventory of record systems subject to the Privacy Act of 1974, as amended. The system of records notice is AAFES 0604.02, entitled “Unfair Labor Practice Claim/Charges Files.”
Comments will be accepted on or before May 23, 2016. This proposed action will be effective on the day following the end of the comment period unless comments are received which result in a contrary determination.
You may submit comments, identified by docket number and title, by any of the following methods:
*
Follow the instructions for submitting comments.
*
Ms. Tracy Rogers, Department of the Army, Privacy Office, U.S. Army Records Management and Declassification Agency, 7701 Telegraph Road, Casey Building, Suite 144, Alexandria, VA 22325-3905 or by calling (703) 428-7499.
The Department of the Army systems of records notices subject to the Privacy Act of 1974 (5 U.S.C. 552a), as amended, have been published in the
The proposed changes to the record system being amended are set forth in this notice. The proposed amendment is not within the purview of subsection (r) of the Privacy Act of 1974 (5 U.S.C. 552a), as amended, which requires the submission of a new or altered system report.
Unfair Labor Practice Claim/Charges Files (August 9, 1996, 61 FR 41572).
Department of Defense.
Notice.
The Department of Defense is publishing this notice to announce an open meeting of the Strategic Environmental Research and Development Program, Scientific Advisory Board (SAB). This meeting will be open to the public.
Wednesday, June 8, 2016, from 8:30 a.m. to 5:00 p.m.
801 North Glebe Road, Arlington, VA 22203.
Dr. Herb Nelson, SERDP Office, 4800 Mark Center Drive, Suite 17D08, Alexandria, VA 22350-3605; or by telephone at (571) 372-6565.
This meeting is being held under the provisions of the Federal Advisory Committee Act of 1972 (5 U.S.C. Appendix, as amended), the Government in the Sunshine Act of 1976 (5 U.S.C. 552b, as amended), and 41 CFR 102-3.150. This notice is published in accordance with Section 10(a)(2) of the Federal Advisory Committee Act (Pub. L. 92-463).
Pursuant to 5 U.S.C. 552b and 41 CFR 102-3.140 through 102-3.165, and the availability of space, this meeting is open to the public. Seating is on a first-come basis.
The purpose of the June 8, 2016 meeting is to review continuing and new start research and development projects requesting Strategic Environmental Research and Development Program funds as required by the SERDP Statute, U.S. Code—Title 10, Subtitle A, Part IV, Chapter 172, § 2904. The full agenda follows:
Pursuant to 41 CFR 102-3.140, and section 10(a)(3) of the Federal Advisory Committee Act of 1972, the public or interested organizations may submit written statements to the Strategic Environmental Research and Development Program, Scientific Advisory Board. Written statements may be submitted to the committee at any time or in response to an approved meeting agenda.
All written statements shall be submitted to the Designated Federal Officer (DFO) for the Strategic Environmental Research and Development Program, Scientific Advisory Board. The DFO will ensure that the written statements are provided to the membership for their consideration. Contact information for the DFO can be obtained from the GSA's FACA Database at
Office of Innovation and Improvement, Department of Education.
Notice.
Notice inviting applications for new awards for fiscal year (FY) 2016.
Research consistently demonstrates that concentrated poverty in schools negatively affects academic performance. Children who attend high-poverty schools have poorer academic outcomes than those who do not.
In this competition, we are particularly interested in projects that seek to improve MSAP outcomes related to minority group isolation and academic achievement by implementing complementary strategies to increase the socioeconomic integration of schools in an effort to eliminate, reduce, or prevent minority group isolation. Therefore, we include an invitational priority for these types of projects. These proposals will help inform future MSAP competitions conducted under ESSA, which will include the statutory priority for projects proposing to increase racial integration by taking into account socioeconomic diversity in designing and implementing magnet school programs. We also encourage applicants to define socioeconomic status (such as family income, education level or other factors), and to describe how the applicant's approach to defining and using socioeconomic status connects to their efforts to eliminate, reduce, or prevent minority group isolation.
When proposing projects that seek to eliminate, reduce, or prevent minority group isolation and, if applicable, increase the socioeconomic integration of schools, we encourage all applicants to consult the “Guidance on the Voluntary Use of Race to Achieve Diversity and Avoid Racial Isolation in Elementary and Secondary Schools,” released by the U.S. Department of Education's Office for Civil Rights (OCR) and the U.S. Department of Justice on December 2, 2011.
This competition is also designed to improve MSAP outcomes by supporting evidence-based strategies for eliminating, reducing, or preventing minority group isolation; increasing diversity; and improving academic achievement. For this reason, we include a selection factor that asks applicants to address the extent to which projects are grounded in a logic model (as defined in this notice) that connects the program's inputs to its intended outcomes.
In addition, we include a competitive preference priority for applicants that can support their proposed projects with evidence of promise (as defined in this notice). Such evidence will enable us to better understand the empirical connection between school districts that have systematically moved toward integration in the past and student outcomes that are relevant to MSAP. We are particularly interested in evidence-based strategies that promote racial integration by taking into account socioeconomic diversity.
In accordance with 34 CFR 75.105(b)(2)(ii), Competitive Preference Priorities 1, 2, and 3 are from the MSAP regulations (34 CFR 280.32). Competitive Preference Priority 4 is from the notice of final supplemental priorities and definitions for discretionary grant programs, published in the
These priorities are:
The Secretary evaluates the applicant's need for assistance by considering—
(a) The costs of fully implementing the magnet schools project as proposed;
(b) The resources available to the applicant to carry out the project if funds under the program were not provided;
(c) The extent to which the costs of the project exceed the applicant's resources; and
(d) The difficulty of effectively carrying out the approved plan and the project for which assistance is sought, including consideration of how the design of the magnet schools project—
The Secretary determines the extent to which the applicant proposes to carry out new magnet schools projects or significantly revise existing magnet schools projects.
The Secretary determines the extent to which the applicant proposes to select students to attend magnet schools by methods such as lottery, rather than through academic examination.
Projects that are designed to improve student achievement (as defined in this notice) or other related outcomes by supporting local or regional partnerships to give students access to real-world STEM experiences and to give educators access to high-quality STEM-related professional learning.
Projects that propose a process, product, strategy, or practice supported by evidence of promise.
Within this competitive preference priority, we are particularly interested in applications that address the following invitational priority.
This priority is:
We are especially interested in evidence of promise surrounding racial and socioeconomic integration.
An applicant addressing Competitive Preference Priority 5 should clearly identify up to two research study citation(s) to be reviewed for the purposes of meeting this priority. In addition, the applicant should specify the intervention(s) in the identified study or studies that it plans to implement and the findings within the citation(s) that the applicant is requesting be considered as evidence of promise. At a minimum, applicants should provide the referenced citation(s), and a discussion of the relevant intervention(s) and findings, in the application narrative. The Department will not consider a study citation that an applicant fails to clearly identify for review.
An applicant must either ensure that all evidence is available to the Department from publicly available sources and provide links or other guidance indicating where it is available; or, in the application, include a copy of the full study in the Appendix. If the Department determines that an applicant provided insufficient information, the applicant will not have an opportunity to provide additional information at a later time.
Under this competition we are particularly interested in applications that address the following invitational priority.
This priority is:
The Secretary encourages projects that propose to increase racial integration by taking into account socioeconomic diversity in designing and implementing magnet school programs. Projects may implement inter-district or intra-district integration strategies such as neighborhood preferences or weighted lotteries.
(i) There is at least one study that is a—
(A) Correlational study with statistical controls for selection bias;
(B) Quasi-experimental study that meets the What Works Clearinghouse Evidence Standards with reservations; or
(C) Randomized controlled trial that meets the What Works Clearinghouse Evidence Standards with or without reservations.
(ii) The study referenced in paragraph (i) found a statistically significant or substantively important (defined as a difference of 0.25 standard deviations or larger), favorable association between at least one critical component and one relevant outcome presented in the logic model for the proposed process, product, strategy, or practice.
For grades and subjects in which assessments are required under section 1111(b)(3) of the Elementary and Secondary Act of 1965, as amended (ESEA): (1) A student's score on such assessments; and, as appropriate (2) other measures of student learning, such as those described in the subsequent paragraph, provided that they are rigorous and comparable across schools within a local educational agency (LEA).
For grades and subjects in which assessments are not required under section 1111(b)(3) of the ESEA: (1) Alternative measures of student learning and performance, such as student results on pre-tests, end-of-course tests, and objective performance-based assessments; (2) student learning objectives; (3) student performance on English language proficiency assessments; and (4) other measures of student achievement that are rigorous and comparable across schools within an LEA.
20 U.S.C. 7231-7231j.
The Department is not bound by any estimates in this notice.
1.
2.
3.
In addition to the particular data and other items for required and voluntary desegregation plans described in the application package, an application must include—
• Projected enrollment by race and ethnicity for magnet and feeder schools;
• Signed civil rights assurances (included in the application package); and
• An assurance that the desegregation plan is being implemented or will be implemented if the application is funded.
1. Desegregation plans required by a court order. An applicant that submits a desegregation plan required by a court order must submit complete and signed copies of all court documents demonstrating that the magnet schools are a part of the approved desegregation plan. Examples of the types of documents that would meet this requirement include a Federal or State court order that establishes specific magnet schools, amends a previous order or orders by establishing additional or different specific magnet schools, requires or approves the establishment of one or more unspecified magnet schools, or that authorizes the inclusion of magnet schools at the discretion of the applicant.
2. Desegregation plans required by a State agency or official of competent jurisdiction. An applicant submitting a desegregation plan ordered by a State agency or official of competent jurisdiction must provide documentation that shows that the desegregation plan was ordered based upon a determination that State law was violated. In the absence of this documentation, the applicant should consider its desegregation plan to be a voluntary plan and submit the data and information necessary for voluntary plans.
3. Desegregation plans required by Title VI. An applicant that submits a desegregation plan required by OCR under Title VI must submit a complete copy of the desegregation plan demonstrating that magnet schools are part of the approved plan or that the plan authorizes the inclusion of magnet schools at the discretion of the applicant.
4. Modifications to required desegregation plans. A previously approved desegregation plan that does not include the magnet school or program for which the applicant is now seeking assistance must be modified to include the magnet school component. The modification to the desegregation plan must be approved by the court, agency, or official that originally approved the plan. An applicant that wishes to modify a previously approved OCR Title VI desegregation plan to include different or additional magnet schools must submit the proposed
An applicant should indicate in its application if it is seeking to modify its previously approved desegregation plan. However, all applicants must submit proof of approval of all modifications to their plans to the Department by June 30, 2016. Proof of plan modifications should be mailed to the person and address identified under
A voluntary desegregation plan must be approved by the Department each time an application is submitted for funding. Even if the Department has approved a voluntary desegregation plan in an LEA in the past, the desegregation plan must be resubmitted for approval as part of the application.
An applicant's voluntary desegregation plan must describe how the LEA defines or identifies minority group isolation, demonstrate how the LEA will reduce, eliminate, or prevent minority group isolation for each magnet school in the proposed magnet school application, and, if relevant, at identified feeder schools, and demonstrate that the proposed voluntary desegregation plan is adequate under Title VI. For additional guidance on how an LEA can voluntarily reduce minority group isolation and promote diversity in an LEA in light of the Supreme Court's decision in
Complete and accurate enrollment forms and other information as required by the regulations in 34 CFR 280.20(f) and (g) for applicants with voluntary desegregation plans are critical to the Department's determination of an applicant's eligibility under a voluntary desegregation plan (specific requirements are detailed in the application package).
Voluntary desegregation plan applicants must submit evidence of school board approval or evidence of other official adoption of the plan as required by the regulations in 34 CFR 280.20(f)(2).
4.
1.
To obtain a copy via the Internet, use the following address:
To obtain a copy from ED Pubs, write, fax, or call the following: Education Publications Center, P.O. Box 22207, Alexandria, VA 22304. Telephone, toll free: 1-877-433-7827. FAX: (703) 605-6794. If you use a telecommunications device for the deaf (TDD) or a text telephone (TTY), call, toll free: 1-877-576-7734.
You can contact ED Pubs at its Web site, also:
If you request an application from ED Pubs, be sure to identify this program as follows: CFDA number 84.165A.
To obtain a copy from the program office, contact: Tiffany McClain, U.S. Department of Education, 400 Maryland Avenue SW., Room 4W250, Washington, DC 20202-5970. Telephone: (202) 453-7200 or by email:
Individuals with disabilities can obtain a copy of the application package in an accessible format (
2.a.
• A “page” is 8.5″ x 11″, on one side only, with 1″ margins at the top, bottom, and both sides.
• Double space (no more than three lines per vertical inch) all text in the application narrative, including titles, headings, footnotes, quotations, references, and captions, as well as all text in charts, tables, figures, and graphs.
• Use a font that is either 12-point or larger or no smaller than 10 pitch (characters per inch).
•
• Include page numbers at the bottom of each page in your narrative.
The page limit does not apply to Part I, the cover sheet; Part II, the budget section, including the narrative budget justification; Part IV, the assurances, certifications, the desegregation plan
Our reviewers will not read any pages of your application that exceed the page limit.
2.b.
Because we plan to make successful applications available to the public, you may wish to request confidentiality of business information.
Consistent with Executive Order 12600, please designate in your application any information that you believe is exempt from disclosure under Exemption 4. In the appropriate Appendix section of your application, under “Other Attachments Form,” please list the page number or numbers on which we can find this information. For additional information please see 34 CFR 5.11(c).
3.
Applications for grants under this competition must be submitted electronically using the Grants.gov Apply site (Grants.gov). For information (including dates and times) about how to submit your application electronically, or in paper format by mail or hand delivery if you qualify for an exception to the electronic submission requirement, please refer to
We do not consider an application that does not comply with the deadline requirements.
Individuals with disabilities who need an accommodation or auxiliary aid in connection with the application process should contact the person listed under
4.
5.
6.
a. Have a Data Universal Numbering System (DUNS) number and a Taxpayer Identification Number (TIN);
b. Register both your DUNS number and TIN with the System for Award Management (SAM) (formerly the Central Contractor Registry), the Government's primary registrant database;
c. Provide your DUNS number and TIN on your application; and
d. Maintain an active SAM registration with current information while your application is under review by the Department and, if you are awarded a grant, during the project period.
You can obtain a DUNS number from Dun and Bradstreet at the following Web site:
If you are a corporate entity, agency, institution, or organization, you can obtain a TIN from the Internal Revenue Service. If you are an individual, you can obtain a TIN from the Internal Revenue Service or the Social Security Administration. If you need a new TIN, please allow two to five weeks for your TIN to become active.
The SAM registration process can take approximately seven business days, but may take upwards of several weeks, depending on the completeness and accuracy of the data you enter into the SAM database. Thus, if you think you might want to apply for Federal financial assistance under a program administered by the Department, please allow sufficient time to obtain and register your DUNS number and TIN. We strongly recommend that you register early.
Once your SAM registration is active, it may be 24 to 48 hours before you can access the information in, and submit an application through, Grants.gov.
If you are currently registered with SAM, you may not need to make any changes. However, please make certain that the TIN associated with your DUNS number is correct. Also note that you will need to update your registration annually. This may take three or more business days.
Information about SAM is available at
In addition, if you are submitting your application via Grants.gov, you must (1) be designated by your organization as an Authorized Organization Representative (AOR); and (2) register yourself with Grants.gov as an AOR. Details on these steps are outlined at the following Grants.gov Web page:
7.
a.
Applications for grants under MSAP, CFDA number 84.165A, must be submitted electronically using the Governmentwide Grants.gov Apply site at
We will reject your application if you submit it in paper format unless, as described elsewhere in this section, you qualify for one of the exceptions to the electronic submission requirement
You may access the electronic grant application for the Magnet Schools Assistance Program at
Please note the following:
• When you enter the Grants.gov site, you will find information about submitting an application electronically through the site, as well as the hours of operation.
• Applications received by Grants.gov are date and time stamped. Your application must be fully uploaded and submitted and must be date and time stamped by the Grants.gov system no later than 4:30:00 p.m., Washington, DC time, on the application deadline date. Except as otherwise noted in this section, we will not accept your application if it is received—that is, date and time stamped by the Grants.gov system—after 4:30:00 p.m., Washington, DC time, on the application deadline date. We do not consider an application that does not comply with the deadline requirements. When we retrieve your application from Grants.gov, we will notify you if we are rejecting your application because it was date and time stamped by the Grants.gov system after 4:30:00 p.m., Washington, DC time, on the application deadline date.
• The amount of time it can take to upload an application will vary depending on a variety of factors, including the size of the application and the speed of your Internet connection. Therefore, we strongly recommend that you do not wait until the application deadline date to begin the submission process through Grants.gov.
• You should review and follow the Education Submission Procedures for submitting an application through Grants.gov that are included in the application package for MSAP to ensure that you submit your application in a timely manner to the Grants.gov system. You can also find the Education Submission Procedures pertaining to Grants.gov under News and Events on the Department's G5 system home page at
• You will not receive additional point value because you submit your application in electronic format, nor will we penalize you if you qualify for an exception to the electronic submission requirement, as described elsewhere in this section, and submit your application in paper format.
• You must submit all documents electronically, including all information you typically provide on the following forms: the Application for Federal Assistance (SF 424), the Department of Education Supplemental Information for SF 424, Budget Information—Non-Construction Programs (ED 524), and all necessary assurances and certifications.
• You must upload any narrative sections and all other attachments to your application as files in a read-only, non-modifiable Portable Document Format (PDF). Do not upload an interactive or fillable PDF file. If you upload a file type other than a read-only, non-modifiable PDF (
• Your electronic application must comply with any page limit requirements described in this notice.
• After you electronically submit your application, you will receive from Grants.gov an automatic notification of receipt that contains a Grants.gov tracking number. This notification indicates receipt by Grants.gov only, not receipt by the Department. Grants.gov will also notify you automatically by email if your application met all the Grants.gov validation requirements or if there were any errors (such as submission of your application by someone other than a registered Authorized Organization Representative, or inclusion of an attachment with a file name that contains special characters). You will be given an opportunity to correct any errors and resubmit, but you must still meet the deadline for submission of applications.
Once your application is successfully validated by Grants.gov, the Department will retrieve your application from Grants.gov and send you an email with a unique PR/Award number for your application.
These emails do not mean that your application is without any disqualifying errors. While your application may have been successfully validated by Grants.gov, it must also meet the Department's application requirements as specified in this notice and in the application instructions. Disqualifying errors could include, for instance, failure to upload attachments in a read-only, non-modifiable PDF; failure to submit a required part of the application; or failure to meet applicant eligibility requirements. It is your responsibility to ensure that your submitted application has met all of the Department's requirements.
• We may request that you provide us original signatures on forms at a later date.
If you are prevented from electronically submitting your application on the application deadline date because of technical problems with the Grants.gov system, we will grant you an extension until 4:30:00 p.m., Washington, DC time, the following business day to enable you to transmit your application electronically or by hand delivery. You also may mail your application by following the mailing instructions described elsewhere in this notice.
If you submit an application after 4:30:00 p.m., Washington, DC time, on the application deadline date, please contact the person listed under
The extensions to which we refer in this section apply only to the unavailability of, or technical problems with, the Grants.gov system. We will not grant you an extension if you failed to fully register to submit your application to Grants.gov before the application deadline date and time or if the
• You do not have access to the Internet; or
• You do not have the capacity to upload large documents to the Grants.gov system;
• No later than two weeks before the application deadline date (14 calendar days or, if the fourteenth calendar day before the application deadline date falls on a Federal holiday, the next business day following the Federal holiday), you mail or fax a written statement to the Department, explaining which of the two grounds for an exception prevents you from using the Internet to submit your application.
If you mail your written statement to the Department, it must be postmarked no later than two weeks before the application deadline date. If you fax your written statement to the Department, we must receive the faxed statement no later than two weeks before the application deadline date.
Address and mail or fax your statement to: Tiffany McClain, U.S. Department of Education, 400 Maryland Avenue SW., Room 4W250, Washington, DC 20202-5970. FAX: (202) 205-5630.
Your paper application must be submitted in accordance with the mail or hand delivery instructions described in this notice.
b.
If you qualify for an exception to the electronic submission requirement, you may mail (through the U.S. Postal Service or a commercial carrier) your application to the Department. You must mail the original and two copies of your application, on or before the application deadline date, to the Department at the following address: U.S. Department of Education, Application Control Center, Attention: (CFDA Number 84.165A) LBJ Basement Level 1, 400 Maryland Avenue SW., Washington, DC 20202-4260.
You must show proof of mailing consisting of one of the following:
(1) A legibly dated U.S. Postal Service postmark.
(2) A legible mail receipt with the date of mailing stamped by the U.S. Postal Service.
(3) A dated shipping label, invoice, or receipt from a commercial carrier.
(4) Any other proof of mailing acceptable to the Secretary of the U.S. Department of Education.
If you mail your application through the U.S. Postal Service, we do not accept either of the following as proof of mailing:
(1) A private metered postmark.
(2) A mail receipt that is not dated by the U.S. Postal Service.
The U.S. Postal Service does not uniformly provide a dated postmark. Before relying on this method, you should check with your local post office.
We will not consider applications postmarked after the application deadline date.
c.
If you qualify for an exception to the electronic submission requirement, you (or a courier service) may deliver your paper application to the Department by hand. You must deliver the original and two copies of your application by hand, on or before the application deadline date, to the Department at the following address: U.S. Department of Education, Application Control Center, Attention: (CFDA Number 84.165A) 550 12th Street SW., Room 7039, Potomac Center Plaza, Washington, DC 20202-4260.
The Application Control Center accepts hand deliveries daily between 8:00 a.m. and 4:30:00 p.m., Washington, DC time, except Saturdays, Sundays, and Federal holidays.
If you mail or hand deliver your application to the Department—
(1) You must indicate on the envelope and—if not provided by the Department—in Item 11 of the SF 424 the CFDA number, including suffix letter, if any, of the competition under which you are submitting your application; and
(2) The Application Control Center will mail to you a notification of receipt of your grant application. If you do not receive this notification within 15 business days from the application deadline date, you should call the U.S. Department of Education Application Control Center at (202) 245-6288.
1.
The maximum score for all of the selection criteria is 100 points. The maximum score for each criterion is included in parentheses following the title of the specific selection criterion. Each criterion also includes the factors that reviewers will consider in determining the extent to which an applicant meets the criterion.
Points awarded under these selection criteria are in addition to any points an applicant earns under the competitive preference priorities in this notice. The maximum score that an application may receive under the competitive preference priorities and the selection criteria is 125 points.
(a)
The Secretary reviews each application to determine the quality of the desegregation-related activities and determines the extent to which the applicant demonstrates—
(1) The effectiveness of its plan to recruit students from different social, economic, ethnic, and racial backgrounds into the magnet schools. (34 CFR 280.31)
(2) How it will foster interaction among students of different social, economic, ethnic, and racial backgrounds in classroom activities, extracurricular activities, or other activities in the magnet schools (or, if appropriate, in the schools in which the magnet school programs operate). (34 CFR 280.31)
(3) How it will ensure equal access and treatment for eligible project participants who have been traditionally underrepresented in courses or activities offered as part of the magnet school,
(4) The effectiveness of all other desegregation strategies proposed by the applicant for the elimination, reduction, or prevention of minority group isolation in elementary schools and secondary schools with substantial proportions of minority students. (Section 5301(b)(1) of the ESEA)
(b)
The Secretary reviews each application to determine the quality of the project design. In determining the quality of the design of the proposed project, the Secretary considers the following factors:
(1) The manner and extent to which the magnet school program will improve student academic achievement for all students attending each magnet school program, including the manner and extent to which each magnet school program will increase student academic achievement in the instructional area or areas offered by the school. (Sections 5305(b)(1)(B) and 5305(b)(1)(D)(i) of the ESEA)
(2) The extent to which the applicant demonstrates that it has the resources to operate the project beyond the length of
(3) The extent to which the training or professional development services to be provided by the proposed project are of sufficient quality, intensity, and duration to lead to improvements in practice among the recipients of those services. (34 CFR 75.210)
(4) The extent to which the proposed project is supported by strong theory (as defined in this notice). (34 CFR 75.210)
(c)
The Secretary considers the quality of the management plan for the proposed project. In determining the quality of the management plan for the proposed project, the Secretary considers the following factors:
(1) The adequacy of the management plan to achieve the objectives of the proposed project on time and within budget, including clearly defined responsibilities, timelines, and milestones for accomplishing project tasks; and
(2) How the applicant will ensure that a diversity of perspectives are brought to bear in the operation of the proposed project, including those of parents, teachers, the business community, a variety of disciplinary and professional fields, recipients or beneficiaries of services, or others, as appropriate.
(d)
The Secretary reviews each application to determine the qualifications of the personnel the applicant plans to use on the project. The Secretary determines the extent to which—
(1) The project director (if one is used) is qualified to manage the project;
(2) Other key personnel are qualified to manage the project; and
(3) Teachers who will provide instruction in participating magnet schools are qualified to implement the special curriculum of the magnet schools.
To determine personnel qualifications, the Secretary considers experience and training in fields related to the objectives of the project, including the key personnel's knowledge of and experience in curriculum development and desegregation strategies.
(e)
The Secretary considers the quality of the evaluation to be conducted of the proposed project. In determining the quality of the evaluation, the Secretary considers the following factors:
(1) The extent to which the methods of evaluation provide for examining the effectiveness of project implementation strategies;
(2) The extent to which the methods of evaluation include the use of objective performance measures that are clearly related to the intended outcomes of the project and will produce quantitative and qualitative data to the extent possible; and
(3) The extent to which the methods of evaluation will provide performance feedback and permit periodic assessment of progress toward achieving intended outcomes.
2.
In addition, in making a competitive grant award, the Secretary also requires various assurances including those applicable to Federal civil rights laws that prohibit discrimination in programs or activities receiving Federal financial assistance from the Department of Education (34 CFR 100.4, 104.5, 106.4, 108.8, and 110.23).
3.
1.
If your application is not evaluated or not selected for funding, we notify you.
2.
We reference the regulations outlining the terms and conditions of an award in the
3.
(b) At the end of your project period, you must submit a final performance report, including financial information, as directed by the Secretary. If you receive a multi-year award, you must submit an annual performance report that provides the most current performance and financial expenditure information as directed by the Secretary under 34 CFR 75.118. The Secretary may also require more frequent performance reports under 34 CFR 75.720(c). For specific requirements on reporting, please go to
(c) The Secretary may provide a grantee with additional funding for data collection analysis and reporting. In this case the Secretary establishes a data collection period.
4.
(a) The percentage of magnet schools receiving assistance whose student enrollment reduces, eliminates, or prevents minority group isolation.
(b) The percentage of students from major racial and ethnic groups in magnet schools receiving assistance who score proficient or above on State assessments in reading/language arts.
(c) The percentage of students from major racial and ethnic groups in magnet schools receiving assistance who score proficient or above on State assessments in mathematics.
(d) The cost per student in a magnet school receiving assistance.
(e) The percentage of magnet schools that received assistance that are still operating magnet school programs three years after Federal funding ends.
(f) The percentage of magnet schools that received assistance that meet the State's annual measurable objectives and, for high schools, graduation rate targets at least three years after Federal funding ends.
Recognizing that States are no longer required to report annual measurable objectives to the Department under the ESEA, as amended by the ESSA, we include this performance measure in order to ensure grantees monitor and report high school graduation rates. States must establish and measure against ambitious, long-term goals; we encourage MSAP grantees to consider these State goals and incorporate them into their annual performance reporting as appropriate.
5.
In making a continuation award, the Secretary also considers whether the grantee is operating in compliance with the assurances in its approved application, including those applicable to Federal civil rights laws that prohibit discrimination in programs or activities receiving Federal financial assistance from the Department (34 CFR 100.4, 104.5, 106.4, 108.8, and 110.23).
Tiffany McClain, U.S. Department of Education, 400 Maryland Avenue SW., Room 4W250, Washington, DC 20202-5970. Telephone: (202) 453-7200 or by email:
If you use a TDD or TTY, call the FRS, at 1-800-877-8339.
You may also access documents of the Department published in the
National Center for Education Statistics (NCES), Department of Education (ED).
Notice.
In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. chapter 3501
Interested persons are invited to submit comments on or before May 23, 2016.
To access and review all the documents related to the information collection listed in this notice, please use
For specific questions related to collection activities, please contact Kashka Kubzdela at
The Department of Education (ED), in accordance with the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3506(c)(2)(A)), provides the general public and Federal agencies with an opportunity to comment on proposed, revised, and continuing collections of information. This helps the Department assess the impact of its information collection requirements and minimize the public's reporting burden. It also helps the public understand the Department's information collection requirements and provide the requested data in the desired format. ED is soliciting comments on the proposed information collection request (ICR) that is described below. The Department of Education is especially interested in public comment addressing the following issues: (1) Is this collection necessary to the proper functions of the Department; (2) will this information be processed and used in a timely manner; (3) is the estimate of burden accurate; (4) how might the Department enhance the quality, utility, and clarity of the information to be collected; and (5) how might the Department minimize the burden of this collection on the respondents, including through the use of information technology. Please note that written comments received in response to this notice will be considered public records.
U.S. Department of Education, President's Advisory Commission on Asian Americans and Pacific Islanders.
Announcement of an open meeting.
This notice sets forth the schedule and agenda of the meeting of the President's Advisory Commission on Asian Americans and Pacific Islanders (AAPI Commission). The notice also describes the functions of the Commission. Notice of the meeting is required by § 10(a)(2) of the Federal Advisory Committee Act and is intended to notify the public of its opportunity to attend.
The AAPI Commission meeting will be held on May 3, 2016 from 1:00-5:00 p.m. ET and May 4, 2016 from 9:00-12:00 a.m. ET at the U.S. Department of Education, 550 12th Street SW., 10th Floor, Washington, DC 20202.
Jennifer Tran, White House Initiative on Asian Americans and Pacific Islanders, Potomac Center Plaza, 550 12th Street SW., Washington, DC 20202; telephone: 202-245-6747.
Members of the public who would like to attend the meetings on May 3, 2016 and May 4, 2016, should R.S.V.P. to Jennifer Tran via email at
You may also access documents of the Department published in the
Executive Order No. 13515, as amended by Executive Orders 13585 continued by Executive Order 13708.
Department of Energy, Office of Energy Efficiency and Renewable Energy.
Notice of Charter Renewal.
Pursuant to Section 14(a)(2)(A) of the Federal Advisory Committee Act (Pub. L. 92-463), and in accordance with Title 41 of the Code of Federal Regulations, section 102-3.65(a), and following consultation with the Committee Management Secretariat, General Services Administration, notice is hereby given that the Appliance Standards and Rulemaking Federal Advisory Committee's (ASRAC) charter is being renewed.
The Committee will provide advice and recommendations to the Secretary of Energy on matters concerning the DOE's Appliances and Commercial Equipment Standards Program's (Program) test procedures and rulemaking process.
Additionally, the renewal of the ARSAC has been determined to be essential to conduct business of the Department of Energy's and to be the in the public interest in connection with the performance of duties imposed upon the Department of Energy, by law and agreement. The Committee will continue to operate in accordance with the provisions of the Federal Advisory Committee Act, the rules and regulations in implementation of that Act.
John Cymbalsky, Designated Federal Officer at (202) 287-1692.
Office of Fossil Energy, Department of Energy.
Notice of orders.
The Office of Fossil Energy (FE) of the Department of Energy gives notice that during March 2016, it issued orders granting authority to import and export natural gas, to import and export liquefied natural gas (LNG), and to vacate authority. These orders are summarized in the attached appendix and may be found on the FE Web site at
They are also available for inspection and copying in the U.S. Department of Energy (FE-34), Division of Natural Gas Regulation, Office of Regulation and International Engagement, Office of Fossil Energy, Docket Room 3E-033, Forrestal Building, 1000 Independence Avenue SW., Washington, DC 20585, (202) 586-9478. The Docket Room is open between the hours of 8:00 a.m. and 4:30 p.m., Monday through Friday, except Federal holidays.
Take notice that the Commission received the following electric corporate filings:
Take notice that the Commission received the following electric rate filings:
The filings are accessible in the Commission's eLibrary system by clicking on the links or querying the docket number.
Any person desiring to intervene or protest in any of the above proceedings must file in accordance with Rules 211 and 214 of the Commission's Regulations (18 CFR 385.211 and 385.214) on or before 5:00 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding.
eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, service, and qualifying facilities filings can be found at:
Take notice that the Commission received the following electric rate filings:
The filings are accessible in the Commission's eLibrary system by clicking on the links or querying the docket number.
Any person desiring to intervene or protest in any of the above proceedings must file in accordance with Rules 211 and 214 of the Commission's Regulations (18 CFR 385.211 and 385.214) on or before 5:00 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding.
eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, service, and qualifying facilities filings can be found at:
Take notice that the Commission has received the following Natural Gas Pipeline Rate and Refund Report filings:
Any person desiring to intervene or protest in any of the above proceedings must file in accordance with Rules 211 and 214 of the Commission's Regulations (18 CFR 385.211 and § 385.214) on or before 5:00 p.m. Eastern time on the specified date(s). Protests may be considered, but intervention is necessary to become a party to the proceeding.
Any person desiring to protest in any of the above proceedings must file in accordance with Rule 211 of the Commission's Regulations (18 CFR 385.211) on or before 5:00 p.m. Eastern time on the specified comment date.
The filings are accessible in the Commission's eLibrary system by clicking on the links or querying the docket number.
eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, service, and qualifying facilities filings can be found at:
Take notice that the following hydroelectric application has been filed with the Commission and is available for public inspection:
a.
b.
c.
d.
e.
f.
g.
h.
i.
j.
The Commission strongly encourages electronic filing. Please file motions to intervene, protests, comments, or recommendations using the Commission's eFiling system at
The Commission's Rules of Practice and Procedure require all intervenors filing documents with the Commission to serve a copy of that document on each person whose name appears on the official service list for the project. Further, if an intervenor files comments or documents with the Commission relating to the merits of an issue that may affect the responsibilities of a particular resource agency, they must also serve a copy of the document on that resource agency.
k.
l.
m. Individuals desiring to be included on the Commission's mailing list should so indicate by writing to the Secretary of the Commission.
n.
o.
This is a supplemental notice in the above-referenced proceeding of 63SU 8ME LLC`s application for market-based rate authority, with an accompanying rate tariff, noting that such application includes a request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability.
Any person desiring to intervene or to protest should file with the Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426, in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214). Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant.
Notice is hereby given that the deadline for filing protests with regard to the applicant's request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability, is May 4, 2016.
The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at
Persons unable to file electronically should submit an original and 5 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426.
The filings in the above-referenced proceeding are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for electronic review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the Web site that enables subscribers to receive email notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please email
Environmental Protection Agency (EPA).
Notice.
The Environmental Protection Agency (EPA) announces a public teleconference of the Science and Information Subcommittee (SIS) to the Great Lakes Advisory Board (Board). The purpose of this meeting is to discuss the Great Lakes Restoration Initiative (GLRI) covering FY15-19 and other relevant matters.
The teleconference will be held on Wednesday, May 11, 2016 from 10:00 a.m. to 12:00 p.m. Central Time, 11:00 a.m. to 1:00 p.m. Eastern Time. An opportunity will be provided to the public to comment.
The public teleconference will be held by teleconference only. The teleconference number is: 1-877-226-9607; participant code: 605 016 6037.
Any member of the public wishing further information regarding this teleconference may contact Rita Cestaric, Designated Federal Officer (DFO), by email at
Section 309(a) of the Clean Air Act requires that EPA make public its comments on EISs issued by other Federal agencies. EPA's comment letters on EISs are available at:
Federal Communications Commission.
Notice.
The following applicants filed AM or FM proposals to change the community of license: Agape Educational Media, Inc., Station WOWB, Facility ID 40428, BPED-20160329AER, From Brewton, AL, To Pace, FL; Chehalis Valley Educational Foundation, Station KACS, Facility ID 10685, BPED-20160314AAD, From Chehalis, WA, To Rainier, WA; Maria Elena Juarez, Station KRXR, Facility ID 2805, BP-20160217ABQ, From Gooding, ID, To Kuna, ID; Minerva R. Lopez, Station KOUL, Facility ID 28074, BPH-20160216ABP, From Benavides, TX, To Driscoll, TX; Radiojones, LLC, Station WXRS-FM, Facility ID 36212, BPH-20160315AAI, From Portal, GA, To Brooklet, GA Radiojones, LLC, Station WBMZ, Facility ID 73247, BPH-20160315AAU, From Metter, GA, To Portal, GA; RJ Broadcasting Ls, LLC, Station KIDJ, Facility ID 12665, BPH-20160229AAZ, From Rexburg, ID, To Sugar City, ID.
The agency must receive comments on or before June 21, 2016.
Federal Communications Commission, 445 12th Street SW., Washington, DC 20554.
Tung Bui, 202-418-2700.
The full text of these applications is available for inspection and copying during normal business hours in the Commission's Reference Center, 445 12th Street SW., Washington, DC 20554 or electronically via the Media Bureau's Consolidated Data Base System,
Based upon the foregoing, the Receiver has determined that the continued existence of the receivership will serve no useful purpose. Consequently, notice is given that the receivership shall be terminated, to be effective no sooner than thirty days after the date of this Notice. If any person wishes to comment concerning the termination of the receivership, such comment must be made in writing and sent within thirty days of the date of this Notice to: Federal Deposit Insurance Corporation, Division of Resolutions and Receiverships, Attention: Receivership Oversight Department 32.1, 1601 Bryan Street, Dallas, TX 75201.
No comments concerning the termination of this receivership will be considered which are not sent within this time frame.
The companies listed in this notice have applied to the Board for approval, pursuant to the Bank Holding Company Act of 1956 (12 U.S.C. 1841
The applications listed below, as well as other related filings required by the Board, are available for immediate inspection at the Federal Reserve Bank indicated. The applications will also be available for inspection at the offices of the Board of Governors. Interested persons may express their views in writing on the standards enumerated in the BHC Act (12 U.S.C. 1842(c)). If the proposal also involves the acquisition of a nonbanking company, the review also includes whether the acquisition of the nonbanking company complies with the standards in section 4 of the BHC Act (12 U.S.C. 1843). Unless otherwise noted, nonbanking activities will be conducted throughout the United States.
Unless otherwise noted, comments regarding each of these applications must be received at the Reserve Bank indicated or the offices of the Board of Governors not later than May 19, 2016.
A. Federal Reserve Bank of Dallas (Robert L. Triplett III, Senior Vice President) 2200 North Pearl Street, Dallas, Texas 75201-2272:
1.
The notificants listed below have applied under the Change in Bank Control Act (12 U.S.C. 1817(j)) and § 225.41 of the Board's Regulation Y (12 CFR 225.41) to acquire shares of a bank or bank holding company. The factors that are considered in acting on the notices are set forth in paragraph 7 of the Act (12 U.S.C. 1817(j)(7)).
The notices are available for immediate inspection at the Federal Reserve Bank indicated. The notices also will be available for inspection at the offices of the Board of Governors. Interested persons may express their views in writing to the Reserve Bank indicated for that notice or to the offices of the Board of Governors. Comments must be received not later than May 9, 2016.
A. Federal Reserve Bank of Chicago (Colette A. Fried, Assistant Vice President) 230 South LaSalle Street, Chicago, Illinois 60690-1414:
1.
B. Federal Reserve Bank of Minneapolis (Jacquelyn K. Brunmeier, Assistant Vice President) 90 Hennepin Avenue, Minneapolis, Minnesota 55480-0291:
1.
Office of Government-wide Policy (OGP), General Services Administration (GSA).
Notice of a bulletin.
The purpose of this notice is to inform agencies that FTR Bulletin 16-03 pertaining to Relocation Allowances—Relocation Income Tax (RIT) Allowance Tables is now available online at
Mr. Rick Miller, Office of Asset and Transportation Management (MAE), Office of Government-wide Policy, GSA, at 202-501-3822 or via email at
GSA published FTR Amendment 2008-04 in the
The Centers for Disease Control and Prevention (CDC) has submitted the following information collection request to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act of 1995. The notice for the proposed information collection is published to obtain comments from the public and affected agencies.
Written comments and suggestions from the public and affected agencies concerning the proposed collection of information are encouraged. Your comments should address any of the following: (a) Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; (b) Evaluate the accuracy of the agencies estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used; (c) Enhance the quality, utility, and clarity of the information to be collected; (d) Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology,
To request additional information on the proposed project or to obtain a copy of the information collection plan and instruments, call (404) 639-7570 or
National Environmental Assessment Reporting System (NEARS), formerly the National Voluntary Environmental Assessment Information System (NVEAIS)—Revision—National Center for Environmental Health (NCEH), Centers for Disease Control and Prevention (CDC).
Since 2014, environmental factor data associated with foodborne outbreaks have been reported to the National Voluntary Environmental Assessment Information System (NVEAIS; OMB Control No. 0920-0980; expiration date 08/31/2016). CDC is requesting a three-year Office of Management and Budget (OMB) revision for NVEAIS, hereafter referred to as the National Environmental Assessment Reporting System (NEARS). In 2015, it was recommended that NVEAIS be renamed as NEARS. This name change will be an enhancement of the current surveillance system and was recommended by CDC leadership, and other food safety partners who desired to simplify and improve the name.
The goal of NEARS remains to collect data on foodborne illness outbreaks and environmental assessments routinely conducted by local, state, federal, territorial, or tribal food safety programs during outbreak investigations. The data reported through this surveillance system provides timely data on the causes of outbreaks, including environmental factors associated with outbreaks, which are essential to environmental public health regulators' efforts to respond more effectively to outbreaks and prevent future, similar outbreaks.
NEARS was developed by the Environmental Health Specialists Network (EHS-Net), a collaborative network of CDC, the U.S. Food and Drug Administration (FDA), the U.S. Department of Agriculture (USDA), and local, state, territorial, and tribal food safety programs. NEARS is designed to link to CDC's National Outbreak Reporting System (NORS, under the National Disease Surveillance Program II—Disease Summaries; OMB Control No. 0920-0004; expiration date 10/31/2017), a disease outbreak surveillance system for enteric diseases transmitted by food.
When linked, NEARS and NORS data provide opportunities to strengthen the robustness of outbreak data reported to CDC. The foodborne outbreak environmental assessment data reported to NEARS will be used to characterize data on food vehicles and monitor trends; identify contributing factors and their environmental antecedents; generate hypotheses, guide planning, and implementation; evaluate food safety programs, and ultimately assist to prevent future outbreaks. Collectively, these data play a vital role in improving the food safety system, strengthening the robustness of outbreak data reported to CDC.
The first type of NEARS respondent is food safety program officials. Although not a requirement, food safety program personnel participating in NEARS will be encouraged to take two trainings: NEARS food safety program personnel training and NEARS e-learning. The former will train food safety personnel on identifying environmental factors, logging in and entering data into the web-based NEARS data entry system, and troubleshooting problems. The latter is an e-Learning course on how to use a systems approach in foodborne illness outbreak environmental assessments. It is suggested that respondents take this training one time, for a total of 10 hours.
Next, for each outbreak, one official from each participating program will spend a little over an hour to make establishment observations, 30 minutes to record environmental assessment data, and 40 minutes for data entry for both NEARS's surveys into the web-based system. Officials will not report on their programs or personnel.
Food safety programs are typically located in public health or agriculture agencies. There are approximately 3,000 such agencies in the United States. It is not possible to determine exactly how many outbreaks will occur in the future, nor where they will occur. However, based on existing data, we estimate a maximum of 1,400 foodborne illness outbreaks will occur annually. Only programs in the jurisdictions in which these outbreaks occur would voluntarily report to NEARS. Thus, not every program will respond every year. We assume each outbreak will occur in a different jurisdiction.
The second type of NEARS respondents are managers of retail establishments. The manager interview will be conducted at each establishment associated with an outbreak. Most outbreaks are associated with only one establishment. We estimate that a maximum average of four managers at each establishment will be interviewed per outbreak. Each interview will take about 20 minutes.
The total estimated annual burden is 20,300 hours, an increase of 14,233 hours over the previously approved 6,067 burden hours. This increase in requested burden hours is due to the addition of the NEARS e-learning training opportunity.
There is no cost to the respondents other than their time.
Notice.
The Centers for Medicare & Medicaid Services (CMS) is announcing an opportunity for the public to comment on CMS' intention to collect information from the public. Under the Paperwork Reduction Act of 1995 (PRA), federal agencies are required to publish notice in the
Comments on the collection(s) of information must be received by the OMB desk officer by May 23, 2016.
When commenting on the proposed information collections, please reference the document identifier or OMB control number. To be assured consideration, comments and recommendations must be received by the OMB desk officer via one of the following transmissions: OMB, Office of Information and Regulatory Affairs, Attention: CMS Desk Officer, Fax Number: (202) 395-5806
To obtain copies of a supporting statement and any related forms for the proposed collection(s) summarized in this notice, you may make your request using one of following:
1. Access CMS' Web site address at
2. Email your request, including your address, phone number, OMB number, and CMS document identifier, to
3. Call the Reports Clearance Office at (410) 786-1326.
Reports Clearance Office at (410) 786-1326.
Under the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501-3520), federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. The term “collection of information” is defined in 44 U.S.C. 3502(3) and 5 CFR 1320.3(c) and includes agency requests or requirements that members of the public submit reports, keep records, or provide information to a third party. Section 3506(c)(2)(A) of the PRA (44 U.S.C. 3506(c)(2)(A)) requires federal agencies to publish a 30-day notice in the
1.
By special statutory provision, Medicare Part B covers intravenous immunoglobulin (IVIG) for persons with PIDD who wish to receive the drug in-home, but does not allow for Medicare to cover any of the items and services needed to administer the drug unless the person is homebound or otherwise receiving services under a Medicare home health episode of care. Therefore, most beneficiaries with PIDD receive treatment at hospital outpatient departments, physicians' offices, and other outpatient settings. A current alternative to IVIG is subcutaneous immunoglobulin (SCIG), a product that permits some beneficiaries to self-administer the immunoglobulin (IG) safely at home without an attending healthcare professional. SCIG at home is reimbursed by Medicare. However, there are limitations to SCIG—
Under the Medicare Patient IVIG Access Demonstration project, by paying for the items and services needed to administer the IVIG drug in-home, Medicare will enable beneficiaries and their physicians to have greater flexibility in choosing the option that is most appropriate for the beneficiary. With the exception of coverage of these items and services, no other aspects of Medicare coverage for IVIG (
The Medicare Patient IVIG Access Demonstration project mandates CMS to:
• Evaluate the impact of the Medicare IVIG Access Demonstration project on Medicare beneficiary access to IVIG at home,
• Determine the appropriateness of implementing a new payment methodology for IVIG in all settings and determining an appropriate payment amount, and
• Update the existing 2007 Office of the Assistant Secretary for Planning and Evaluation (ASPE) report
The impact evaluation seeks to understand the experiences of demonstration participants and non-participants, to update the 2007 ASPE report, and to support the payment methodology through the use of qualitative and quantitative data collection. The qualitative data collection will consist of a series of stakeholder interviews. Interviews with IVIG/SCIG physicians and nurses will provide information on the experiences of beneficiaries from the perspective of those who have significant, in-depth and practical hands-on experience with delivering IG to Medicare beneficiaries with and without access to home infusions. We will be able to gather their
Centers for Medicare & Medicaid Services, HHS.
Notice.
The Centers for Medicare & Medicaid Services (CMS) is announcing an opportunity for the public to comment on CMS' intention to collect information from the public. Under the Paperwork Reduction Act of 1995 (the PRA), federal agencies are require; to publish notice in the
Comments must be received by June 21, 2016.
When commenting, please reference the document identifier or OMB control number. To be assured consideration, comments and recommendations must be submitted in any one of the following ways:
1.
2.
To obtain copies of a supporting statement and any related forms for the proposed collection(s) summarized in this notice, you may make your request using one of following:
1. Access CMS' Web site address at
2. Email your request, including your address, phone number, OMB number, and CMS document identifier, to
3. Call the Reports Clearance Office at (410) 786-1326.
Reports Clearance Office at (410) 786-1326.
This notice sets out a summary of the use and burden associated with the following information collections. More detailed information can be found in each collection's supporting statement and associated materials (see
Under the PRA (44 U.S.C. 3501-3520), federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. The term “collection of information” is defined in 44 U.S.C. 3502(3) and 5 CFR 1320.3(c) and includes agency requests or requirements that members of the public submit reports, keep records, or provide information to a third party. Section 3506(c)(2)(A) of the PRA requires federal agencies to publish a 60-day notice in the
1.
2.
Centers for Medicare & Medicaid Services (CMS), HHS.
Notice.
This notice announces the application of the American Society for Histocompatibility and Immunogenetics (ASHI) for approval as an accreditation organization for clinical laboratories under the Clinical Laboratory Improvement Amendments of 1988 (CLIA) program for the following specialty and subspecialty areas: General Immunology; Histocompatibility; and ABO/Rh typing. We have determined that the ASHI accreditation meets or exceeds the applicable CLIA requirements. We are announcing the approval and grant ASHI deeming authority for a period of 6 years.
Penelope Meyers, (410) 786-3366.
On October 31, 1988, the Congress enacted the Clinical Laboratory Improvement Amendments of 1988 (CLIA) (Pub. L. 100-578). CLIA amended section 353 of the Public Health Service Act. We issued a final rule implementing the accreditation provisions of CLIA on July 31, 1992 (57 FR 33992). Under those provisions, we may grant deeming authority to an accreditation organization if its requirements for laboratories accredited under its program are equal to or more stringent than the applicable CLIA program requirements in 42 CFR part 493 (Laboratory Requirements). Subpart E of part 493 (Accreditation by a Private, Nonprofit Accreditation Organization or Exemption Under an Approved State Laboratory Program) specifies the requirements an accreditation organization must meet to be approved by us as an accreditation organization under CLIA.
In this notice, we approve ASHI as an organization that may accredit laboratories for purposes of establishing its compliance with CLIA requirements for the subspecialty of General Immunology, the specialty of Histocompatibility, and the subspecialty of ABO/Rh typing. We have examined the initial ASHI application and all subsequent submissions to determine its accreditation program's equivalency with the requirements for approval of an accreditation organization under subpart E of part 493. We have determined that ASHI meets or exceeds the applicable CLIA requirements. We have also determined that ASHI will ensure that its accredited laboratories will meet or exceed the applicable requirements in subparts H, I, J, K, M, Q, and the applicable sections of R. Therefore, we grant ASHI approval as an accreditation organization under subpart E of part 493, for the period stated in the
The following describes the process used to determine that ASHI accreditation program meets the necessary requirements to be approved by us and that, as such, we may approve ASHI as an accreditation program with deeming authority under the CLIA program. ASHI formally applied to us for approval as an accreditation organization under CLIA for the subspecialty of General Immunology, the specialty of Histocompatibility, and the subspecialty of ABO/Rh typing. In reviewing these materials, we reached the following determinations for each applicable part of the CLIA regulations:
ASHI submitted its mechanism for monitoring compliance with all requirements equivalent to condition-level requirements, a list of all its current laboratories and the expiration date of their accreditation, and a detailed comparison of the individual accreditation requirements with the comparable condition-level requirements. The ASHI policies and procedures for oversight of laboratories performing laboratory testing for the subspecialty of General Immunology, the specialty of Histocompatibility, and the subspecialty of ABO/Rh typing are equivalent to those of CLIA in the matters of inspection, monitoring proficiency testing (PT) performance, investigating complaints, and making PT information available. ASHI's requirements for monitoring and inspecting laboratories are the same as those previously approved by us for laboratories in the areas of accreditation organization, data management, the inspection process, procedures for removal or withdrawal of accreditation, notification requirements, and accreditation organization resources. The requirements of the accreditation programs submitted for approval are equal to the requirements of the CLIA regulations.
ASHI's requirements are equal to or more stringent than the CLIA requirements at § 493.801 through § 493.865.
For the specialty of Histocompatibility, ASHI requires participation in at least one external PT program, if available, in histocompatibility testing with an 80 percent score required for successful participation and enhanced PT for laboratories that fail an event. The CLIA regulations do not contain a requirement for external PT for the specialty of Histocompatibility. For the subspecialty of General Immunology, and the subspecialty of ABO/Rh typing, ASHI's requirements are equal to the CLIA requirements.
ASHI's requirements for the submitted subspecialties and specialties are equal to the CLIA requirements at § 493.1100 through § 493.1105.
The ASHI requirements for the submitted subspecialties and specialties are equal to or more stringent than the CLIA requirements at § 493.1200 through § 493.1299. For instance, ASHI's control procedure requirements for the test procedures Nucleic Acid Testing and Flow Cytometry are more specific and detailed than the CLIA language for requirements for control procedures. Section 493.1256 paragraphs (c)(1) and (c)(2) require control materials that will detect immediate errors and monitor accuracy and precision of test performance that may be caused by test system failures, environmental conditions and variance in operator performance. ASHI standards provide detailed, specific requirements for the control materials to be used to meet these CLIA requirements.
We have determined that ASHI requirements for the submitted subspecialties and specialties are equal to or more stringent than the CLIA requirements at § 493.1403 through § 493.1495 for laboratories that perform moderate and high complexity testing. Experience requirements for Director, Technical Supervisor, and General Supervisor exceed CLIA's personnel experience requirements in the specialty of Histocompatibility.
We have determined that the ASHI requirements for the submitted subspecialties and specialties are equal to or more stringent than the CLIA requirements at § 493.1771 through § 493.1780. ASHI inspections are more frequent than CLIA requires. ASHI performs an onsite inspection every 2 years and requires submission of a self-evaluation inspection in the intervening years. If the self-evaluation inspection indicates that an onsite inspection is warranted, ASHI conducts an additional onsite review.
ASHI meets the requirements of subpart R to the extent that it applies to accreditation organizations. ASHI policy sets forth the actions the organization takes when laboratories it accredits do not comply with its requirements and standards for accreditation. When appropriate, ASHI will deny, suspend, or revoke accreditation in a laboratory accredited by ASHI and report that action to us within 30 days. ASHI also provides an appeals process for laboratories that have had accreditation denied, suspended, or revoked.
We have determined that ASHI's laboratory enforcement and appeal policies are equal to or more stringent than the requirements of part 493 subpart R as they apply to accreditation organizations.
The Federal validation inspections of laboratories accredited by ASHI may be conducted on a representative sample basis or in response to substantial allegations of noncompliance (that is, complaint inspections). The outcome of those validation inspections, performed by CMS or our agents, or the State survey agencies, will be our principal means for verifying that the laboratories accredited by ASHI remain in compliance with CLIA requirements. This federal monitoring is an ongoing process.
Our regulations at 42 CFR 493.575 provide that we may rescind the approval of an accreditation organization, such as that of ASHI, for cause, before the end of the effective date of approval. If we determine that ASHI has failed to adopt, maintain and enforce requirements that are equal to, or more stringent than, the CLIA requirements, or that systemic problems exist in its monitoring, inspection or enforcement processes, we may impose a probationary period, not to exceed 1 year, in which ASHI would be allowed to address any identified issues. Should ASHI be unable to address the identified issues within that timeframe, we may, in accordance with the applicable regulations, revoke ASHI's deeming authority under CLIA.
Should circumstances result in our withdrawal of ASHI's approval, we will publish a notice in the
This document does not impose information collection requirements, that is, reporting, record keeping or third party disclosure requirements. Consequently, there is no need for review by the Office of Management and Budget (OMB) under the authority of the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35). The requirements associated with the accreditation process for clinical laboratories under the CLIA program, codified in 42 CFR part 493 subpart E, are currently
In accordance with the provisions of Executive Order 12866, this notice was not reviewed by the Office of Management and Budget.
Office of Refugee Resettlement, ACF, HHS.
Notice of award of a single-source program expansion supplement grant to BCFS Health and Human Services (BCFS) in San Antonio, TX.
The Administration for Children and Families (ACF), Office of Refugee Resettlement (ORR), announces the award of a single-source program expansion supplement grant for $5,820,000 to BCFS Health and Human Services (BCFS) in San Antonio, TX, under the Unaccompanied Children's (UC) Program to support a program expansion supplement.
The expansion supplement grant will support the need to increase shelter capacity to accommodate the increasing numbers of UCs being referred by DHS.
BCFS has a network of trained, qualified emergency staff able to bring on board and operate emergency beds in short timeframe. BCFS provides residential services to UC in the care and custody of ORR, as well as services to include counseling, case management, and additional support services to the family or to the UC and their sponsor when a UC is released from ORR's care and custody.
Supplemental award funds will support activities from October 1, 2015 through September 30, 2016.
Jallyn Sualog, Director, Division of Children's Services, Office of Refugee Resettlement, 330 C Street SW., Washington, DC 20201. Email:
While the number of referrals, to the Unaccompanied Children Program in FY 2015, was below the total referrals from FY 2014, ORR has seen a change to recent referral trends. The UC program has seen an increase in the numbers of UC referred for placement since January 2015. FY15 was the first fiscal year, in the history of the UC program, in which there were eight (11) consecutive months of steadily increasing referrals. During FY 15, the largest total referrals occurred during August, with over 4,300 referrals, and these high referral numbers continued into the month of September with 4,172 referrals. In October and November, 2015, the DCS program has received referrals for initial placements for 10,158 unaccompanied children. ORR has experienced a steadily increasing census of UC in care, with longer average length of stay. This increase, in UC referred for placement, has increased the need for additional shelter beds.
ORR has specific requirements for the provision of services. Award recipients must have the infrastructure, licensing, experience, and appropriate level of trained staff to meet the service requirements and the urgent need for expansion of services. The program's ability to avoid a buildup of children waiting, in Border Patrol stations, for placement in shelters, can only be accommodated through the expansion of the existing program and its services through the supplemental award.
This program is authorized by—
(A) Section 462 of the Homeland Security Act of 2002, which in March 2003, transferred responsibility for the care and custody of Unaccompanied Alien Children from the Commissioner of the former Immigration and Naturalization Service (INS) to the Director of ORR of the Department of Health and Human Services (HHS).
(B) The Flores Settlement Agreement, Case No. CV85-4544RJK (C.D. Cal. 1996), as well as the William Wilberforce Trafficking Victims Protection Reauthorization Act of 2008 (Pub.L. 110-457), which authorizes post release services under certain conditions to eligible children. All programs must comply with the Flores Settlement Agreement, Case No. CV85-4544-RJK (C.D. Cal. 1996), pertinent regulations and ORR policies and procedures.
Food and Drug Administration, HHS.
Notice of public workshop.
The Food and Drug Administration (FDA), Center for Biologics Evaluation and Research (CBER) is announcing a public workshop entitled “Scientific Evidence in Development of Human Cells, Tissues, and Cellular and Tissue-Based Products (HCT/Ps) Subject to Premarket Approval. The purpose of the public workshop is to identify and discuss scientific considerations and challenges to help inform the development of HCT/Ps subject to premarket approval, including stem cell-based products.
The public workshop will be held on September 8, 2016, from 8:30 a.m. to 5 p.m. See the
The public workshop will be held at FDA's White Oak Campus, 10903 New Hampshire Ave., Bldg. 31 Conference Center, the Great Room, Silver Spring, MD 20993-0002. Entrance for the public workshop participants (non-FDA employees) is through Building 1, where routine security check procedures will be performed. For parking and security information, please refer to
Lori Jo Churchyard, Center for Biologics Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 71, Rm. 7301, Silver Spring, MD 20993, 240-402-7911.
The purpose of the public workshop is to identify and discuss scientific considerations and challenges to help inform the development of HCT/Ps subject to premarket approval, including stem cell-based products.
Elsewhere in this issue of the
If you need special accommodations due to a disability and/or have registration questions, please contact Tasha Johnson or Pauline Cottrell at
Food and Drug Administration, HHS.
Notice.
The Food and Drug Administration (FDA) is announcing the issuance of an Emergency Use Authorization (EUA) (the Authorization) for an in vitro diagnostic device for detection of the Ebola Zaire virus in response to the Ebola virus outbreak in West Africa. FDA issued this Authorization under the Federal Food, Drug, and Cosmetic Act (the FD&C Act), as requested by OraSure Technologies, Inc. The Authorization contains, among other things, conditions on the emergency use of the authorized in vitro diagnostic device. The Authorization follows the September 22, 2006, determination by then-Secretary of the Department of Homeland Security (DHS), Michael Chertoff, that the Ebola virus presents a material threat against the U.S. population sufficient to affect national security. On the basis of such determination, the Secretary of Health and Human Services (HHS) declared on August 5, 2014, that circumstances exist justifying the authorization of emergency use of in vitro diagnostic devices for detection of Ebola virus, subject to the terms of any authorization issued under the FD&C Act. The Authorization, which includes an explanation of the reasons for issuance, is reprinted in this document.
The Authorization is effective as of March 4, 2016.
Submit written requests for single copies of the EUA to the Office of Counterterrorism and Emerging Threats, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 1, Rm. 4338, Silver Spring, MD 20993-0002. Send one self-addressed adhesive label to assist that office in processing your request or include a fax number to which the Authorization may be sent. See the
Carmen Maher, Office of Counterterrorism and Emerging Threats, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 1, Rm. 4347, Silver Spring, MD 20993-0002, 301-796-8510 (this is not a toll free number).
Section 564 of the FD&C Act (21 U.S.C. 360bbb-3), as amended by the Project BioShield Act of 2004 (Pub. L. 108-276) and the Pandemic and All-Hazards Preparedness Reauthorization Act of 2013 (Pub. L. 113-5), allows FDA to strengthen the public health protections against biological, chemical, nuclear, and radiological agents. Among other things, section 564 of the FD&C Act allows FDA to authorize the use of an unapproved medical product or an unapproved use of an approved medical product in certain situations. With this EUA authority, FDA can help assure that medical countermeasures may be used in emergencies to diagnose, treat, or prevent serious or life-threatening diseases or conditions caused by biological, chemical, nuclear, or radiological agents when there are no adequate, approved, and available alternatives.
Section 564(b)(1) of the FD&C Act provides that, before an EUA may be issued, the Secretary of HHS must declare that circumstances exist justifying the authorization based on one of the following grounds: (1) A determination by the Secretary of Homeland Security that there is a domestic emergency, or a significant potential for a domestic emergency, involving a heightened risk of attack with a biological, chemical, radiological, or nuclear agent or agents; (2) a determination by the Secretary of Defense that there is a military emergency, or a significant potential for a military emergency, involving a heightened risk to U.S. military forces of attack with a biological, chemical, radiological, or nuclear agent or agents; (3) a determination by the Secretary of HHS that there is a public health emergency, or a significant potential for a public health emergency, that affects, or has a significant potential to affect, national security or the health and security of U.S. citizens living abroad, and that involves a biological, chemical, radiological, or nuclear agent or agents, or a disease or condition that may be attributable to such agent or agents; or (4) the identification of a material threat by the Secretary of Homeland Security under section 319F-2 of the Public Health Service (PHS) Act (42 U.S.C. 247d-6b) sufficient to affect national security or the health and security of U.S. citizens living abroad.
Once the Secretary of HHS has declared that circumstances exist justifying an authorization under section 564 of the FD&C Act, FDA may authorize the emergency use of a drug, device, or biological product if the Agency concludes that the statutory criteria are satisfied. Under section 564(h)(1) of the FD&C Act, FDA is required to publish in the
No other criteria for issuance have been prescribed by regulation under section 564(c)(4) of the FD&C Act. Because the statute is self-executing, regulations or guidance are not required for FDA to implement the EUA authority.
On September 22, 2006, then-Secretary of DHS, Michael Chertoff, determined that the Ebola virus presents a material threat against the U.S. population sufficient to affect national security.
An electronic version of this document and the full text of the Authorization are available on the Internet at
Having concluded that the criteria for issuance of the Authorization under section 564(c) of the FD&C Act are met, FDA has authorized the emergency use of an in vitro diagnostic device for detection of Ebola Zaire virus (detected in the West Africa outbreak in 2014) subject to the terms of the Authorization. The Authorization in its entirety (not including the authorized versions of the fact sheets and other written materials) follows and provides an explanation of the reasons for its issuance, as required by section 564(h)(1) of the FD&C Act:
Food and Drug Administration, HHS.
Notice.
The Food and Drug Administration (FDA) is announcing an opportunity for public comment on the proposed collection of certain information by the Agency. Under the Paperwork Reduction Act of 1995 (the PRA), Federal Agencies are required to publish notice in the
Submit either electronic or written comments on the collection of information by June 21, 2016.
You may submit comments as follows:
Submit electronic comments in the following way:
•
• If you want to submit a comment with confidential information that you do not wish to be made available to the public, submit the comment as a written/paper submission and in the manner detailed (see “Written/Paper Submissions” and “Instructions”).
Submit written/paper submissions as follows:
•
• For written/paper comments submitted to the Division of Dockets Management, FDA will post your comment, as well as any attachments, except for information submitted, marked and identified, as confidential, if submitted as detailed in “Instructions.”
• Confidential Submissions—To submit a comment with confidential information that you do not wish to be
FDA PRA Staff, Office of Operations, Food and Drug Administration, 8455 Colesville Rd., COLE-14526, Silver Spring, MD 20993-0002,
Under the PRA (44 U.S.C. 3501-3520), Federal Agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. “Collection of information” is defined in 44 U.S.C. 3502(3) and 5 CFR 1320.3(c) and includes Agency requests or requirements that members of the public submit reports, keep records, or provide information to a third party. Section 3506(c)(2)(A) of the PRA (44 U.S.C. 3506(c)(2)(A)) requires Federal Agencies to provide a 60-day notice in the
With respect to the following collection of information, FDA invites comments on these topics: (1) Whether the proposed collection of information is necessary for the proper performance of FDA's functions, including whether the information will have practical utility; (2) the accuracy of FDA's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques, when appropriate, and other forms of information technology.
Section 801(e)(2) of the Federal Food, Drug, and Cosmetic Act (the FD&C Act) (21 U.S.C. 381(e)(2)) provides for the exportation of an unapproved device under certain circumstances if the exportation is not contrary to the public health and safety and it has the approval of the foreign country to which it is intended for export. Requesters communicate (either directly or through a business associate in the foreign country) with a representative of the foreign government to which they seek exportation, and written authorization must be obtained from the appropriate office within the foreign government approving the importation of the medical device. An alternative to obtaining written authorization from the foreign government is to accept a notarized certification from a responsible company official in the United States that the product is not in conflict with the foreign country's laws. This certification must include a statement acknowledging that the responsible company official making the certification is subject to the provisions of 18 U.S.C. 1001. This statutory provision makes it a criminal offense to knowingly and willingly make a false or fraudulent statement, or make or use a false document, in any manner within the jurisdiction of a department or Agency of the United States. The respondents to this collection of information are companies that seek to export medical devices. FDA's estimate of the reporting burden is based on the experience of FDA's medical device program personnel.
FDA estimates the burden of this collection of information as follows:
Food and Drug Administration, HHS.
Notice.
The Food and Drug Administration (FDA) has determined the regulatory review period for LUZU and is publishing this notice of that determination as required by law. FDA has made the determination because of the submission of an application to the Director of the U.S. Patent and Trademark Office (USPTO), Department of Commerce, for the extension of a patent which claims that human drug product.
Anyone with knowledge that any of the dates as published (in the
You may submit comments as follows:
Submit electronic comments in the following way:
•
• If you want to submit a comment with confidential information that you do not wish to be made available to the public, submit the comment as a written/paper submission and in the manner detailed (see “Written/Paper Submissions” and “Instructions”).
Submit written/paper submissions as follows:
•
• For written/paper comments submitted to the Division of Dockets Management, FDA will post your comment, as well as any attachments, except for information submitted, marked and identified, as confidential, if submitted as detailed in “Instructions.”
• Confidential Submissions—To submit a comment with confidential information that you do not wish to be made publicly available, submit your comments only as a written/paper submission. You should submit two copies total. One copy will include the information you claim to be confidential with a heading or cover note that states “THIS DOCUMENT CONTAINS CONFIDENTIAL INFORMATION”. The Agency will review this copy, including the claimed confidential information, in its consideration of comments. The second copy, which will have the claimed confidential information redacted/blacked out, will be available for public viewing and posted on
Beverly Friedman, Office of Regulatory Policy, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, Rm. 6250, Silver Spring, MD 20993, 301-796-3600.
The Drug Price Competition and Patent Term Restoration Act of 1984 (Pub. L. 98-417) and the Generic Animal Drug and Patent Term Restoration Act (Pub. L. 100-670) generally provide that a patent may be extended for a period of up to 5 years so long as the patented item (human drug product, animal drug product, medical device, food additive, or color additive) was subject to regulatory review by FDA before the item was marketed. Under these acts, a product's regulatory review period forms the basis for determining the amount of extension an applicant may receive.
A regulatory review period consists of two periods of time: A testing phase and an approval phase. For human drug products, the testing phase begins when the exemption to permit the clinical investigations of the drug becomes effective and runs until the approval phase begins. The approval phase starts with the initial submission of an application to market the human drug product and continues until FDA grants permission to market the drug product. Although only a portion of a regulatory review period may count toward the actual amount of extension that the Director of USPTO may award (for example, half the testing phase must be subtracted as well as any time that may have occurred before the patent was issued), FDA's determination of the length of a regulatory review period for a human drug product will include all of the testing phase and approval phase as specified in 35 U.S.C. 156(g)(1)(B).
FDA has approved for marketing the human drug product LUZU (luliconazole). LUZU is indicated for topical treatment of interdigital tinea pedis, tinea cruris, and tinea corporis caused by the organisms
FDA has determined that the applicable regulatory review period for LUZU is 2,242 days. Of this time, 1,903 days occurred during the testing phase of the regulatory review period, while 339 days occurred during the approval phase. These periods of time were derived from the following dates:
1.
2.
3.
This determination of the regulatory review period establishes the maximum potential length of a patent extension. However, the USPTO applies several statutory limitations in its calculations of the actual period for patent extension. In its application for patent extension, this applicant seeks 1,289 days of patent term extension.
Anyone with knowledge that any of the dates as published are incorrect may submit either electronic or written comments and ask for a redetermination (see
Submit petitions electronically to
Food and Drug Administration, HHS.
Notice.
The Food and Drug Administration (FDA) is announcing the issuance of an Emergency Use Authorization (EUA) (the Authorization) for an in vitro diagnostic device for detection of Zika virus in response to the Zika virus outbreak in the Americas. FDA issued this Authorization under the Federal Food, Drug, and Cosmetic Act (the FD&C Act), as requested by the U.S. Centers for Disease Control and Prevention (CDC). The Authorization contains, among other things, conditions on the emergency use of the authorized in vitro diagnostic device. The Authorization follows the February 26, 2016, determination by the Department of Health and Human Services (HHS) Secretary that there is a significant potential for a public health emergency that has a significant potential to affect national security or the health and security of U.S. citizens living abroad and that involves Zika virus. On the basis of such determination, the HHS Secretary declared on February 26, 2016, that circumstances exist justifying the authorization of emergency use of in vitro diagnostic tests for detection of Zika virus and/or diagnosis of Zika virus infection subject to the terms of any authorization issued under the FD&C Act. The Authorization, which includes an explanation of the reasons for issuance, is reprinted in this document.
The Authorization is effective as of March 17, 2016.
Submit written requests for single copies of the EUA to the Office of Counterterrorism and Emerging Threats, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 1, Rm. 4338, Silver Spring, MD 20993-0002. Send one self-addressed adhesive label to assist that office in processing your request or include a fax number to which the Authorization may be sent. See the
Carmen Maher, Office of Counterterrorism and Emerging Threats, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 1, Rm. 4347, Silver Spring, MD 20993-0002, 301-796-8510 (this is not a toll free number).
Section 564 of the FD&C Act (21 U.S.C. 360bbb-3) as amended by the Project BioShield Act of 2004 (Pub. L. 108-276) and the Pandemic and All-Hazards Preparedness Reauthorization Act of 2013 (Pub. L. 113-5) allows FDA to strengthen the public health protections against biological, chemical, nuclear, and radiological agents. Among other things, section 564 of the FD&C Act allows FDA to authorize the use of an unapproved medical product or an unapproved use of an approved medical product in certain situations. With this EUA authority, FDA can help assure that medical countermeasures may be used in emergencies to diagnose, treat, or prevent serious or life-threatening diseases or conditions caused by biological, chemical, nuclear, or radiological agents when there are no adequate, approved, and available alternatives.
Section 564(b)(1) of the FD&C Act provides that, before an EUA may be issued, the Secretary of HHS must declare that circumstances exist justifying the authorization based on one of the following grounds: (1) A determination by the Secretary of Homeland Security that there is a domestic emergency, or a significant potential for a domestic emergency,
Once the Secretary of HHS has declared that circumstances exist justifying an authorization under section 564 of the FD&C Act, FDA may authorize the emergency use of a drug, device, or biological product if the Agency concludes that the statutory criteria are satisfied. Under section 564(h)(1) of the FD&C Act, FDA is required to publish in the
No other criteria for issuance have been prescribed by regulation under section 564(c)(4) of the FD&C Act. Because the statute is self-executing, regulations or guidance are not required for FDA to implement the EUA authority.
On February 26, 2016, the Secretary of HHS determined that there is a significant potential for a public health emergency that has a significant potential to affect national security or the health and security of U.S. citizens living abroad and that involves Zika virus. On February 26, 2016, under section 564(b)(1) of the FD&C Act, and on the basis of such determination, the Secretary of HHS declared that circumstances exist justifying the authorization of emergency use of in vitro diagnostic tests for detection of Zika virus and/or diagnosis of Zika virus infection, subject to the terms of any authorization issued under section 564 of the FD&C Act. Notice of the determination and declaration of the Secretary was published in the
An electronic version of this document and the full text of the Authorization are available on the Internet at
Having concluded that the criteria for issuance of the Authorization under section 564(c) of the FD&C Act are met, FDA has authorized the emergency use of an in vitro diagnostic device for detection of Zika virus subject to the terms of the Authorization. The Authorization in its entirety (not including the authorized versions of the fact sheets and other written materials) follows and provides an explanation of the reasons for its issuance, as required by section 564(h)(1) of the FD&C Act.
Food and Drug Administration, HHS.
Notice; request for comments and for scientific data and information; extension of comment period.
The Food and Drug Administration (FDA or we) is extending the comment period for the notice entitled “Risk Assessment of Foodborne Illness Associated With Pathogens From Produce Grown in Fields Amended With Untreated Biological Soil Amendments of Animal Origin; Request for Scientific Data, Information, and Comments” that appeared in the
Submit either electronic or written comments by July 5, 2016.
You may submit comments as follows:
Submit electronic comments in the following way:
•
• If you want to submit a comment with confidential information that you do not wish to be made available to the public, submit the comment as a written/paper submission and in the manner detailed (see “Written/Paper Submissions” and “Instructions”).
Submit written/paper submissions as follows:
•
• For written/paper comments submitted to the Division of Dockets Management, FDA will post your comment, as well as any attachments, except for information submitted, marked and identified, as confidential, if submitted as detailed in “Instructions.”
• Confidential Submissions—To submit a comment with confidential information that you do not wish to be made publicly available, submit your comments only as a written/paper submission. You should submit two copies total. One copy will include the
Jane Van Doren, Center for Food Safety and Applied Nutrition (HFS-005), Food and Drug Administration, 5100 Paint Branch Pkwy., College Park, MD 20740, 240-402-2927.
In the
We received multiple requests for an extension of the comment period. The requests conveyed concern that the original 60-day comment period does not allow sufficient time to provide the scientific data, information, and comments described in the notice. We have considered the requests and are extending the comment period for the notice until July 5, 2016. We believe that a 60-day extension allows adequate time for interested persons to submit comments without significantly delaying rulemaking on these important issues.
Office of Disease Prevention and Health Promotion, Office of the Assistant Secretary for Health, Office of the Secretary, U.S. Department of Health and Human Services.
Notice; correction.
In the
Emmeline Ochiai, email address:
In the
Nominations for membership to the Committee must be submitted by 6:00 p.m. Eastern Time on May 2, 2016.
Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meeting.
The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.
Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meeting.
The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.
This notice is being published less than 15 days prior to the meeting due to the timing limitations imposed by the review and funding cycle.
Under the provisions of Section 3507(a)(1)(D) of the Paperwork Reduction Act of 1995, the National Institutes of Health (NIH) has submitted to the Office of Management and Budget (OMB) a request for review and approval of the information collection listed below. This proposed information collection was previously published in the
To obtain a copy of the data collection plans and instruments, submit comments in writing, or request more information on the proposed project, contact: Ms. Deshiree Belis, National Heart, Lung, and Blood Institute, National Institutes of Health, 6705 Rockledge Dr., Suite 6185A, Bethesda, MD 20892, or call non-toll-free number 301-435-1032, or Email your request, including your address to
OMB approval is requested for 3 years. There are no costs to respondents other than their time. The total estimated annualized burden hours are 8,382.
Estimates of annualized total hour burden are summarized in Table A.12-1.4 Below.
National Institutes of Health, HHS.
Notice.
This is notice, in accordance with 35 U.S.C. 209 and 37 CFR part 404, that the National Cancer Institute, National Institutes of Health, Department of Health and Human Services, is contemplating the grant of an exclusive patent license to Dedalus Pharma, LLC (“Dedalus”) located in Maryland, USA.
United States Provisional Patent Application No. 62/088,882, filed December 8, 2014, entitled “Anti-CD70 Chimeric Antigen Receptors” [HHS Reference No. E-021-2015/0-US-01]; and PCT Application No. PCT/US2015/025047 filed April 9, 2015 entitled “Anti-CD70 Chimeric Antigen Receptors” [HHS Reference No. E-021-2015/0-PCT-02].
The patent rights in these inventions have been assigned to the government of the United States of America.
The patent rights in these inventions have been assigned to the government of the United States of America. The prospective exclusive license territory may be worldwide and the field of use may be limited to the development and commercialization of CD70 chimeric antigen receptor (CAR)-based autologous peripheral blood T cell therapy products as set forth in the Licensed Patent Rights for the treatment of chronic myelogenous leukemia in humans.
Only written comments and/or applications for a license which are received by the Technology Transfer Center at the National Cancer Institute on or before May 9, 2016 will be considered.
Requests for copies of the patent application, inquiries, and comments relating to the contemplated exclusive license should be directed to: Andrew Burke, Ph.D., Licensing and Patenting Manager, Technology Transfer Center, National Cancer Institute, 9609 Medical Center Drive, MSC 9702, Rockville, MD 20852; Telephone: (240) 276-5484; Email:
The present invention describes chimeric antigen receptors (CARs) targeting CD70. CARs are hybrid proteins comprised of extracellular antigen binding domains and intracellular signaling domains designed to activate the cytotoxic functions of CAR-transduced T cells upon antigen stimulation.
CD70 is a co-stimulatory molecule that provides proliferative and survival cues to competent cells upon binding to its cognate receptor, CD27. Its expression is primarily restricted to activated lymphoid cells; however, recent research has demonstrated that several cancers, including renal cell carcinoma, glioblastoma, non-Hodgkin's lymphoma, and chronic myelogenous leukemia also express CD70 under certain circumstances. Due to its limited expression in normal tissues, CARs targeting CD70 may be useful in adoptive cell therapy protocols for the treatment of select cancers.
The prospective exclusive license will be royalty bearing and will comply with the terms and conditions of 35 U.S.C. 209 and 37 CFR part 404. The prospective exclusive license may be granted unless within fifteen (15) days from the date of this published notice, the NCI receives written evidence and argument that establishes that the grant of the license would not be consistent with the requirements of 35 U.S.C. 209 and 37 CFR part 404.
Complete applications for a license in an appropriate field of use that are timely filed in response to this notice will be treated as objections to the grant of the contemplated exclusive license. Comments and objections submitted to this notice will not be made available for public inspection and, to the extent permitted by law, will not be released under the Freedom of Information Act, 5 U.S.C. 552.
Under the provisions of section 3507(a)(1)(D) of the Paperwork Reduction Act of 1995, the National Institutes of Health (NIH), has submitted to the Office of Management and Budget (OMB) a request for review and approval of the information collection listed below. This proposed information collection was previously published in the
To obtain a copy of the data collection plans and instruments or request more information on the proposed project contact: Dale Sandler, Ph.D., Chief, Epidemiology Branch, National Institute of Environmental Health Sciences, NIH, 111 T.W. Alexander Drive, P.O. Box 12233, MD A3-05, Research Triangle Park, NC 27709, or call non-toll-free number 919-541-4668, or email your request, including your address to:
OMB approval is requested for 3 years. There are no costs to respondents other than their time. The total estimated annualized burden hours are 11,440.
Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings.
The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.
U.S. Customs and Border Protection, Department of Homeland Security.
30-Day notice and request for comments; Extension of an existing collection of information.
U.S. Customs and Border Protection (CBP) of the Department of Homeland Security will be submitting the following information collection request to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act: Regulations Relating to Recordation and Enforcement of Trademarks and Copyrights (Part 133 of the CBP Regulations). This is a proposed extension of an information collection that was previously approved. CBP is proposing that this information collection be extended with no change to the burden hours or to the information collected. This document is published to obtain comments from the public and affected agencies.
Written comments should be received on or before May 23, 2016 to be assured of consideration.
Interested persons are invited to submit written comments on this proposed information collection to
Requests for additional information should be directed to Tracey Denning, U.S. Customs and Border Protection, Regulations and Rulings, Office of Trade, 90 K Street NE., 10th Floor, Washington, DC 20229-1177, at 202-325-0265.
This proposed information collection was previously published in the
CBP officers enforce these intellectual property rights at the border. The information that respondents must submit in order to seek the assistance of CBP to protect against infringing imports is specified for trademarks under 19 CFR 133.2 and 133.3, and the information to be submitted for copyrights is specified under 19 CFR 133.32 and 133.33. Trademark, trade name, and copyright owners seeking border enforcement of their intellectual property rights provide information through the recordation process in order to assist CBP officers in identifying violating articles at the border. Respondents may submit this information through the IPR e-Recordation Web site at
Office of the Assistant Secretary for Community Planning and Development, HUD.
Notice.
This Notice identifies unutilized, underutilized, excess, and surplus Federal property reviewed by HUD for suitability for use to assist the homeless.
Juanita Perry, Department of Housing and Urban Development, 451 Seventh Street SW., Room 7266, Washington, DC 20410; telephone (202) 402-3970; TTY number for the hearing- and speech-impaired (202) 708-2565 (these telephone numbers are not toll-free), or call the toll-free Title V information line at 800-927-7588.
In accordance with 24 CFR part 581 and section 501 of the Stewart B. McKinney Homeless Assistance Act (42 U.S.C. 11411), as amended, HUD is publishing this Notice to identify Federal buildings and other real property that HUD has reviewed for suitability for use to assist the homeless. The properties were reviewed using information provided to HUD by Federal landholding agencies regarding unutilized and underutilized buildings and real property controlled by such agencies or by GSA regarding its inventory of excess or surplus Federal property. This Notice is also published in order to comply with the December 12, 1988 Court Order in
Properties reviewed are listed in this Notice according to the following categories: Suitable/available, suitable/unavailable, and suitable/to be excess, and unsuitable. The properties listed in the three suitable categories have been reviewed by the landholding agencies, and each agency has transmitted to HUD: (1) Its intention to make the property available for use to assist the homeless, (2) its intention to declare the property excess to the agency's needs, or (3) a statement of the reasons that the property cannot be declared excess or made available for use as facilities to assist the homeless.
Properties listed as suitable/available will be available exclusively for homeless use for a period of 60 days from the date of this Notice. Where
For properties listed as suitable/to be excess, that property may, if subsequently accepted as excess by GSA, be made available for use by the homeless in accordance with applicable law, subject to screening for other Federal use. At the appropriate time, HUD will publish the property in a Notice showing it as either suitable/available or suitable/unavailable.
For properties listed as suitable/unavailable, the landholding agency has decided that the property cannot be declared excess or made available for use to assist the homeless, and the property will not be available.
Properties listed as unsuitable will not be made available for any other purpose for 20 days from the date of this Notice. Homeless assistance providers interested in a review by HUD of the determination of unsuitability should call the toll free information line at 1-800-927-7588 for detailed instructions or write a letter to Ann Marie Oliva at the address listed at the beginning of this Notice. Included in the request for review should be the property address (including zip code), the date of publication in the
For more information regarding particular properties identified in this Notice (
May 2, 2016, 9:00 a.m.-1:00 p.m.
Inter-American Foundation, 1331 Pennsylvania Ave. NW., Suite 1200 North Building, Washington, DC 20004.
Meeting of the Board of Directors, Open to the Public.
Paul Zimmerman, General Counsel (202) 683-7118.
Fish and Wildlife Service, Interior.
Notice of receipt of applications for permit.
We, the U.S. Fish and Wildlife Service, invite the public to comment on the following applications to conduct certain activities with endangered species. With some exceptions, the Endangered Species Act (ESA) prohibit activities with listed species unless Federal authorization is acquired that allows such activities.
We must receive comments or requests for documents on or before May 23, 2016.
•
•
When submitting comments, please indicate the name of the applicant and the PRT# you are commenting on. We will post all comments on
Brenda Tapia, (703) 358-2104 (telephone); (703) 358-2281 (fax);
Send your request for copies of applications or comments and materials concerning any of the applications to the contact listed under
Please make your requests or comments as specific as possible. Please confine your comments to issues for which we seek comments in this notice, and explain the basis for your comments. Include sufficient information with your comments to allow us to authenticate any scientific or commercial data you include.
The comments and recommendations that will be most useful and likely to influence agency decisions are: (1) Those supported by quantitative information or studies; and (2) Those that include citations to, and analyses of, the applicable laws and regulations. We will not consider or include in our administrative record comments we receive after the close of the comment period (see
Comments, including names and street addresses of respondents, will be available for public review at the street address listed under
To help us carry out our conservation responsibilities for affected species, and in consideration of section 10(a)(1)(A) of the Endangered Species Act of 1973, as amended (16 U.S.C. 1531
The applicant requests a permit to import biological samples from salvaged specimens of chimpanzee (
The applicant requests a permit to import biological samples from captive-held Asian elephants (
The applicant requests a permit to import one female captive-bred snow leopard (
The applicant requests a permit to import biological samples from captive-bred and captive held mangabey (
The applicant requests a permit to export and re-import non-living museum specimens of endangered and threatened species of plants and animals previously accessioned in the applicant's collection for scientific research. This notification covers activities to be conducted by the applicant over a 5-year period.
The applicant requests renewal of their permit to export captive-bred/captive-hatched Kihansi spray toads (
The applicant requests a renewal of his captive-bred wildlife registration under 50 CFR 17.21(g) for the following species to enhance species propagation or survival: Cheetah (
The applicant requests an amendment and renewal of his captive-bred wildlife registration under 50 CFR 17.21(g) for the following species to enhance species propagation or survival: African lion (
The applicant requests an amendment to his captive-bred wildlife registration under 50 CFR 17.21(g) for the following species to enhance species propagation or survival: Blue-billed curassow (
The applicant requests an amendment to his captive-bred wildlife registration under 50 CFR 17.21(g) to add Galapagos tortoise (
Bureau of Indian Affairs, Interior.
Notice.
The Oglala Sioux Tribe and State of South Dakota entered into an amendment to an existing Tribal-State compact governing Class III gaming. This notice announces approval of the amendment.
Effective April 22, 2016.
Ms. Paula L. Hart, Director, Office of Indian Gaming, Office of the Assistant Secretary—Indian Affairs, Washington, DC 20240, (202) 219-4066.
Section 11 of the Indian Gaming Regulatory Act (IGRA) requires the Secretary of the Interior to publish in the
Bureau of Land Management, Interior.
Notice.
Notice is hereby given that the Celebration Fire 2-year temporary road closure is in effect on public lands administered by the Morley Nelson Snake River Birds of Prey National Conservation Area (NCA). One mile of road will be closed to motorized vehicle traffic to protect sensitive resources.
This closure will be in effect on April 22, 2016 and will remain in effect until April 23, 2018, unless otherwise rescinded or modified by the authorized officer or designated Federal officer.
Tate Fischer, Four Rivers Field Office Manager at 3948 Development Ave., Boise, Idaho, 83705, via email at
The Celebration Fire temporary closure affects a 1-mile road segment that crosses public lands located in Owyhee County, Idaho, approximately 5 miles northeast of Murphy, which burned June 6-9, 2015. The road affected by this temporary closure is found in:
The road is shown on the map named, “Celebration Fire Temporary Road Closure.” The Celebration Fire temporary road closure, which affects approximately 1 mile of road, is necessary to protect sensitive resources, which, with the removal of vegetation,
The effects of the temporary road closure are described in the Boise Normal Fire Rehabilitation and Stabilization Environmental Assessment (#ID-090-2004-050-EA), and the specific proposal was analyzed in Determination of NEPA Adequacy, (#DOI-BLM-ID-B011-2015-0006-DNA), signed on September 16, 2015. The BLM has placed the EA and the Finding of No Significant Impact on file in the BLM Administrative Record at the address specified in the
Under the authority of Section 303(a) of the Federal Land Policy and Management Act of 1976 (43 U.S.C. 1733(a)), 43 CFR 8360.0-7, and 43 CFR 8364.1, the BLM will enforce the following rule within the Celebration Fire Temporary Road Closure order:
Motorized vehicles must not be used on the closed road segment.
43 CFR 8364.1.
Bureau of Ocean Energy Management (BOEM), Interior.
Notice of Availability (NOA) of a Draft Environmental Impact Statement (EIS).
BOEM is announcing the availability of a Draft EIS for Gulf of Mexico OCS oil and gas lease sales tentatively scheduled from 2017-2022 (2017-2022 Gulf of Mexico Multisale Draft EIS or Draft Environmental Impact Statement). BOEM proposes to conduct 10 region-wide Gulf of Mexico oil and gas lease sales during this five-year period that are tentatively scheduled in the Proposed 2017-2022 OCS Oil and Gas Leasing Program (Five-Year Program). The lease sales proposed in the Gulf of Mexico in the Five-Year Program are region-wide lease sales comprised of the Western and Central Planning Areas, and a small portion of the Eastern Planning Area this is not subject to Congressional moratorium. As Federal regulations allow for several related or similar proposals to be analyzed in one EIS (40 CFR 1502.4), the 2017-2022 Gulf of Mexico Multisale Draft EIS provides the environmental analyses necessary for all 10 region-wide Gulf of Mexico oil and gas lease sales tentatively scheduled in the Five-Year Program. As a decision on whether and how to proceed with each proposed lease sale in the Five-Year Program is made individually, the proposed action considered in the 2017-2022 Gulf of Mexico Multisale Draft EIS is comprised of a single region-wide sale in the Gulf of Mexico. The Draft EIS provides a discussion of the potential significant impacts of a proposed action and an analysis of reasonable alternatives to the proposed action. This NOA also serves to announce the beginning of the public comment period for the Draft EIS.
The Draft EIS and associated information are available on BOEM's Web site at
Comments should be submitted no later than June 6, 2016.
For more information on the Draft EIS, you may contact Mr. Gary D. Goeke, Bureau of Ocean Energy Management, Gulf of Mexico OCS Region, Office of Environment (GM 623E), 1201 Elmwood Park Boulevard, New Orleans, Louisiana 70123-2394 or by email at
Federal, State, Tribal, and local governments and/or agencies and the public may submit written comments on this Draft EIS through the following methods:
1.
2. U.S. mail in an envelope labeled “Comments for the 2017-2022 Gulf of Mexico Multisale Draft EIS” and addressed to Mr. Gary D. Goeke, Chief, Environmental Assessment Section, Office of Environment (GM 623E), Bureau of Ocean Energy Management, Gulf of Mexico OCS Region, 1201 Elmwood Park Boulevard, New Orleans, Louisiana 70123-2394. Comments must be postmarked by the last day of the comment period to be considered. This date is June 6, 2016; or
3. Via email to
BOEM will hold public meetings to obtain comments regarding the Draft Environmental Impact Statement. The meetings are scheduled as follows:
• Beaumont, Texas: Monday, May 9, 2016, Holiday Inn Hotel and Suites Beaumont—Plaza, 3950 I-10 South at Walden Road, Beaumont, Texas 77705, one meeting beginning at 4:30 p.m. CDT;
New Orleans, Louisiana: Thursday, May 12, 2016, Sheraton Metairie—New Orleans Hotel, 4 Gallaria Boulevard,
• Panama City, Florida: Tuesday, May 17, 2016, Bay Point Golf Resort and Spa, 4114 Jan Cooley Drive, Panama City Beach, Florida 32408, one meeting beginning at 4:30 p.m. CDT;
• Mobile, Alabama: Wednesday, May 18, 2016, Renaissance Mobile Riverview Plaza Hotel, 64 South Water Street, Mobile, Alabama 36602, one meeting beginning at 4:30 p.m. CDT; and
• Gulfport, Mississippi: Thursday, May 19, 2016, Courtyard by Marriott, Gulfport Beachfront MS Hotel, 1600 East Beach Boulevard, Gulfport, Mississippi 39501, one meeting beginning at 4:30 p.m. CDT.
Before including your address, phone number, email address, or other personal identifying information in your comment, you should be aware that your entire comment, including your personal identifying information, may be made publicly available at any time. While you can ask us in your comments to withhold your personal identifying information from public review, we cannot guarantee that we will be able to do so.
This NOA of a Draft EIS is in compliance with the National Environmental Policy Act of 1969, as amended (42 U.S.C. 4321
Office of Surface Mining Reclamation and Enforcement, Interior.
Notice and request for comments.
In compliance with the Paperwork Reduction Act of 1995, the Office of Surface Mining Reclamation and Enforcement (OSMRE) is announcing that the information collection request for the Nomination and Request for Payment Form for OSMRE's Technical Training Courses, has been submitted to the Office of Management and Budget (OMB) for review and approval. This information collection activity was previously approved by OMB, and assigned control number 1029-0120. The information collection request describes the nature of the information collection and its expected burden and cost.
OMB has up to 60 days to approve or disapprove the information collection but may respond after 30 days. Therefore, public comments should be submitted to OMB by May 23, 2016, in order to be assured of consideration.
Submit comments to the Office of Information and Regulatory Affairs, Office of Management and Budget, Department of the Interior Desk Officer, via email at
To receive a copy of the information collection request contact John Trelease at (202) 208-2783, or electronically at
OMB regulations at 5 CFR 1320, which implement provisions of the Paperwork Reduction Act of 1995 (Pub. L. 104-13), require that interested members of the public and affected agencies have an opportunity to comment on information collection and recordkeeping activities [see 5 CFR 1320.8(d)]. OSMRE has submitted a request to OMB to renew its approval of the collection of information found in its Nomination and Request for Payment Form for OSM Technical Training Courses. OSMRE is requesting a 3-year term of approval for this collection. This collection is required to obtain or retain a benefit.
An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB control number. The OMB control number for this collection of information is 1029-0120. The OMB control number and expiration date appear on the form.
As required by 5 CFR 1320.8(d), a
Send comments on the need for the collection of information for the performance of the functions of the agency; the accuracy of the agency's burden estimates; ways to enhance the quality, utility and clarity of the information collection; and ways to minimize the information collection burden on respondents, such as use of automated means of collection of the information, to the offices listed in the
Before including your address, phone number, email address, or other personal identifying information in your comment, you should be aware that your entire comment—including your personal identifying information—may be made publicly available at any time. While you can ask us in your comment to withhold your personal identifying information from public review, we cannot guarantee that we will be able to do so.
On the basis of the record
The Commission, pursuant to section 751(c) of the Tariff Act of 1930 (19 U.S.C. 1675(c)), instituted these reviews on April 1, 2015 (80 FR 17490) and determined on July 6, 2015 that it would conduct full reviews (80 FR 43118, July 21, 2015). Notice of the scheduling of the Commission's reviews and of a public hearing to be held in connection therewith was given by posting copies of the notice in the Office of the Secretary, U.S. International Trade Commission, Washington, DC, and by publishing the notice in the
The Commission made these determinations pursuant to section 751(c) of the Tariff Act of 1930 (19 U.S.C. 1675(c)). It completed and filed its determinations in these reviews on April 18, 2016. The views of the Commission are contained in USITC Publication 4605 (April 2016), entitled
By order of the Commission.
U.S. International Trade Commission.
Notice.
Notice is hereby given that the U.S. International Trade Commission has determined to extend the target date for completion of the above-captioned investigation until June 1, 2016. The Commission also requests briefing from the parties on the issues indicated in this notice.
Lucy Grace D. Noyola, Office of the General Counsel, U.S. International Trade Commission, 500 E Street SW., Washington, DC 20436, telephone 202-205-3438. Copies of non-confidential documents filed in connection with this investigation are or will be available for inspection during official business hours (8:45 a.m. to 5:15 p.m.) in the Office of the Secretary, U.S. International Trade Commission, 500 E Street SW., Washington, DC 20436, telephone 202-205-2000. General information concerning the Commission may also be obtained by accessing its Internet server (
The Commission instituted this investigation on December 12, 2014, based on a complaint filed by RealD, Inc. of Beverly Hills, California (“RealD”). 79 FR 73902-03 (Dec. 12, 2014). The complaint alleges violations of section 337 of the Tariff Act of 1930, as amended, 19 U.S.C. 1337, in the importation into the United States, the sale for importation, and the sale within the United States after importation of certain three-dimensional cinema systems, and components thereof, that infringe certain claims of U.S. Patent Nos. 7,905,602 (“the '602 patent”), 7,857,455 (“the '455 patent”), 7,959,296 (“the '296 patent”), and 8,220,934 (“the '934 patent”).
On July 23, 2015, the Commission later terminated the investigation as to various of the asserted claims and the '602 patent in its entirety. Notice (July 23, 2015) (determining not to review Order No. 6 (July 2, 2015)); Notice (Aug. 20, 2015) (determining not to review Order No. 7 (Aug. 3, 2015)).
On September 25, 2015, the Commission determined on summary determination that RealD satisfied the economic prong of the domestic industry requirement through its significant investment in plant, significant investment in labor, and substantial investment in engineering, research, and development. Notice (Sept. 25, 2015) (determining to review in part Order No. 9 (Aug. 20, 2015)). The Commission, however, reversed the presiding administrative law judge's (“ALJ”) summary determination with respect to RealD's investment in equipment.
On December 16, 2015, the ALJ issued a final ID finding a violation of section 337 with respect to the remaining asserted patents. The ALJ found that the asserted claims of each patent are infringed and not invalid or unenforceable. The ALJ found that the technical prong of the domestic industry requirement was satisfied for the asserted patents. The ALJ also issued a Recommended Determination on Remedy and Bonding (“RD”), recommending that a limited exclusion order and cease and desist orders should issue and that a bond of 100 percent should be imposed during the period of presidential review.
On December 29, 2015, MasterImage filed a petition for review challenging various findings in the final ID. On January 6, 2016, RealD filed a response to MasterImage's petition. On January 15, 2016, and January 19, 2016, MasterImage and RealD respectively filed post-RD statements on the public interest under Commission Rule 210.50(a)(4). The Commission did not receive any post-RD public interest comments from the public in response to the Commission notice issued on December 22, 2015. 80 FR 80795 (Dec. 28, 2015).
On February 16, 2016, the Commission determined to review the final ID in part and requested additional briefing from the parties on certain issues. 81 FR at 8744-45. The Commission also solicited briefing from the parties and the public on the issues of remedy, the public interest, and bonding.
On March 1, 2016, the parties filed initial written submissions addressing the Commission's questions and the issues of remedy, the public interest, and bonding. On March 11, 2016, the parties filed response briefs. No comments were received from the public.
On April 14, 2016, MasterImage filed a letter, notifying the Commission that, on that same day, the Patent Trial and Appeal Board of the U.S. Patent and Trademark Office (“PTAB”) issued a Final Written Decision finding claims 1, 6-10, and 18-20 of the '934 patent unpatentable.
The Commission has determined to extend the target date for completion of the investigation until June 1, 2016.
The Commission requests a response to the following question only:
1. What is the effect of the PTAB's Final Written Decision on the Commission's final determination, including any underlying findings, in this investigation? Please include in your response any effect on the issuance of remedial orders with respect to the asserted claims of the '455 and '296 patents and claim 11 of the '934 patent.
Any person desiring to submit a document to the Commission in confidence must request confidential treatment. All such requests should be directed to the Secretary to the Commission and must include a full statement of the reasons why the Commission should grant such treatment.
The authority for the Commission's determination is contained in section 337 of the Tariff Act of 1930, as amended (19 U.S.C. 1337), and in Part 210 of the Commission's Rules of Practice and Procedure (19 CFR part 210).
By order of the Commission.
On the basis of the record
Pursuant to section 207.18 of the Commission's rules, the Commission also gives notice of the commencement of the final phase of its investigation. The Commission will issue a final phase notice of scheduling, which will be published in the
On March 3, 2016, the American HFC Coalition and its individual members (Amtrol, Inc., West Warwick, Rhode Island; Arkema, Inc., King of Prussia, Pennsylvania; The Chemours Company FC LLC, Wilmington, Delaware; Honeywell International Inc., Morristown, New Jersey; Hudson Technologies, Pearl River, New York; Mexichem Fluor Inc., St. Gabriel, Louisiana; and Worthington Industries, Inc., Columbus, Ohio) and District Lodge 154 of the International Association of Machinists and Aerospace Workers filed a petition with the Commission and Commerce, alleging that an industry in the United States is materially injured and threatened with material injury by reason of LTFV imports of 1,1,1,2-Tetrafluoroethane (R-134a) from China. Accordingly, effective March 3, 2016, the Commission, pursuant to section 733(a) of the Tariff Act of 1930 (19 U.S.C. 1673b(a)), instituted antidumping duty investigation No. 731-TA-1313 (Preliminary).
Notice of the institution of the Commission's investigation and of a public conference to be held in connection therewith was given by posting copies of the notice in the Office
The Commission made this determination pursuant to section 733(a) of the Tariff Act of 1930 (19 U.S.C. 1673b(a)). It completed and filed its determination in this investigation on April 18, 2016. The views of the Commission are contained in USITC Publication 4806 (April 2016), entitled
By order of the Commission.
Employment and Training Administration (ETA), Department of Labor.
Notice.
The Department of Labor (DOL) is soliciting comments concerning a proposed extension for the authority to conduct the revision to the information collection request (ICR) titled, “Youthful Offender Grants Management Information System, (OMB Control No. 1205-0513).” This comment request is part of continuing Departmental efforts to reduce paperwork and respondent burden in accordance with the Paperwork Reduction Act of 1995 (PRA), 44 U.S.C. 3501
Consideration will be given to all written comments received by June 21, 2016.
A copy of this ICR with applicable supporting documentation; including a description of the likely respondents, proposed frequency of response, and estimated total burden may be obtained free by contacting Ann Leonetti by telephone at 202-693-2746, TTY 1-877-889-5627, (these are not toll-free numbers) or by email at
Submit written comments about, or requests for a copy of, this ICR by mail or courier to the U.S. Department of Labor, Employment and Training Administration, Attention: Ann Leonetti, Room N-4508, 200 Constitution Avenue NW., Washington, DC 20210; by email:
Ann Leonetti by telephone at 202-693-2746, TTY 1-877-889-5627, (these are not toll-free numbers) or by email at
44 U.S.C. 3506(c)(2)(A).
The DOL, as part of continuing efforts to reduce paperwork and respondent burden, conducts a pre-clearance consultation program to provide the general public and Federal agencies an opportunity to comment on proposed and/or continuing collections of information before submitting them to the OMB for final approval. This program helps to ensure requested data can be provided in the desired format, reporting burden (time and financial resources) is minimized, collection instruments are clearly understood, and the impact of collection requirements can be properly assessed.
Each year, the Department of Labor/Employment and Training Administration is appropriated funds for youthful offender demonstration projects. The Department of Labor uses these funds for a variety of multi-site demonstrations aimed at developing model programs for serving young offenders. The Department expects over the next few years to award 28 new Youthful Offender grants in various sets of demonstrations each year for two years of operation and up to one year of follow-up services and post-placement data collection. In any given year this will result in 28 grants in their first year of operation, 28 grants in their second year of operation, and 28 grants providing follow-up services and tracking post-placement outcomes, for a total of 84 grants collecting data each year.
This data collection request is to permit the Department of Labor to continue with revisions a management information system for these various sets of grantees. This request includes the collection of data by grantees on participant characteristics, services provided, and participant outcomes; the quarterly progress report submitted by grantees, the quarterly narrative report, and the annual recidivism report. This request continues a reporting and recordkeeping system for a minimum level of information collection that is necessary to comply with Equal Opportunity requirements, to hold Youthful Offender grantees appropriately accountable for the Federal funds they receive, including performance measures, and to allow the Department to fulfill its oversight and management responsibilities.
Revisions include adding questions on immigration status, welfare receipt, mental health treatment, and child support obligations to the data collected at intake; inserting several additional outcomes and clarifying some of the reporting items in the quarterly progress report; and broadening the recidivism survey to cover young adult offenders as well as juvenile offenders and to allow it to be filled out by the adult criminal justice system for young adult offenders. This request also adds the quarterly narrative report to be submitted by grantees. Burden hours for the quarterly narrative report were included in the supporting statement three years ago, but the report was left out of the final approval. This request also adds burden hours not included in the request three years ago for the time spent by grantees generating, reviewing, and correcting errors in the quarterly progress reports; increases the average burden to participants for the collection of intake data; and reduces the average burden hours from 30 to 16 for grantees to complete the quarterly narrative reports to make it consistent with the average hours approved for the quarterly narrative reports of similar Division of Youth services programs.
Section 185 of the Workforce Innovation and Opportunity Act authorizes the collection of data from grantees on the demographic characteristics of participants, activities provided, and program outcomes. This information collection is subject to the PRA. A Federal agency generally cannot conduct or sponsor a collection of information, and the public is generally not required to respond to an information collection, unless it is approved by the OMB under the PRA and displays a currently valid OMB Control Number. In addition, notwithstanding any other provisions of law, no person shall generally be subject to penalty for failing to comply with a collection of information that does not display a valid Control Number.
Interested parties are encouraged to provide comments to the contact shown in the
The DOL is particularly interested in comments that:
• Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;
• Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;
• Enhance the quality, utility, and clarity of the information to be collected; and
• Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology,
Employment and Training Administration (ETA), Labor.
Notice.
The Department of Labor, as part of its continuing effort to reduce paperwork and respondent burden conducts a preclearance consultation program to provide the general public and federal agencies with an opportunity to comment on proposed and/or continuing collections of information in accordance with the Paperwork Reduction Act of 1995 (PRA 95) [44 U.S.C. 3506(c)(2)(A)]. This program helps to ensure that requested data can be provided in the desired format, reporting burden (time and financial resources) is minimized, collection instruments are clearly understood, and the impact of collection requirements on respondents can be properly assessed. This notice utilizes standard clearance procedures in accordance with the Paperwork Reduction Act of 1995 and 5 CFR 1320.12.
Written comments must be submitted to the office listed in the
Submit written comments to U.S. Department of Labor, Employment and Training Administration, Office of Workforce Investment, attn: Athena R. Brown, Room N-4209, 200 Constitution Avenue NW., Washington, DC 20210. Telephone number: 202-693-3737 (this is not a toll-free number).
Each Indian and Native American (INA) grantee receiving WIOA, Section 166 funds (non-Pub. L. 102-477 grantees) to administer the Comprehensive Services Program (CSP) is required to submit a CSP Report (ETA Form 9084) on a quarterly basis. Grantees receiving WIOA Section 166 Supplemental Youth Services Program (SYSP) funds (non-Pub. L. 102-477 grantees) currently submit a SYSP Report (ETA Form 9085) semi-annually. This request is to extend the existing ETA Form 9084 and 9085 report submitted each quarter, or semi-annually, by INA grantees. The only revision to the ETA 9085 is to increase the age range for youth to twenty-four years old per the WIOA.
ETA requires the collection and reporting of data on eligible persons served under the WIOA, Section 166 CSP and SYSP to assess the performance and delivery of services. The current ETA forms 9084 and 9085 expire on September 30, 2016. This request is to extend the instructions and forms currently used until such time when the WIOA Final Rule and policy guidance are issued. Subsequently, a revised Information Collection Request will be required to comply with the Final Rule. In the interim, ETA will continue to administer the INA programs under the Workforce Investment Act (WIA) Final Rule.
The Department of Labor is particularly interested in comments which:
* Evaluate whether the proposed collection of information is necessary
* evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;
* enhance the quality, utility, and clarity of the information to be collected; and
* minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology,
Comments submitted in response to this comment request will be summarized and/or included in the request for Office of Management and Budget approval of the information collection request; they will also become a matter of public record.
Notice.
The Department of Labor, as part of its continuing effort to reduce paperwork and respondent burden, conducts a pre-clearance consultation program to provide the general public and Federal agencies with an opportunity to comment on proposed and/or continuing collections of information in accordance with the Paperwork Reduction Act of 1995 (PRA95) [44 U.S.C. 3506(c)(2)(A)]. This program helps to ensure that requested data can be provided in the desired format, reporting burden (time and financial resources) is minimized, collection instruments are clearly understood, and the impact of collection requirements on respondents can be properly assessed. The Bureau of Labor Statistics (BLS) is soliciting comments concerning the proposed revision of the “Report on Occupational Employment and Wages.” A copy of the proposed information collection request (ICR) can be obtained by contacting the individual listed below in the
Written comments must be submitted to the office listed in the
Send comments to Carol Rowan, BLS Clearance Officer, Division of Management Systems, Bureau of Labor Statistics, Room 4080, 2 Massachusetts Avenue NE., Washington, DC 20212. Written comments also may be transmitted by fax to 202-691-5111 (this is not a toll free number).
Carol Rowan, BLS Clearance Officer, at 202-691-7628 (this is not a toll free number). (See
The Occupational Employment Statistics (OES) survey is a Federal/State establishment survey of wage and salary workers designed to produce data on current occupational employment and wages. OES survey data assist in the development of employment and training programs established by the 1998 Workforce Investment Act (WIA) and further reinforced by the Workforce Innovation and Opportunity Act (WIOA) and the Perkins Vocational Education Act of 1998.
The OES program operates a periodic mail survey of a sample of non-farm establishments conducted by all fifty States, the District of Columbia, Guam, Puerto Rico, and the U.S. Virgin Islands. Over three-year periods, data on occupational employment and wages are collected by industry at the four- and five-digit North American Industry Classification System (NAICS) levels. The Department of Labor uses OES data in the administration of the Foreign Labor Certification process under the Immigration Act of 1990.
Office of Management and Budget clearance is being sought for the Occupational Employment Statistics (OES) program. Occupational employment data obtained by the OES survey are used to develop information regarding current and projected employment needs and job opportunities. These data assist in the development of State vocational education plans. OES wage data provide a significant source of information to support a number of different Federal, State, and local efforts.
As part of an ongoing effort to reduce respondent burden, OES has several electronic submission options which are available to respondents. Respondents have the ability to submit data by email, or fillable online forms. In many cases, a respondent can submit existing payroll records and would not need to submit a survey form.
The Bureau of Labor Statistics is particularly interested in comments that:
• Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility.
• Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used.
• Enhance the quality, utility, and clarity of the information to be collected.
• Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology,
Comments submitted in response to this notice will be summarized and/or included in the request for Office of Management and Budget approval of the information collection request; they also will become a matter of public record.
Office of Management and Budget.
Notice and request for comments.
In compliance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3501,
The first notice of this information collection request, as required by the Paperwork Reduction act, was published in the
In developing the current form, OMB has identified some potential duplication in the current process for reporting the SF-SAC and the Schedule of Expenditure for Financial Assistance (SEFA). Currently, awardees subject to Single Audit reporting create a Schedule of Expenditures of Federal Awards (SEFA) and use it to complete their SF-FAC through the Federal Audit Clearing (FAC) House. The SEFA and the SF-SAC contain similar data which is submitted to FAC in two formats.
Therefore, as a part of the DATA Act Section 5 Pilot to Reduce Recipient Reporting Burden, OMB and the Department of Health and Humand Services (DATA Act Program Management Office (DAP)) would like to test a more streamlined process for submitting the SEFA. Under this test, participants would be provided the opportunity to use an expanded SF-SAC Concept Form which includes a additional information related to the SEFA notes . The FAC would then generate a customizable SEFA that a recipient could download, modify, and include in their Annual Single Audit Report.
DAP has developed a detailed draft sampling process to help identify and recruit potential participants for the Test Model. DAP has determined that it will target a minimum of 42 participants per Test Model. In order to achieve this goal, DAP will perform targeted outreach to a sample of Federal award recipients from the USAspending.gov database for FY15 reflecting the diversity of the recipient community. DAP target recipients who meet the Single Audit criterion of expending $750,000 or more annually in federal funds. Recognizing that PRA requires that OMB approve federally sponsored data collection of the public, DAP will reach out to an identified sample of 702 recipients with information on the Section 5 Grants Pilot and a Test Model participation form to request information from recipients after receiving OMB PRA clearance. DAP expects to receive PRA clearance for this data collection in late winter/early spring 2016. Interested participants will be requested to read brief descriptions of the Test Models and indicate all Test Models in which they would like to participate. DAP will continuously monitor recipient responses, feedback, and preferences. DAP will assign interested recipients to Test Models based on indicated interest while maintaining diversity amongst recipients for each Test Model. DAP will follow up and engage with recipients as necessary in an effort to achieve the stated goal of 42 participants per Test Model. DAP is also collecting contact information for recipients interested in Test Model participation through voluntary self-nomination and third-party recommendations.
The concept form is included under this notice and will be used for the pilot project. We are
Submit comments on or before May 23, 2016. Late comments will be considered to the extent practicable.
Electronic mail comments may be submitted to: Gilbert Tran at
All responses will be summarized and included in the request for OMB approval. All comments will also be a matter of public record.
Due to potential delays in OMB's receipt and processing of mail sent through the U.S. Postal Service, we encourage respondents to submit comments electronically to ensure timely receipt. We cannot guarantee that mailed comments will be received before the comment closing date.
Gilbert Tran, Office of Federal Financial Management, Office of Management and Budget, (202) 395-3052. The proposed revisions to the Information Collection Form, Form SF-SAC can be obtained by contacting the Office of Federal Financial Management as indicated above or by download from the OMB Grants Management home page on the Internet at
The Members of the National Council on Disability (NCD) will hold a quarterly meeting on Thursday, May 5, 2016, 1:00 p.m.-4:00 p.m. (Eastern Daylight Time), and on Friday, May 6, 2016, 9:00 a.m.-4:30 p.m. (Eastern Daylight Time) in Washington, DC.
The meeting will occur at a different location each day. On Thursday, the quarterly meeting will be held at the White House Old Executive Office Building. The location, due to security clearance considerations, will not be open to the public for in-person attendance, however the quarterly meeting's proceedings will be available by phone to all interested parties (in a listen-only capacity with the exception of the public comment period). Interested parties may access Thursday's meeting's proceedings by phone by using the following call-in number: 888-428-9490; passcode: 9482562. If asked, the call host's name is Clyde Terry. On Friday, the quarterly meeting will be held at the Access Board Conference Room, 1331 F Street NW., Suite 800, Washington, DC. Interested parties may join the meeting in person or by phone in a listening-only capacity (with the exception of the public comment period) using the following call-in number: 888-428-9490; passcode: 9482562. If asked, the call host's name is Clyde Terry.
The Council will host a strategy session on legislative and other next steps for its 2012 “Rocking the Cradle” report on the rights of parents with disabilities and their children; and hear policy presentations on the topics of mental health services in higher education, and Medicaid managed care and the direct care workforce. The Council will also receive reports from its standing committees; and receive public comment during two town halls, on the topics of mental health services in higher education; and challenges of the direct care workforce.
The times provided below are approximations for when each agenda item is anticipated to be discussed (all times Eastern):
To better facilitate NCD's public comment, any individual interested in providing public comment is asked to register his or her intent to provide comment in advance by sending an email to
Anne Sommers, NCD, 1331 F Street NW., Suite 850, Washington, DC 20004; 202-272-2004 (V), 202-272-2074 (TTY).
A CART streamtext link has been arranged for this teleconference meeting. The web link to access CART on Thursday, May 5, 2016 is:
Those who plan to attend the meeting in-person and require accommodations should notify NCD as soon as possible to allow time to make arrangements. To help reduce exposure to fragrances for those with multiple chemical sensitivities, NCD requests that all those attending the meeting in person refrain from wearing scented personal care products such as perfumes, hairsprays, and deodorants.
National Credit Union Administration (NCUA).
Notice and request for comment.
NCUA, as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to comment on this reinstatement of a previously approved collection, as required by Paperwork Reduction Act of 1995 (Pub. L. 104-13, 44 U.S.C. Chapter 35). The purpose of this notice is to allow for 60 days of public comment. NCUA is soliciting comments on the reinstatement of the information collection described below.
Comments should be received on or before June 21, 2016 to be assured consideration.
Interested persons are invited to submit written comments on the information collection to Dawn Wolfgang, National Credit Union Administration, 1775 Duke Street, Alexandria, Virginia 22314-3428; Fax No. 703-519-8579; or Email at
Requests for additional information should be directed to the address above.
NCUA is requesting reinstatement of the previously approved collection of information related to the Reverse Mortgage Guidance which sets forth standards intended to ensure that financial institutions effectively assess and manage the compliance and reputation risks associated with reverse mortgage products. The information collection will allow NCUA to evaluate the adequacy of a federally-insured credit union's internal policies and procedures as they relate to reverse mortgage products.
Comments submitted in response to this notice will be summarized and included in the request for Office of Management and Budget approval. All comments will be a matter of public record. The public is invited to submit comments concerning: (a) Whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; (b) the accuracy of the agency's estimate of the burden of the collection of information, including the validity of the methodology and assumptions used; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of the information on the respondents, including the use of automated collection techniques or other forms of information technology.
April 18, 2016 (81 FR 22650).
11:15 a.m., Thursday, April 21, 2016.
Board Room, 7th Floor, Room 7047, 1775 Duke Street, Alexandria, VA 22314-3428.
Closed.
Pursuant to the provisions of the “Government in Sunshine Act” notice is hereby given that the NCUA Board gave previous notice of the regular meeting of the NCUA Board scheduled for April 21, 2016. Prior to the meeting, on April 20, 2016, with less than seven days' notice to the public, the NCUA Board unanimously determined that agency business required changing the previously announced closed meeting time from 11:15 a.m. to 9:00 a.m. No earlier notice of the change was possible.
9:00 a.m., Thursday, April 21, 2016.
Gerard Poliquin, Secretary of the Board, Telephone: 703-518-6304.
National Endowment for the Arts, National Foundation on the Arts and Humanities.
Notice of meeting.
Pursuant to the Federal Advisory Committee Act, as amended, notice is hereby given that four meetings of the Arts Advisory Panel to the National Council on the Arts will be held by teleconference.
All meetings are Eastern time and ending times are approximate:
National Endowment for the Arts, Constitution Center, 400 7th St. SW., Washington, DC 20506.
Further information with reference to these meetings can be obtained from Ms. Kathy Plowitz-Worden, Office of Guidelines & Panel Operations, National Endowment for the Arts, Washington, DC 20506;
The closed portions of meetings are for the purpose of Panel review, discussion, evaluation, and recommendations on financial assistance under the National Foundation on the Arts and the Humanities Act of 1965, as amended, including information given in confidence to the agency. In accordance with the determination of the Chairman of February 15, 2012, these sessions will be closed to the public pursuant to subsection (c)(6) of section 552b of title 5, United States Code.
In accordance with the Federal Advisory Committee Act (Pub. L. 92-463 as amended), the National Science Foundation announces the following meeting:
In accordance with the Federal Advisory Committee Act (Pub. L. 92-463 as amended), the National Science Foundation announces the following meeting:
In accordance with the Federal Advisory Committee Act (Pub. L. 92-463, as amended), the National Science Foundation (NSF) announces the following meeting:
In accordance with the Federal Advisory Committee Act (Pub. L. 92-463 as amended), the National Science Foundation announces the following meeting:
Nuclear Regulatory Commission.
Draft interim staff guidance; request for comment.
The U.S. Nuclear Regulatory Commission (NRC) is soliciting public comment on its draft Japan Lessons-Learned Division Interim Staff Guidance (JLD-ISG), JLD-ISG-2016-01, “Guidance for Activities Related to Near-Term Task Force Recommendation 2.1, Flooding Hazard Reevaluation; Focused Evaluation and Integrated Assessment.” This draft JLD-ISG revision provides guidance and clarification to assist operating power reactor respondents and holders of construction permits under the NRC's regulations with the performance of the focused evaluations and revised integrated assessments for external flooding.
Submit comments by May 23, 2016. Comments received after this date will be considered if it is practical to do so, but the Commission is able to ensure consideration only for comments received on or before this date.
You may submit comments by any of the following methods (unless
•
•
For additional direction on obtaining information and submitting comments, see “Obtaining Information and Submitting Comments” in the
Eric Bowman, Office of Nuclear Reactor Regulation, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001; telephone: 301-415-2963; email:
Please refer to Docket ID NRC-2016-0084 when contacting the NRC about the availability of information for this action. You may obtain publicly-available information related to this action by any of the following methods:
•
•
•
Please include Docket ID NRC-2016-0084 in your comment submission.
The NRC cautions you not to include identifying or contact information that you do not want to be publicly disclosed in your comment submission. The NRC posts all comment submissions at
If you are requesting or aggregating comments from other persons for submission to the NRC, then you should inform those persons not to include identifying or contact information that they do not want to be publicly disclosed in their comment submission. Your request should state that the NRC does not routinely edit comment submissions to remove such information before making the comment submissions available to the public or entering the comment submissions into ADAMS.
Following the events at the Fukushima Dai-ichi nuclear power plant on March 11, 2011, the NRC established a senior-level agency task force referred to as the Near-Term Task Force (NTTF). The NTTF was tasked with conducting a systematic and methodical review of the NRC regulations and processes, and determining if the agency should make additional improvements to these programs in light of the events at Fukushima Dai-ichi. As a result of this review, the NTTF developed a comprehensive set of recommendations, documented in SECY-11-0093, “Recommendations for Enhancing Reactor Safety in the 21st Century, the Near-Term Task Force Review of Insights from the Fukushima Dai-ichi Accident,” dated July 12, 2011. These recommendations were enhanced by the NRC staff following interactions with stakeholders. Documentation of the staff's efforts is contained in SECY-11-0124, dated September 9, 2011, and SECY-11-0137, dated October 3, 2011.
As directed by the Commission's SRM for SECY-11-0093, the NRC staff reviewed the NTTF recommendations within the context of the NRC's existing regulatory framework and considered the various regulatory vehicles available to the NRC to implement the recommendations. In SECY-11-0124 and SECY-11-0137, the staff established the prioritization of the recommendations. After receiving the Commission's direction in SRM-SECY-11-0124 and SRM-SECY-11-0137, the NRC staff issued a request for information pursuant to section 50.54(f) of title 10 of the
In COMSECY-14-0037, dated November 21, 2014, the NRC staff requested that the Commission review and approve changes to revise the Recommendation 2.1 flooding assessments and integrate the Phase 2 decision-making into the development and implementation of mitigating strategies in accordance with Order EA-12-049 and the related Mitigation of Beyond-Design-Basis Events rulemaking.
In SRM-COMSECY-14-0037, the Commission disapproved this recommendation. Instead, the Commission instructed the staff to develop a closure plan for the flooding reevaluation activities and to reassess the existing guidance for performing a Phase 1 integrated assessment in order to focus on those plants with the most potential for safety benefits.
In COMSECY-15-0019, the staff provided revised guidance for performing a Phase 1 integrated assessment and described a modified process for identifying the list of plants that would be required to perform an integrated assessment. The process proposed by the staff included the development of a graded, risk-informed and performance-based approach consistent with Commission direction to focus on those plants with the greatest potential need for safety enhancements. Specifically, the process included consideration and evaluation of local intense precipitation by performing a focused evaluation of the impact of the
In SRM-COMSECY-15-0019, the Commission approved the staff's plans to modify the approach for integrated assessments to implement a graded approach for determining the need for, and prioritization and scope of, plant-specific integrated assessments. As discussed in COMSECY-15-0019, the majority of sites with reevaluated flooding hazards exceeding the design-basis flood are expected to screen out from the integrated assessment process. The licensees will instead provide focused evaluations to ensure appropriate actions are taken and that these actions are effective and reasonable.
The Nuclear Energy Institute (NEI) submitted guidance NEI 16-05, “External Flooding Assessment Guidelines,” Revision 0, on April 12, 2016. The guidance is an industry-developed methodology that describes the flooding impact assessment process, which is intended to meet the requested information of an integrated assessment, as described in the document titled, “Request for Information Pursuant to Title 10 of the
Draft ISG JLD ISG 2016-01 is being issued to describe to stakeholders methods acceptable to the staff for performance of the focused evaluations and revised integrated assessments and describe some exceptions and clarifications to NEI 16-05, Revision 0.
This guidance is not intended for use in design-basis applications or in regulatory activities beyond the scope of performing the focused evaluations and integrated assessment part of NTTF Recommendation 2.1 flooding activities. This ISG is being issued in draft form for public comment to involve the public in development of the implementation guidance. Compliance with the ISG is not required.
The documents identified in the following table are available to interested persons through one or more of the following methods, as indicated.
The NRC may post materials related to this document, including public comments, on the Federal rulemaking Web site at
By this action, the NRC is requesting public comments on draft ISG JLD-ISG-2016-01. This draft JLD-ISG proposes guidance related to the performance of a focused evaluation and integrated assessment as part of NTTF 2.1 flooding activities. The NRC staff will make a final determination regarding issuance of the JLD-ISG after it considers any public comments received in response to this request.
For the Nuclear Regulatory Commission.
Nuclear Regulatory Commission.
License amendment application; opportunity to request a hearing and to petition for leave to intervene; correction.
The U.S. Nuclear Regulatory Commission (NRC) is correcting a notice that was published in the
The correction is effective April 22, 2016.
Please refer to Docket ID NRC-2015-0162 when contacting the NRC about the availability of information regarding this document. You may obtain publicly-available information related to this document using any of the following methods:
•
•
•
Jeanne Dion, Office of Nuclear Reactor Regulation, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001; telephone: 301-415-1349, email:
In the FR on July 7, 2015, in FR Doc. 2015-16541, on page 38755, column 1, line 1, correct “amendment dated March 31, 2015, as supplemented on May 27 and June 15, 2015 (available in ADAMS under Accession Nos. ML15098A446, ML15147A611, and ML15167A359, respectively)” to read “amendment dated March 31, 2015, as supplemented on April 28, May 27, and June 15, 2015 (available in ADAMS under Accession Nos. ML15098A446, ML15124A334, ML15147A611, and ML15167A359, respectively).”
For the Nuclear Regulatory Commission.
Pursuant to Title 10 of the
A request for a hearing or petition for leave to intervene may be filed within thirty days after publication of this notice in the
A request for a hearing or petition for leave to intervene may be filed with the NRC electronically in accordance with NRC's E-Filing rule promulgated in August 2007, 72 FR 49139; August 28, 2007. Information about filing electronically is available on the NRC's public Web site at
In addition to a request for hearing or petition for leave to intervene, written comments, in accordance with 10 CFR 110.81, should be submitted within thirty days after publication of this notice in the
The information concerning this application for an export license follows.
For the Nuclear Regulatory Commission.
Pursuant to 10 CFR 110.70 (b) “Public Notice of Receipt of an Application,” please take notice that the Nuclear Regulatory Commission (NRC) has received the following request for an import license. Copies of the request are available electronically through Agencywide Documents Access and Management System and can be accessed through the Public Electronic Reading Room link
A request for a hearing or petition for leave to intervene may be filed within thirty days after publication of this notice in the
A request for a hearing or petition for leave to intervene may be filed with the NRC electronically in accordance with NRC's E-Filing rule promulgated in August 2007, 72 FR 49139; August 28, 2007. Information about filing electronically is available on the NRC's public Web site at
In addition to a request for hearing or petition for leave to intervene, written comments, in accordance with 10 CFR 110.81, should be submitted within thirty days after publication of this notice in the FR to Office of the Secretary, U.S. Nuclear Regulatory Commission, Washington, DC 20555, Attention: Rulemaking and Adjudications.
The information concerning this import license application follows.
For the Nuclear Regulatory Commission.
Nuclear Regulatory Commission.
Standard review plan draft section revision; request for comment.
The U.S. Nuclear Regulatory Commission (NRC) is soliciting public comment on draft NUREG-0800, “Standard Review Plan for the Review of Safety Analysis Reports for Nuclear Power Plants: LWR Edition,” Section 5.4.2.1, “Steam Generator Materials and Design.” The NRC seeks comments on the proposed draft section revision of the Standard Review Plan (SRP),
Comments must be filed no later than May 23, 2016. Comments received after this date will be considered, if it is practical to do so, but the Commission is able to ensure consideration only for comments received on or before this date.
You may submit comments by any of the following methods (unless this document describes a different method for submitting comments on a specific subject):
•
•
For additional direction on obtaining information and submitting comments, see “Obtaining Information and Submitting Comments” in the
Carolyn Lauron, telephone: 301-415-2736, email: Carolyn
Please refer to Docket ID NRC-2016-0045 when contacting the NRC about the availability of information for this action. You may obtain publicly-available information related to this action by any of the following methods:
•
•
•
Please include Docket ID NRC-2016-0045 in your comment submission.
The NRC cautions you not to include identifying or contact information that you do not want to be publicly disclosed in your comment submission. The NRC posts all comment submissions at
If you are requesting or aggregating comments from other persons for submission to the NRC, then you should inform those persons not to include identifying or contact information that they do not want to be publicly disclosed in their comment submission. Your request should state that the NRC does not routinely edit comment submissions to remove such information before making the comment submissions available to the public or entering the comment submissions into ADAMS.
The NRC seeks public comment on the proposed draft section revision SRP Section 5.4.2.1. The changes to this SRP section reflect current staff review methods and practices based on lessons learned from NRC reviews of design certification and combined license applications completed since the last revision of this section.
Following the NRC staff's evaluation of public comments, the NRC intends to finalize SRP Section 5.4.2.1, Revision 4, in ADAMS and post it on the NRC's public Web site at
Issuance of these draft SRP sections, if finalized, would not constitute Backfitting as defined in § 50.109 of title 10 of the
1.
The SRP provides internal guidance to the NRC staff on how to review an application for NRC regulatory approval in the form of licensing. Changes in internal staff guidance are not matters for which either nuclear power plant applicants or licensees are protected under either the Backfit Rule or the issue finality provisions of 10 CFR part 52.
2.
The NRC staff does not intend to impose or apply the positions described in the draft SRP to existing licenses and regulatory approvals. Hence, the issuance of a final SRP—even if considered guidance within the purview of the issue finality provisions in 10 CFR part 52—would not need to be evaluated as if it were a Backfit or as being inconsistent with issue finality provisions. If, in the future, the NRC staff seeks to impose a position in the SRP on holders of already issued licenses in a manner that does not provide issue finality as described in the applicable issue finality provision, then the staff must make the showing as set forth in the Backfit Rule or address the criteria for avoiding issue finality as described in the applicable issue finality provision.
3.
Applicants and potential applicants are not, with certain exceptions, protected by either the Backfit Rule or any issue finality provisions under 10 CFR part 52. Neither the Backfit Rule nor the issue finality provisions under 10 CFR part 52—with certain exclusions—were intended to apply to every NRC action that substantially changes the expectations of current and future applicants. The exceptions to the general principle are applicable whenever an applicant references a 10 CFR part 52 license (
The NRC staff does not, at this time, intend to impose the positions represented in the draft SRP in a manner that is inconsistent with any issue finality provisions. If, in the future, the staff seeks to impose a position in the draft SRP in a manner that does not provide issue finality as described in the applicable issue finality provision, then the staff must address the criteria for avoiding issue finality as described in the applicable issue finality provision.
For the Nuclear Regulatory Commission.
Postal Regulatory Commission.
Notice.
The Commission is noticing a recent Postal Service filing concerning an amendment to Priority Mail Contract 77 negotiated service agreement. This notice informs the public of the filing, invites public comment, and takes other administrative steps.
Submit comments electronically via the Commission's Filing Online system at
David A. Trissell, General Counsel, at 202-789-6820.
On April 15, 2016, the Postal Service filed notice that it has agreed to an amendment to the existing Priority Mail Contract 77 negotiated service agreement approved in this docket.
The Postal Service also filed the unredacted Amendment under seal. The Postal Service seeks to incorporate by reference the Application for Non-Public Treatment originally filed in this docket for the protection of information that it has filed under seal. Notice at 1.
The Amendment modifies the rates received by the contract partner after June 30, 2016.
The Postal Service intends for the Amendment to become effective 2 business days after the date that the Commission completes its review of the Notice. Notice at 1. The Postal Service asserts that the Amendment will not materially affect cost coverage; therefore, the supporting financial documentation and certification originally filed in this docket remain applicable.
The Commission invites comments on whether the changes presented in the Postal Service's Notice are consistent with the policies of 39 U.S.C. 3632, 3633, or 3642, 39 CFR 3015.5, and 39 CFR part 3020, subpart B. Comments are due no later than April 25, 2016. The public portions of these filings can be accessed via the Commission's Web site (
The Commission appoints Curtis E. Kidd to represent the interests of the general public (Public Representative) in this docket.
1. The Commission reopens Docket No. CP2014-31 for consideration of matters raised by the Postal Service's Notice.
2. Pursuant to 39 U.S.C. 505, the Commission appoints Curtis E. Kidd to serve as an officer of the Commission (Public Representative) to represent the interests of the general public in this proceeding.
3. Comments are due no later than April 25, 2016.
4. The Secretary shall arrange for publication of this order in the
By the Commission.
Postal Regulatory Commission.
Notice.
The Commission is noticing a recent Postal Service filing concerning an amendment to Priority Mail Contract 136 negotiated service agreement. This notice informs the public of the filing, invites public comment, and takes other administrative steps.
Submit comments electronically via the Commission's Filing Online system at
David A. Trissell, General Counsel, at 202-789-6820.
On April 15, 2016, the Postal Service filed notice that it has agreed to an amendment to the existing Priority Mail Contract 136 negotiated service agreement approved in this docket.
The Postal Service also filed the unredacted Amendment. Notice at 1. The Postal Service seeks to incorporate by reference the Application for Non-Public Treatment originally filed in this docket for the protection of information that it has filed under seal.
The Amendment changes terms for the annual adjustment provision of the contract.
The Postal Service intends for the Amendment to become effective one business day after the date that the Commission completes its review of the Notice.
The Commission invites comments on whether the changes presented in the Postal Service's Notice are consistent with the policies of 39 U.S.C. 3632, 3633, or 3642, 39 CFR 3015.5, and 39 CFR part 3020, subpart B. Comments are due no later than April 25, 2016. The public portions of these filings can be accessed via the Commission's Web site (
The Commission appoints Cassie D'Souza to represent the interests of the general public (Public Representative) in this docket.
1. The Commission reopens Docket No. CP2015-110 for consideration of matters raised by the Postal Service's Notice.
2. Pursuant to 39 U.S.C. 505, the Commission appoints Cassie D'Souza to serve as an officer of the Commission (Public Representative) to represent the interests of the general public in this proceeding.
3. Comments are due no later than April 25, 2016.
4. The Secretary shall arrange for publication of this order in the
By the Commission.
Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (the “Act”),
The Exchange filed a proposal to adopt Exchange Rule 14.10 setting forth additional requirements for the listing of securities that are issued by the Exchange or any of its affiliates as well as the monitoring of such securities' trading activity on the Exchange. Proposed Rule 14.10 is based on Bats BZX Exchange, Inc. (“BZX”) Rule 14.3(e), which was recently amended and filed for immediate effectiveness with the Commission.
The text of the proposed rule change is available at the Exchange's Web site at
In its filing with the Commission, the Exchange included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in Sections A, B, and C below, of the most significant parts of such statements.
The Exchange is proposing to adopt Rule 14.10 setting forth reporting requirements on the Exchange should the Exchange or EDGA Affiliate list a security on the Exchange (the “Affiliate Security”). Proposed Rule 14.10(a)(1) would define “EDGA Affiliate” as “the Exchange and any entity that directly or indirectly, through one or more intermediaries, controls, is controlled by, or is under common control with the Exchange, where “control” means that one entity possesses, directly or indirectly, voting control of the other entity either through ownership of capital stock or other equity securities or through majority representation on the board of directors or other management body of such entity.” Proposed Rule 14.10(a)(2) would define “Affiliate Security” as “any security issued by an EDGA Affiliate or any Exchange-listed option on any such security, with the exception of Portfolio Depositary Receipts as defined in Rule 14.8(d) and Investment Company Units as defined in Rule 14.2.”
In the event that an EDGA Affiliate seeks to list an Affiliate Security, paragraph (b)(1) of proposed Rule 14.10 would require that prior to the initial listing of the Affiliate Security on the Exchange, Exchange personnel shall determine that such security satisfies the Exchange's rules for listing, and such finding must be approved by the Regulatory Oversight Committee of the Exchange's Board of Directors.
Proposed paragraph (b)(2) of proposed Rule 14.10 would state that throughout the continued listing of the Affiliate Security on the Exchange, the Exchange will prepare a quarterly report for the Regulatory Oversight Committee of the Exchange's Board of Directors and that such report describe the Exchange's monitoring of the Affiliate Security's compliance with the Exchange's listing standards. Sub-paragraph (A) of proposed Rule 14.10(b)(2) would require the report include a description of the Affiliate Security's compliance with the Exchange's minimum share price requirement, and, sub-paragraph (B) would require the report to describe the
Sub-paragraph (3) of proposed Rule 14.10(b) would require the Exchange to commission an annual review and report by an independent accounting firm of the compliance of the Affiliate Security with the Exchange's listing requirements. The Exchange would be required to promptly furnish a copy of this annual report to the Regulatory Oversight Committee of the Exchange's Board of Directors.
Sub-paragraph (4) of proposed Rule 14.10(b) would state that in the event the Exchange determines that the EDGA Affiliate is not in compliance with any of the Exchange's listing standards, the Exchange is required to notify the issuer of such non-compliance promptly and request a plan of compliance. The Exchange would also be required to file a report with the Commission within five business days of providing such notice to the issuer of its non-compliance. The required report would identify the date of the non-compliance, type of non-compliance, and any other material information conveyed to the issuer in the notice of non-compliance. Within five business days of receipt of a plan of compliance from the issuer, the Exchange would again be required to notify the Commission of such receipt, whether the plan of compliance was accepted by the Exchange or what other action was taken with respect to the plan and the time period provided to regain compliance with the Exchange's listing standards, if any.
Sub-paragraph (c) of proposed Rule 14.10 would require that throughout the trading of an Affiliate Security on the Exchange, the Exchange prepare a quarterly report on the Affiliate Security for the Regulatory Oversight Committee of the Exchange's Board of Directors that describes the Exchange's monitoring of the trading of the Affiliate Security, including summaries of all related surveillance alerts, complaints, regulatory referrals, trades cancelled or adjusted pursuant to Exchange Rules, investigations, examinations, formal and informal disciplinary actions, exception reports and trading data used to ensure the Affiliate Security's compliance with the Exchange's listing and trading rules.
Lastly, paragraph (d) of proposed Rule 14.10 would require the Exchange to promptly provide a copy of the reports required by sub-paragraphs (b) and (c) described above to the Commission.
The listing of an Affiliate Security or where an Affiliate Security is traded on the Exchange could potentially create a conflict of interest between the Exchange's self-regulatory responsibility to vigorously oversee the listing and trading of the stock on its market, and its own commercial or economic interests. Such “self-listing” may raise questions as to the Exchange's ability to independently and effectively enforce its rules against an affiliate or the operator/owner of its facility. In addition, such listing has the potential to exacerbate possible conflicts that may arise when the Exchange oversees competitors that may also be listed or traded on the Exchange. The Exchange believes that the proposed rule change, by requiring heightened reporting by the Exchange to the Regulatory Oversight Committee of the Exchange's Board of Directors and the Commission with respect to the Exchange's oversight of the listing and trading on the Exchange of any EDGA Affiliate Security, will help protect against any concern that the Exchange will not effectively enforce its rules with respect to the listing and trading of these securities. In addition, the requirements that an independent accounting firm review such issuer's compliance with the Exchange's listing standards adds a degree of independent oversight to the Exchange's regulation of the listing of these securities and should help mitigate against any potential or actual conflicts of interest. The Exchange also believes that these additional requirements contained in the proposed rule change would provide additional assurance that any Affiliate Securities listed and traded on the Exchange by an EDGA Affiliate comply with the Exchange's listing standards and trading rules on an on-going basis. Finally, the Exchange believes that the proposed rule change would eliminate any perception of a potential conflict of interest if an EDGA Affiliate seeks to list a security on the Exchange or if an Affiliate Security is traded on the Exchange.
The Exchange believes that its proposal is consistent with the requirements of the Act and the rules and regulations thereunder that are applicable to a national securities exchange, and, in particular, with the requirements of Section 6(b) of the Act.
The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The proposed rule change is not designed to address any competitive issues, but rather set forth the Exchange's controls that are in place to address the potential conflicts of interest that may arise in the listing of Affiliate Securities on the Exchange.
Written comments were neither solicited nor received.
The Exchange has filed the proposed rule change pursuant to Section
A proposed rule change filed under Rule 19b-4(f)(6) under the Act
At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings to determine whether the proposed rule should be approved or disapproved.
Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:
• Use the Commission's Internet comment form (
• Send an email to
• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.
For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
Notice is hereby given that, pursuant to the Paperwork Reduction Act of 1995 (44 U.S.C. 3501
Regulation E (17 CFR 230.601-230.610a) exempts from registration under the Securities Act of 1933 (15 U.S.C. 77a
Respondents to this collection of information include SBICs and BDCs making an offering of securities under Regulation E. Each respondent's reporting burden under rule 607 relates to the burden associated with filing its sales material electronically. The burden of filing electronically, however, is negligible and there have been no filings made under this rule, so this collection of information does not impose any burden on the industry. However, we are requesting one annual response and an annual burden of one hour for administrative purposes. The estimate of average burden hours is made solely for purposes of the Paperwork Reduction Act and is not derived from a quantitative, comprehensive, or even representative survey or study of the burdens associated with Commission rules and forms.
The requirements of this collection of information are mandatory. Responses will not be kept confidential. An agency may not conduct or sponsor, and a person is not required to respond to a collection of information unless it displays a currently valid control number.
The public may view the background documentation for this information collection at the following Web site,
Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (the “Act”),
The Exchange is proposing a rule change to make a series of changes to paragraph (e) of Exchange Rule 14.3 regarding the requirements for the listing of securities that are issued by the Exchange or any of its affiliates.
The text of the proposed rule change is available at the Exchange's Web site at
In its filing with the Commission, the Exchange included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in Sections A, B, and C below, of the most significant parts of such statements.
The Exchange is proposing to make a series of changes to paragraph (e) of Exchange Rule 14.3 regarding the reporting requirements on the Exchange should the Exchange or BZX Affiliate
Exchange Rule 14.3(e)(1)(B) currently defines Affiliate Security as “any security issued by a BZX Affiliate, with the exception of Portfolio Depository Receipts as defined in Rule 14.11(b) and Index Fund Shares as defined in Rule 14.11(c).” The Exchange proposes to expand the definition of Affiliate Security to include any Exchange-listed option on any security issued by a BZX Affiliate.
In the event that a BZX Affiliate seeks to list an Affiliate Security, paragraph (e)(2) of Rule 14.3 requires that prior to the initial listing of the Affiliate Security on the Exchange, Exchange personnel shall determine that such security satisfies the Exchange's rules for listing, and such finding must be approved by the Regulatory Oversight Committee of the Exchange's Board of Directors. The Exchange proposes to renumber this paragraph as (e)(2)(A) and rename paragraph (2) as “Affiliate Securities Listed on the Exchange.” The Exchange does not propose any
Current Rule 14.3(e)(3) states that throughout the continued listing of the Affiliate Security on the Exchange, the Exchange will prepare a quarterly report for the Regulatory Oversight Committee of the Exchange's Board of Directors. Current sub-paragraph (i) of the Rule 14.3(e)(3) requires that the report describe the Exchange's monitoring of the Affiliate Security's compliance with the Exchange's listing standards, including, as described in current sub-paragraph (i)(a), the Affiliate Security's compliance with the Exchange's minimum share price requirement, and, as described under current sub-paragraph (i)(b) the Affiliate Security's compliance with each of the quantitative continued listing requirements.
The Exchange proposes to renumber paragraph (3)(A) of Rule 14.3(e) as paragraph as (2)(B) and reformat this section of the rule as follows. Paragraph (2)(B) would state that throughout the continued listing of the Affiliate Security on the Exchange, the Exchange will prepare a quarterly report for the Regulatory Oversight Committee of the Exchange's Board of Directors describing the Exchange's monitoring of the Affiliate Security's compliance with the Exchange's listing standards. Paragraph (2)(B)(i) would require that the report include a description of the Affiliate Security's compliance with the Exchange's minimum share price requirement and paragraph (2)(B)(ii) would require that the report include a description of the Affiliate Security's compliance with each of the quantitative continued listing requirements. The Exchange does not propose any substantive changes to this section of the rule.
Current sub-paragraph (ii) of Rule 14.3(e)(3)(A) states that the report shall also describe the Exchange's monitoring of the trading of the Affiliate Security, including summaries of all related surveillance alerts, complaints, regulatory referrals, trades cancelled or adjusted pursuant to Rule 11.17, investigations, examinations, formal and informal disciplinary actions, exception reports and trading data used to ensure the Affiliate Security's compliance with the Exchange's listing and trading rules. The Exchange proposes to relocate current sub-paragraph (3)(A)(ii) under new sub-paragraph (3) to Rule 14.3(e). The Exchange proposes to include additional language specifying that the Exchange shall prepare a quarterly report on the Affiliate Security for the Regulatory Oversight Committee of the Exchange's Board of Directors that describes the activity described in the sub-paragraph. The Exchange proposes to include additional language that these requirements will be applicable throughout the trading of the Affiliate Security on the Exchange. Current sub-paragraph (3)(B) of Rule 14.3(e) also states that to the extent the Exchange uses Exchange staff to conduct surveillance of trading activity on the Exchange, the Exchange is required to engage an independent third party once a year to review and prepare a report regarding surveillance of the Affiliate Security and promptly forward to the Regulatory Oversight Committee of the Exchange's Board of Directors and the Commission a copy of the report prepared by the independent third party. The Exchange proposes to eliminate the requirements of current sub-paragraph (3)(B) based on the fact that this requirement is not applicable on other national securities exchanges with similar rules regarding the listing or trading of an affiliate security.
Current Rule 14.3(e)(3)(A) also requires that the Exchange to promptly furnish a copy of the quarterly report required by current paragraph (e)(3)(A) to the Commission. The Exchange proposes to renumber this paragraph as (e)(4) and revise it to state that a copy of the reports required by proposed renumbered sub-paragraphs (2) and (3) of Rule 14.3(e), discussed above, will be forwarded promptly to the Commission.
Current sub-paragraph (C) of Rule 14.3(e)(3) requires the Exchange to commission an annual review and report by an independent accounting firm of the compliance of the Affiliate Security with the Exchange's listing requirements. The Exchange is required to promptly furnish a copy of this annual report to the Regulatory Oversight Committee of the Exchange's Board of Directors and the Commission. The Exchange proposes to renumber this paragraph as (2)(C) of Rule 14.3(e) to conform with the reformatting of Rule 14.3(e) proposed above. The Exchange also proposes to delete the requirement that the report also be sent to the Commission as this requirement is proposed to be included in proposed paragraph (e)(4) discussed below. The Exchange does not propose any substantive changes to this section of the rule.
Lastly, current Rule 14.3(e)(4) states that in the event the Exchange determines that the BZX Affiliate is not in compliance with any of the Exchange's listing standards, the Exchange is required to notify the issuer of such non-compliance promptly and request a plan of compliance. The Exchange is also required to file a report with the Commission within five business days of providing such notice to the issuer of its non-compliance. The required report identifies the date of the non-compliance, type of non-compliance, and any other material information conveyed to the issuer in the notice of non-compliance. Within five business days of receipt of a plan of compliance from the issuer, the Exchange is again required to notify the Commission of such receipt, whether the plan of compliance was accepted by the Exchange or what other action was taken with respect to the plan and the time period provided to regain compliance with the Exchange's listing standards, if any. The Exchange proposes to renumber this section of the rule as (2)(D) of Rule 14.3(e) to conform with the reformatting of Rule 14.3(e) proposed above. The Exchange does not propose any substantive changes to this section of the rule.
The Exchange believes that its proposal is consistent with the requirements of the Act and the rules and regulations thereunder that are applicable to a national securities exchange, and, in particular, with the requirements of Section 6(b) of the Act.
The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The proposed rule change is not designed to address any competitive issues, but rather provide additional specificity and transparency to Members, Users, and the investing public regarding the Exchange's controls that are in place to address the potential conflicts of interest that may arise in the listing of Affiliate Securities on the Exchange.
Written comments were neither solicited nor received.
The Exchange has filed the proposed rule change pursuant to Section 19(b)(3)(A)(iii) of the Act
A proposed rule change filed under Rule 19b-4(f)(6) under the Act
At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings to determine whether the proposed rule should be approved or disapproved.
Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:
• Use the Commission's Internet comment form (
• Send an email to
• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.
For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (the “Act”),
The Exchange is proposing a rule change to adopt Exchange Rule 14.10 setting forth additional requirements for the listing of securities that are issued by the Exchange or any of its affiliates as well as the monitoring of such securities' trading activity on the Exchange. Proposed Rule 14.10 is based on Bats BZX Exchange, Inc. (“BZX”) Rule 14.3(e), which was recently amended and filed for immediate effectiveness with the Commission.
The text of the proposed rule change is available at the Exchange's Web site at
In its filing with the Commission, the Exchange included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in Sections A, B, and C below, of the most significant parts of such statements.
The Exchange is proposing to adopt Rule 14.10 setting forth reporting requirements on the Exchange should the Exchange or BYX Affiliate list a security on the Exchange (the “Affiliate Security”). Proposed Rule 14.10(a)(1) would define “BYX Affiliate” as “the Exchange and any entity that directly or indirectly, through one or more intermediaries, controls, is controlled by, or is under common control with the Exchange, where “control” means that one entity possesses, directly or indirectly, voting control of the other entity either through ownership of capital stock or other equity securities or through majority representation on the board of directors or other management body of such entity.” Proposed Rule 14.10(a)(2) would define “Affiliate Security” as “any security issued by a BYX Affiliate or any Exchange-listed option on any such security, with the exception of Portfolio Depositary Receipts as defined in Rule 14.8(d) and Investment Company Units as defined in Rule 14.2.”
In the event that a BYX Affiliate seeks to list an Affiliate Security, paragraph (b)(1) of proposed Rule 14.10 would require that prior to the initial listing of the Affiliate Security on the Exchange, Exchange personnel shall determine that such security satisfies the Exchange's rules for listing, and such finding must be approved by the Regulatory Oversight Committee of the Exchange's Board of Directors.
Proposed paragraph (b)(2) of proposed Rule 14.10 would state that throughout the continued listing of the Affiliate Security on the Exchange, the Exchange will prepare a quarterly report for the Regulatory Oversight Committee of the Exchange's Board of Directors and that such report describe the Exchange's monitoring of the Affiliate Security's compliance with the Exchange's listing standards. Sub-paragraph (A) of proposed Rule 14.10(b)(2) would require the report include a description of the Affiliate Security's compliance with the Exchange's minimum share price requirement, and, sub-paragraph (B) would require the report to describe the Affiliate Security's compliance with each of the quantitative continued listing requirements.
Sub-paragraph (3) of proposed Rule 14.10(b) would require the Exchange to commission an annual review and report by an independent accounting firm of the compliance of the Affiliate Security with the Exchange's listing requirements. The Exchange would be required to promptly furnish a copy of this annual report to the Regulatory Oversight Committee of the Exchange's Board of Directors.
Sub-paragraph (4) of proposed Rule 14.10(b) would state that in the event the Exchange determines that the BYX Affiliate is not in compliance with any of the Exchange's listing standards, the Exchange is required to notify the issuer of such non-compliance promptly and request a plan of compliance. The Exchange would also be required to file a report with the Commission within five business days of providing such notice to the issuer of its non-compliance. The required report would identify the date of the non-compliance, type of non-compliance, and any other material information conveyed to the issuer in the notice of non-compliance. Within five business days of receipt of a plan of compliance from the issuer, the Exchange would again be required to notify the Commission of such receipt, whether the plan of compliance was accepted by the Exchange or what other action was taken with respect to the plan and the time period provided to regain compliance with the Exchange's listing standards, if any.
Sub-paragraph (c) of proposed Rule 14.10 would require that throughout the trading of an Affiliate Security on the Exchange, the Exchange prepare a quarterly report on the Affiliate Security for the Regulatory Oversight Committee of the Exchange's Board of Directors that describes the Exchange's monitoring of the trading of the Affiliate Security, including summaries of all related surveillance alerts, complaints,
Lastly, paragraph (d) of proposed Rule 14.10 would require the Exchange to promptly provide a copy of the reports required by sub-paragraphs (b) and (c) described above to the Commission.
The listing of an Affiliate Security or where an Affiliate Security is traded on the Exchange could potentially create a conflict of interest between the Exchange's self-regulatory responsibility to vigorously oversee the listing and trading of the stock on its market, and its own commercial or economic interests. Such “self-listing” may raise questions as to the Exchange's ability to independently and effectively enforce its rules against an affiliate or the operator/owner of its facility. In addition, such listing has the potential to exacerbate possible conflicts that may arise when the Exchange oversees competitors that may also be listed or traded on the Exchange. The Exchange believes that the proposed rule change, by requiring heightened reporting by the Exchange to the Regulatory Oversight Committee of the Exchange's Board of Directors and the Commission with respect to the Exchange's oversight of the listing and trading on the Exchange of any BYX Affiliate Security, will help protect against any concern that the Exchange will not effectively enforce its rules with respect to the listing and trading of these securities. In addition, the requirements that an independent accounting firm review such issuer's compliance with the Exchange's listing standards adds a degree of independent oversight to the Exchange's regulation of the listing of these securities and should help mitigate against any potential or actual conflicts of interest. The Exchange also believes that these additional requirements contained in the proposed rule change would provide additional assurance that any Affiliate Securities listed and traded on the Exchange by a BYX Affiliate comply with the Exchange's listing standards and trading rules on an on-going basis. Finally, the Exchange believes that the proposed rule change would eliminate any perception of a potential conflict of interest if a BYX Affiliate seeks to list a security on the Exchange or if an Affiliate Security is traded on the Exchange.
The Exchange believes that its proposal is consistent with the requirements of the Act and the rules and regulations thereunder that are applicable to a national securities exchange, and, in particular, with the requirements of Section 6(b) of the Act.
The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The proposed rule change is not designed to address any competitive issues, but rather set forth the Exchange's controls that are in place to address the potential conflicts of interest that may arise in the listing of Affiliate Securities on the Exchange.
Written comments were neither solicited nor received.
The Exchange has filed the proposed rule change pursuant to Section 19(b)(3)(A)(iii) of the Act
A proposed rule change filed under Rule 19b-4(f)(6) under the Act
At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings to determine whether the proposed rule should be approved or disapproved.
Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:
• Use the Commission's Internet comment form (
• Send an email to
• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.
For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
Pursuant to Section 19(b)(1)
The Exchange proposes to establish fees relating to end users and amend the definition of “affiliate,” as well as to amend the co-location section of the Arca Options Fee Schedule (the “Options Fee Schedule”) and, through its wholly owned subsidiary NYSE Arca Equities, Inc. (“NYSE Arca Equities”), the NYSE Arca Equities Schedule of Fees and Charges for Exchange Services (the “Equities Fee Schedule” and, together with the Options Fee Schedule, the “Fee Schedules”) to reflect the changes. The Exchange proposes that the changes be effective the first of the month following approval by the Securities and Exchange Commission (“Commission”).
The proposed rule change is available on the Exchange's Web site at
In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.
The Exchange proposes to establish fees relating to certain end users and amend the definition of “affiliate,” as well as to amend the co-location
Information flows over existing network connections in two formats:
• Multicast format, which is a format in which information is sent one-way from the Exchange to multiple recipients at once, like a radio broadcast; and
• Unicast format, which is a format that allows one-to-one communication, similar to a phone line, in which information is sent to and from the Exchange.
As a general matter, market data is broadcast to Users
A “Rebroadcasting User” would be a User that rebroadcasts to its customers data received from the Exchange in multicast format, unless such User normalizes the raw market data before sending it to its customers.
A “Multicast End User” would be a customer of a Rebroadcasting User, or a customer of a Rebroadcasting User's Multicast End User customer, to whom the Rebroadcasting User or its Multicast End User sends data received from the Exchange in multicast format, other than an Affiliate of the Rebroadcasting User. A Multicast End User may be, but is not required to be, another User or a Hosted Customer.
The Exchange proposes that a User that normalizes raw market data before sending it to its customers would not be a “Rebroadcasting User.” Such normalized data is altered before rebroadcasting, and is no longer in the form received from the Exchange. For example, a User may opt to normalize the raw data distributed by the Exchange and its affiliates by altering it to put it in viewable or algorithmic form, such as by putting it though a feed handler. In addition, the Exchange proposes that a User that rebroadcasts data received from third parties would not be a “Rebroadcasting User,” as the data would not be received from the Exchange.
A Rebroadcasting User may have more than one connection to a single Multicast End User. The multicast format permits a Multicast End User to rebroadcast the data received. Each of such customers is also considered a Multicast End User, irrespective of whether it receives the data from a Rebroadcasting User or another Multicast End User.
The Exchange proposes to charge Rebroadcasting Users fees relating to each Multicast End User as follows:
• If the Rebroadcasting User has one or two connections, either directly or through another Multicast End User, to a Multicast End User, the Rebroadcasting User would be subject to a $1,700 monthly charge.
• If the Rebroadcasting User has more than two connections to a Multicast End User, either directly or through another Multicast End User, the Rebroadcasting User would be subject to a $1,700 monthly charge for the first two connections (in the aggregate) and $850 for each additional connection.
Messages, such as those to send an order or related to clearing a trade, are transmitted in unicast format. A User may enable one or more of its customers to transmit messages in unicast format to and from the Exchange. For example, a User that is a service bureau or extranet may use such connections to facilitate order routing and clearing by its customers. The Exchange proposes to add to its co-location Fee Schedules definitions of a “Transmittal User” and a “Unicast End User.”
A “Transmittal User” would be a User that enables its customers, or the customers of its customers, to transmit messages to and from the Exchange using the unicast format.
A “Unicast End User” would be a customer of a Transmittal User, or a customer of a Transmittal User's Unicast End User customer, for whom the Transmittal User or its Unicast End User customer enables the transmission of messages to and from the Exchange in unicast format, other than a customer that (a) is an Affiliate of the Transmittal User or (b) sends all unicast transmissions through a floor participant, such as a floor broker. A Unicast End User may be, but is not required to be, a User or a Hosted Customer.
A Transmittal User may establish more than one connection for a single Unicast End User. The unicast format permits a Unicast End User to enable one or more of its customers to transmit messages to and from the Unicast End User. Each of such customers is also considered a Unicast End User.
The Exchange proposes to charge Transmittal Users fees relating to each Unicast End User as follows:
• If the Transmittal User has one or two connections to the Unicast End User, either directly or through another Unicast End User, the Transmittal User would be subject to a $1,500 monthly charge.
• If the Transmittal User has more than two connections to the Unicast End User, either directly or through another Unicast End User, the Transmittal User would be subject to a $1,500 monthly charge for the first two connections (in the aggregate) and $750 for each additional connection.
If a Transmittal User's customer sends all unicast transmissions through a floor participant, such as a floor broker, that customer would not be considered a Unicast End User even if such customer is enabled to use unicast communications. Accordingly, the Transmittal User would not be charged with respect to its connection to such customer.
A User may be both a Rebroadcasting User and a Transmittal User.
The proposed fees would not apply to a Multicast End User that is an “Affiliate” of a Rebroadcasting User or
Presently, for purposes of co-location fees the “Affiliate” of a User is defined as “any other User or Hosted Customer that is under 50% or greater common ownership or control of the first User.”
An “Affiliate” of a User is any other User or Hosted Customer that is under common control with, controls, or is controlled by, the first User, provided that: (1) An “Affiliate” of a Rebroadcasting User is any Multicast End User that is under common control with, controls, or is controlled by the Rebroadcasting User; and (2) an “Affiliate” of a Transmittal User is any Unicast End User that is under common control with, controls, or is controlled by the Transmittal User. For purposes of this definition, “control” means ownership or control of 50% or greater.
The Exchange proposes to amend the current definition of Affiliate to clarify that the control relationship does not exist only when a User or Hosted Customer is under the common ownership or control of the first User. Instead, an Affiliate relationship exists whenever the two entities are under common control and irrespective of which entity controls the other. In addition, the Exchange proposes to move the description of what “control” means to the end of the definition, to allow for addition of the definitions of Affiliate of Rebroadcasting Users and Transmittal Users.
By using the same concept of “control” for the definitions of Affiliate of Rebroadcasting Users and Transmittal Users as for the general definition, the Exchange believes that the expanded definition would be consistent in its application across the co-location related fees.
The Exchange incurs expenses and expends resources in connection with the support of Rebroadcasting Users and Transmittal Users. Some such costs are indirect, including those associated with overhead and technology infrastructure, administrative, maintenance and operational costs. Since the inception of co-location, there have been numerous network infrastructure improvements performed and administrative controls established. Additionally, the Exchange has automated retransmission facilities for most of its Users that receive multicast transmissions. These facilities benefit Rebroadcasting Users by reducing their operational costs associated with retransmissions to Multicast End Users that are also Users. The network infrastructure has been expanded to keep pace with the increased number of services available to Users, including Rebroadcasting and Transmittal Users, which, in turn, has increased the administrative and operational costs associated with delivery by Rebroadcasting Users and Transmittal Users to their Multicast End Users and Unicast End Users, respectively. The higher fees proposed in connection with the multicast format reflect the Exchange's experience that there are higher maintenance costs associated with supporting and rebroadcasting the multicast format, largely due to bandwidth requirements.
Based on its experience, the Exchange generally provides more direct support to Rebroadcasting Users and Transmittal Users than other Users, typically in the form of network support for the services that Rebroadcasting Users and Transmittal Users provide their Multicast End Users and Unicast End Users, respectively.
By contrast, in its experience the Exchange has found that entities that are Affiliates typically act as one entity, with one infrastructure, one administration, and one network support group. Accordingly, when the Exchange provides network support to a User rebroadcasting or transmitting multicast or unicast data to Affiliate end users, the Exchange is effectively supporting one entity, irrespective of how many Affiliate end users are involved. As a result, its administrative burden and operational costs are reduced in comparison to when it supports a Rebroadcasting User or Transmittal User rebroadcasting or transmitting to a Multicast End User or Unicast End User, respectively.
The Exchange does not provide network support for end users that receive normalized data. Because the normalized data is altered, the User that normalizes and then rebroadcasts normalized data acts as the source of the feed. As a result the User does not need the Exchange's assistance if an issue arises with its normalized feed. Accordingly, the Exchange proposes to exclude a User that normalizes data from the definition of Rebroadcasting User.
Rebroadcasting Users and Transmittal Users need network support, and the Exchange provides it, irrespective of whether their Multicast or Unicast End Users are Users. For this reason, the Exchange provides Rebroadcasting Users and Transmittal Users support related to their Multicast and Unicast End Users both inside and outside of co-location. Accordingly, the Exchange proposes not to limit the definitions of Multicast End Users and Unicast End Users to end users that are also Users.
In order to assess the proposed fees accurately, the Exchange proposes that Rebroadcasting Users and Transmittal Users be required to report the following
Users that are not Rebroadcasting Users or Transmittal Users may be asked to certify as much to the Exchange.
Users may independently set fees that they charge Multicast End Users and Unicast End Users. The Exchange would not be a party to the contractual relationship between Rebroadcasting Users and Transmittal Users and their customers and would not receive a share of any fees charged by Rebroadcasting Users and Transmittal Users for their services.
As is the case with all Exchange co-location arrangements, (i) neither a User nor any of the User's customers would be permitted to submit orders directly to the Exchange unless such User or customer is a Member, a Sponsored Participant or an agent thereof (
Finally, the Exchange proposes to delete the obsolete text in the Fee Schedules related to the Hosting Fee of $500 per Hosted Customer that was in effect until December 31, 2015. In addition, the Exchange proposes to delete the “Effective January 1, 2016” text that precedes the current description of the $1,000 monthly charge per cabinet per Hosted Customer for each cabinet in which such Hosted Customer is hosted because it is no longer necessary as these fees are current fees.
The proposed change is not otherwise intended to address any other issues relating to co-location services and/or related fees, and the Exchange is not aware of any problems that Users would have in complying with the proposed change.
The Exchange believes that the proposed rule change is consistent with Section 6(b) of the Act,
The Exchange also believes that the proposed rule change is consistent with Section 6(b)(4) of the Act,
The Exchange believes that the proposal is not designed to permit unfair discrimination between customers, issuers, brokers or dealers. Co-location services would continue to be offered by the Exchange in a manner that would not unfairly discriminate between or among market participants that are otherwise capable of satisfying any applicable co-location fees, requirements, terms and conditions established from time to time by the Exchange. The proposed end user-related definitions, fees and reporting requirements would be applied uniformly to all Users providing multicast and unicast connections and would not unfairly discriminate between similarly situated Users of co-location services.
In addition, the proposed end user fees would fairly and equitably allocate the costs associated with maintaining the Data Center facility, hardware and equipment and related to personnel required for installation and ongoing monitoring, support and maintenance of such service among all Users.
In the absence of the proposed end user fees, no charges would be assessed related to the benefit that Multicast End Users and Unicast End Users receive from these services through the Rebroadcasting or Transmittal User from whom they receive data, and the Rebroadcasting or Transmittal Users would thus receive disproportionate benefits.
The Exchange believes that the proposed fees are reasonable in that they are designed to defray applicable expenses incurred and resources expended by the Exchange in support of Rebroadcasting Users and Transmittal Users, including those associated with overhead and technology infrastructure, administrative, maintenance and operational costs, such as the costs of maintaining multiple connections with multiple providers. The Exchange incurs expenses and expends resources in connection with the support of Rebroadcasting Users and Transmittal Users. Some such costs are indirect, including those associated with overhead and technology infrastructure, administrative, maintenance and operational costs. Since the inception of co-location, there have been numerous network infrastructure improvements
Additionally, the Exchange has automated retransmission facilities for most of its Users that receive multicast transmissions. These facilities benefit Rebroadcasting Users by reducing their operational costs associated with retransmissions to Multicast End Users that are also Users. The network infrastructure has been expanded to keep pace with the increased number of services available to Users, including Rebroadcasting and Transmittal Users, which, in turn, has increased the administrative and operational costs associated with delivery by Rebroadcasting Users and Transmittal Users to their Multicast End Users and Unicast End Users, respectively. The Exchange believes that the proposed higher fees proposed in connection with the multicast format are reasonable because they reflect the Exchange's experience that there are higher maintenance costs associated with supporting and rebroadcasting the multicast format, largely due to bandwidth requirements.
In addition, based on its experience, the Exchange believes that the proposed fees are reasonable in that, as a general matter, the Exchange has a greater administrative burden and incurs greater operational costs to support Rebroadcasting Users and Transmittal Users than other Users. The Exchange generally provides more direct support to Rebroadcasting Users and Transmittal Users than other Users, typically in the form of network support for the services that Rebroadcasting Users and Transmittal Users provide their Multicast End Users and Unicast End Users, respectively. Typically when an issue arises, the Exchange and the applicable Rebroadcasting User or Transmittal User would conduct a review to determine the cause of an issue, with the participation of the relevant Multicast or Unicast End User. Based on its experience, the Exchange finds that when the User is a Rebroadcasting User or Transmittal User, pinpointing the issue and providing the needed network support becomes more complicated because each entity involved has its own infrastructure and administration.
The Exchange believes that it is reasonable to charge Rebroadcasting Users and Transmittal Users the proposed fees irrespective of whether their Multicast or Unicast End User is a User, because the Exchange provides Rebroadcasting Users and Transmittal Users support related to their Multicast and Unicast End Users that are outside of co-location as well as those that are Users. If the proposed fees were limited to Rebroadcasting Users and Transmittal Users whose Multicast or Unicast End Users were themselves Users, no charges would be assess related to the benefit that end users outside of co-location received from these services through the rebroadcasting or transmitting User from whom they received data. As a result, the Rebroadcasting Users and Transmittal Users whose Multicast or Unicast End Users were themselves Users would support a disproportionate share of the Exchange's administrative burden and operational costs relating to end users, and the rebroadcasting or transmitting Users would receive disproportionate benefits.
In addition, the Exchange believes that it is reasonable to charge the same amount for one or two connections because it would encourage Users and their customers to establish two connections and thereby create redundancy in the connections.
The Exchange believes that the proposed amendments to the definition of Affiliates regarding the control relationship are reasonable because they would make the definition more accessible and transparent and provide market participants with clarity as to what entities are considered Affiliates, ensuring that Users exclude all possible Affiliates from the proposed fees and the existing fees for Partial Cabinet Solution bundles. The Exchange believes that setting the common ownership or control threshold in the definition of Affiliates of Multicast End Users and Unicast End Users at 50% is reasonable because it is the same threshold as in the current definition of Affiliates.
Expanding the definition of Affiliates, adding the definitions of Multicast End User, Rebroadcasting User, Unicast End User, and Transmittal User, and adding the proposed note on the reporting requirements to the Fee Schedules would make such definitions and requirements accessible and transparent and provide market participants with clarity as to the application of the proposed fees. The Exchange believes that the proposal would remove impediments to, and perfect the mechanisms of, a free and open market and a national market system and, in general, protect investors and the public interest because by including the definitions and reporting requirements in the Fee Schedules, the proposed change would provide all Users with clarity as to the availability and application of co-location services and fees. Such end user-related definitions, fees and reporting requirements would be applied uniformly to all Users providing multicast and unicast connections and would not unfairly discriminate between similarly situated Users of co-location services.
The Exchange believes that excluding Affiliates from the definitions of Multicast End Users and Unicast End Users is reasonable because, in its experience, when the Exchange provides network support to a User rebroadcasting or transmitting multicast or unicast data to Affiliate end users, the Exchange's administrative burden and operational costs are reduced in comparison to when it supports a Rebroadcasting User or Transmittal User rebroadcasting or transmitting multicast or unicast data to a Multicast End User or Unicast End User, respectively. In its experience, entities that are Affiliates typically act as one entity, with one infrastructure, one administration, and one network support group. Accordingly, when the Exchange provides network support to a User rebroadcasting or transmitting multicast or unicast data to Affiliate end users, the Exchange is effectively supporting one entity, irrespective of how many Affiliate end users are involved.
The Exchange believes that having the definition of Affiliates encompass non-Users is reasonable because in its experience entities that are Affiliates typically act as one entity irrespective of whether one or more of them are not Users. If the definition did not encompass non-Users, a User would have to pay the proposed fee if it rebroadcast or transmitted multicast or unicast data to an end user that was not a User but otherwise met the definition of Affiliate. However, the Exchange would incur the same costs irrespective of whether the end user is itself a User or is located outside of co-location. Accordingly, the Exchange believes that having the definition of Affiliates encompass non-Users avoids disparate treatment of a Rebroadcasting User or Transmittal User that has a non-User as its Affiliate, as compared to one that has a User as its Affiliate.
The Exchange believes that it is reasonable that, under the proposed definition, two Multicast End Users or Unicast End Users would not be considered Affiliates even if they otherwise met the requirements of the definition. The Exchange has no direct contract with a Rebroadcasting User's Multicast End Users for connectivity to Exchange data, or with a Transmittal User's Unicast End Users for the transmission of messages to and from the Exchange. As a result, the Exchange would not be able to independently ascertain which Multicast and
The Exchange believes that the proposal to exclude Affiliates from the definitions of Multicast End User and Unicast End User is not designed to permit unfair discrimination between customers, issuers, brokers or dealers because the proposed rule avoids disparate treatment of Users that have divided their various business activities among separate corporate entities, as compared to Users that operate those business activities within a single corporate entity. In addition, the inclusion of non-Users in the definition of Affiliates is not designed to permit unfair discrimination between customers, issuers, brokers or dealers because the proposed rule avoids disparate treatment of Users that have Affiliates that are not Users, as compared to Users whose Affiliates are all Users.
The Exchange believes that the proposal to exclude from the definition of Multicast End Users a User that normalizes raw data before rebroadcasting it to its customers is reasonable and is not designed to permit unfair discrimination between customers, issuers, brokers or dealers because a User that normalizes and then rebroadcasts normalized data acts as the source of the feed, and so does not need the Exchange's assistance if an issue arises with its normalized feed. As a result, the Exchange does not incur the same costs in relation to end users of normalized data as it does in relation to Multicast End Users.
The Exchange believes that the proposal to exclude from the definition of Unicast End User those customers of a Transmittal User (and customers of Users' customers) that send all orders to a Floor broker for representation on the Exchange is reasonable because it would encourage sending orders to Floor brokers for execution, thereby encouraging additional displayed liquidity on the Exchange. This would encourage the execution of transactions on a public registered exchange, thereby promoting public price discovery—an objective fully consistent with the Act.
The Exchange believes that the proposal to have Users report the number of their Multicast End Users and Unicast End Users and the number of connections to each such Multicast End User and Unicast End User is reasonable because it will ensure that the proposed fees are assessed accurately and will provide market participants with clarity as to how the fees will be assessed.
For the reasons above, the proposed change would not unfairly discriminate between or among market participants that are otherwise capable of satisfying any applicable co-location fees, requirements, terms and conditions established from time to time by the Exchange.
Finally, the Exchange believes that it is subject to significant competitive forces, as described below in the Exchange's statement regarding the burden on competition.
For these reasons, the Exchange believes that the proposal is consistent with the Act.
In accordance with Section 6(b)(8) of the Act,
In addition, the Exchange believes that the proposed end user fees would not impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act because they would fairly and equitably allocate the costs associated with maintaining the Data Center facility, hardware and equipment and related to personnel required for installation and ongoing monitoring, support and maintenance of such service among all Users, as well as applicable expenses incurred and resources expended by the Exchange in support of Rebroadcasting Users and Transmittal Users. In the absence of the proposed end user fees, no charges would be assessed related to the benefit that Multicast End Users and Unicast End Users receive from these services through the Rebroadcasting or Transmittal User from whom they receive data, and the Rebroadcasting or Transmittal Users would thus receive disproportionate benefits.
The Exchange believes that the proposed end user fees would not impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act because the Exchange has tailored the proposed definition of Affiliate to include User and non-User Affiliates. If the proposed fees were limited to Rebroadcasting Users and Transmittal Users whose Multicast or Unicast End Users were themselves Users, no charges would be assessed relating to the benefit that end users outside of co-location received from these services through the rebroadcasting or transmitting User from whom they received data. As a result, the Rebroadcasting Users and Transmittal Users whose Multicast or Unicast End Users were themselves Users would support a disproportionate share of the Exchange's administrative burden and operational costs relating to end users, and the rebroadcasting or transmitting Users would receive disproportionate benefits.
The Exchange believes that the proposed end user fees would not impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act because the Exchange has excluded Affiliates from the proposed definitions of Multicast End Users and Unicast End Users. As a result, the proposed end user fees exclude fees related to end users that, in the Exchange's experience, typically act as one entity, with one infrastructure and one administration.
The Exchange believes that the proposal to exclude from the definition
Finally, the Exchange notes that it operates in a highly competitive market in which market participants can readily favor competing venues if, for example, they deem fee levels at a particular venue to be excessive or if they determine that another venue's products and services are more competitive than on the Exchange. In such an environment, the Exchange must continually review, and consider adjusting, the services it offers as well as any corresponding fees and credits to remain competitive with other exchanges. For the reasons described above, the Exchange believes that the proposed rule change reflects this competitive environment.
No written comments were solicited or received with respect to the proposed rule change.
Within 45 days of the date of publication of this notice in the
Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:
• Use the Commission's Internet comment form (
• Send an email to
• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.
For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
Notice is hereby given that, pursuant to the Paperwork Reduction Act of 1995 (44 U.S.C. 3501
Rule 606 (formerly known as Rule 11Ac1-6) requires broker-dealers to prepare and disseminate quarterly order routing reports. Much of the information needed to generate these reports already should be collected by broker-dealers in connection with their periodic evaluations of their order routing practices. Broker-dealers must conduct such evaluations to fulfill the duty of best execution that they owe their customers.
The collection of information obligations of Rule 606 apply to broker-dealers that route non-directed customer orders in covered securities. The Commission estimates that out of the currently 4,240 broker-dealers that are subject to the collection of information obligations of Rule 606, clearing brokers bear a substantial portion of the burden of complying with the reporting and recordkeeping requirements of Rule 606 on behalf of small to mid-sized introducing firms. There currently are approximately 185 clearing brokers. In addition, there are approximately 81 introducing brokers that receive funds or securities from their customers. Because at least some of these firms also may have greater involvement in determining where customer orders are routed for execution, they have been included, along with clearing brokers, in estimating the total burden of Rule 606.
The Commission staff estimates that each firm significantly involved in order routing practices incurs an average burden of 40 hours to prepare and disseminate a quarterly report required by Rule 606, or a burden of 160 hours
Rule 606 also requires broker-dealers to respond to individual customer requests for information on orders handled by the broker-dealer for that customer. Clearing brokers generally bear the burden of responding to these requests. The Commission staff estimates that an average clearing broker incurs an annual burden of 400 hours (2000 responses × 0.2 hours/response) to prepare, disseminate, and retain responses to customers required by Rule 606. With an estimated 185 clearing brokers subject to Rule 606, the total industry-wide burden per year to comply with the customer response requirement in Rule 606 is estimated to be 74,000 hours (185 × 400).
The collection of information obligations imposed by Rule 606 are mandatory. The responses will be available to the public and will not be kept confidential.
An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information under the PRA unless it displays a currently valid OMB control number.
The public may view background documentation for this information collection at the following Web site,
Pursuant to Section 19(b)(1)
The Exchange proposes to establish fees relating to end users and amend the definition of “affiliate,” as well as to amend the co-location section of the NYSE MKT Equities Price List (“Price List”) and the NYSE Amex Options Fee Schedule (“Fee Schedule”) to reflect the changes. The Exchange proposes that the changes be effective the first of the month following approval by the Securities and Exchange Commission (“Commission”). The proposed change is available on the Exchange's Web site at
In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.
The Exchange proposes to establish fees relating to certain end users and amend the definition of “affiliate,” as well as to amend the co-location
Information flows over existing network connections in two formats:
• Multicast format, which is a format in which information is sent one-way from the Exchange to multiple recipients at once, like a radio broadcast; and
• Unicast format, which is a format that allows one-to-one communication, similar to a phone line, in which information is sent to and from the Exchange.
As a general matter, market data is broadcast to Users
A “Rebroadcasting User” would be a User that rebroadcasts to its customers data received from the Exchange in multicast format, unless such User normalizes the raw market data before sending it to its customers.
A “Multicast End User” would be a customer of a Rebroadcasting User, or a customer of a Rebroadcasting User's Multicast End User customer, to whom the Rebroadcasting User or its Multicast End User sends data received from the Exchange in multicast format, other than an Affiliate of the Rebroadcasting User. A Multicast End User may be, but is not required to be, another User or a Hosted Customer.
The Exchange proposes that a User that normalizes raw market data before sending it to its customers would not be a “Rebroadcasting User.” Such normalized data is altered before rebroadcasting, and is no longer in the form received from the Exchange. For example, a User may opt to normalize the raw data distributed by the Exchange and its affiliates by altering it to put it in viewable or algorithmic form, such as by putting it though a feed handler. In addition, the Exchange proposes that a User that rebroadcasts data received from third parties would not be a “Rebroadcasting User,” as the data would not be received from the Exchange.
A Rebroadcasting User may have more than one connection to a single Multicast End User. The multicast format permits a Multicast End User to rebroadcast the data received. Each of such customers is also considered a Multicast End User, irrespective of whether it receives the data from a Rebroadcasting User or another Multicast End User.
The Exchange proposes to charge Rebroadcasting Users fees relating to each Multicast End User as follows:
• If the Rebroadcasting User has one or two connections, either directly or through another Multicast End User, to a Multicast End User, the Rebroadcasting User would be subject to a $1,700 monthly charge.
• If the Rebroadcasting User has more than two connections to a Multicast End User, either directly or through another Multicast End User, the Rebroadcasting User would be subject to a $1,700 monthly charge for the first two connections (in the aggregate) and $850 for each additional connection.
Messages, such as those to send an order or related to clearing a trade, are transmitted in unicast format. A User may enable one or more of its customers to transmit messages in unicast format to and from the Exchange. For example, a User that is a service bureau or extranet may use such connections to facilitate order routing and clearing by its customers. The Exchange proposes to add to its co-location Price List and Fee Schedule definitions of a “Transmittal User” and a “Unicast End User.”
A “Transmittal User” would be a User that enables its customers, or the customers of its customers, to transmit messages to and from the Exchange using the unicast format.
A “Unicast End User” would be a customer of a Transmittal User, or a customer of a Transmittal User's Unicast End User customer, for whom the Transmittal User or its Unicast End User customer enables the transmission of messages to and from the Exchange in unicast format, other than a customer that (a) is an Affiliate of the Transmittal User or (b) sends all unicast transmissions through a floor participant, such as a floor broker. A Unicast End User may be, but is not required to be, a User or a Hosted Customer.
A Transmittal User may establish more than one connection for a single Unicast End User. The unicast format permits a Unicast End User to enable one or more of its customers to transmit messages to and from the Unicast End User. Each of such customers is also considered a Unicast End User.
The Exchange proposes to charge Transmittal Users fees relating to each Unicast End User as follows:
• If the Transmittal User has one or two connections to the Unicast End User, either directly or through another Unicast End User, the Transmittal User would be subject to a $1,500 monthly charge.
• If the Transmittal User has more than two connections to the Unicast End User, either directly or through another Unicast End User, the Transmittal User would be subject to a $1,500 monthly charge for the first two connections (in the aggregate) and $750 for each additional connection.
If a Transmittal User's customer sends all unicast transmissions through a floor participant, such as a floor broker, that customer would not be considered a Unicast End User even if such customer is enabled to use unicast communications. Accordingly, the Transmittal User would not be charged with respect to its connection to such customer.
A User may be both a Rebroadcasting User and a Transmittal User.
The proposed fees would not apply to a Multicast End User that is an “Affiliate” of a Rebroadcasting User or a Unicast End User that is an “Affiliate” of a Transmittal User.
Presently, for purposes of co-location fees the “Affiliate” of a User is defined as “any other User or Hosted Customer that is under 50% or greater common ownership or control of the first User.”
An “Affiliate” of a User is any other User or Hosted Customer that is under common control with, controls, or is controlled by, the first User, provided that: (1) An “Affiliate” of a Rebroadcasting User is any Multicast End User that is under common control with, controls, or is controlled by the Rebroadcasting User; and (2) an “Affiliate” of a Transmittal User is any Unicast End User that is under common control with, controls, or is controlled by the Transmittal User. For purposes of this definition, “control” means ownership or control of 50% or greater.
The Exchange proposes to amend the current definition of Affiliate to clarify that the control relationship does not exist only when a User or Hosted Customer is under the common ownership or control of the first User. Instead, an Affiliate relationship exists whenever the two entities are under common control and irrespective of which entity controls the other. In
By using the same concept of “control” for the definitions of Affiliate of Rebroadcasting Users and Transmittal Users as as for the general definition, the Exchange believes that the expanded definition would be consistent in its application across the co-location related fees.
The Exchange incurs expenses and expends resources in connection with the support of Rebroadcasting Users and Transmittal Users. Some such costs are indirect, including those associated with overhead and technology infrastructure, administrative, maintenance and operational costs. Since the inception of co-location, there have been numerous network infrastructure improvements performed and administrative controls established. Additionally, the Exchange has automated retransmission facilities for most of its Users that receive multicast transmissions. These facilities benefit Rebroadcasting Users by reducing their operational costs associated with retransmissions to Multicast End Users that are also Users. The network infrastructure has been expanded to keep pace with the increased number of services available to Users, including Rebroadcasting and Transmittal Users, which, in turn, has increased the administrative and operational costs associated with delivery by Rebroadcasting Users and Transmittal Users to their Multicast End Users and Unicast End Users, respectively. The higher fees proposed in connection with the multicast format reflect the Exchange's experience that there are higher maintenance costs associated with supporting and rebroadcasting the multicast format, largely due to bandwidth requirements.
Based on its experience, the Exchange generally provides more direct support to Rebroadcasting Users and Transmittal Users than other Users, typically in the form of network support for the services that Rebroadcasting Users and Transmittal Users provide their Multicast End Users and Unicast End Users, respectively.
By contrast, in its experience the Exchange has found that entities that are Affiliates typically act as one entity, with one infrastructure, one administration, and one network support group. Accordingly, when the Exchange provides network support to a User rebroadcasting or transmitting multicast or unicast data to Affiliate end users, the Exchange is effectively supporting one entity, irrespective of how many Affiliate end users are involved. As a result, its administrative burden and operational costs are reduced in comparison to when it supports a Rebroadcasting User or Transmittal User rebroadcasting or transmitting to a Multicast End User or Unicast End User, respectively.
The Exchange does not provide network support for end users that receive normalized data. Because the normalized data is altered, the User that normalizes and then rebroadcasts normalized data acts as the source of the feed. As a result the User does not need the Exchange's assistance if an issue arises with its normalized feed. Accordingly, the Exchange proposes to exclude a User that normalizes data from the definition of Rebroadcasting User.
Rebroadcasting Users and Transmittal Users need network support, and the Exchange provides it, irrespective of whether their Multicast or Unicast End Users are Users. For this reason, the Exchange provides Rebroadcasting Users and Transmittal Users support related to their Multicast and Unicast End Users both inside and outside of co-location. Accordingly, the Exchange proposes not to limit the definitions of Multicast End Users and Unicast End Users to end users that are also Users.
In order to assess the proposed fees accurately, the Exchange proposes that Rebroadcasting Users and Transmittal Users be required to report the following to the Exchange on a monthly basis: (a) The number of their Multicast End Users and Unicast End Users, and (b) the number of connections to each such Multicast End User and Unicast End User. A User that excludes an Affiliate from its list of Multicast End Users or Unicast End Users consistent with the proposed definitions may be required to certify to the Exchange the Affiliate status of such end user.
Users that are not Rebroadcasting Users or Transmittal Users may be asked to certify as much to the Exchange.
Users may independently set fees that they charge Multicast End Users and Unicast End Users. The Exchange would not be a party to the contractual relationship between Rebroadcasting Users and Transmittal Users and their customers and would not receive a share of any fees charged by Rebroadcasting Users and Transmittal Users for their services.
As is the case with all Exchange co-location arrangements, (i) neither a User
Finally, the Exchange proposes to delete the obsolete text in the Price List and Fee Schedule related to the Hosting Fee of $500 per Hosted Customer that was in effect until December 31, 2015. In addition, the Exchange proposes to delete the “Effective January 1, 2016” text that precedes the current description of the $1,000 monthly charge per cabinet per Hosted Customer for each cabinet in which such Hosted Customer is hosted because it is no longer necessary as these fees are current fees.
The proposed change is not otherwise intended to address any other issues relating to co-location services and/or related fees, and the Exchange is not aware of any problems that Users would have in complying with the proposed change.
The Exchange believes that the proposed rule change is consistent with Section 6(b) of the Act,
The Exchange also believes that the proposed rule change is consistent with Section 6(b)(4) of the Act,
The Exchange believes that the proposal is not designed to permit unfair discrimination between customers, issuers, brokers or dealers. Co-location services would continue to be offered by the Exchange in a manner that would not unfairly discriminate between or among market participants that are otherwise capable of satisfying any applicable co-location fees, requirements, terms and conditions established from time to time by the Exchange. The proposed end user-related definitions, fees and reporting requirements would be applied uniformly to all Users providing multicast and unicast connections and would not unfairly discriminate between similarly situated Users of co-location services.
In addition, the proposed end user fees would fairly and equitably allocate the costs associated with maintaining the Data Center facility, hardware and equipment and related to personnel required for installation and ongoing monitoring, support and maintenance of such service among all Users.
In the absence of the proposed end user fees, no charges would be assessed related to the benefit that Multicast End Users and Unicast End Users receive from these services through the Rebroadcasting or Transmittal User from whom they receive data, and the Rebroadcasting or Transmittal Users would thus receive disproportionate benefits.
The Exchange believes that the proposed fees are reasonable in that they are designed to defray applicable expenses incurred and resources expended by the Exchange in support of Rebroadcasting Users and Transmittal Users, including those associated with overhead and technology infrastructure, administrative, maintenance and operational costs, such as the costs of maintaining multiple connections with multiple providers. The Exchange incurs expenses and expends resources in connection with the support of Rebroadcasting Users and Transmittal Users. Some such costs are indirect, including those associated with overhead and technology infrastructure, administrative, maintenance and operational costs. Since the inception of co-location, there have been numerous network infrastructure improvements performed and administrative controls established.
Additionally, the Exchange has automated retransmission facilities for most of its Users that receive multicast transmissions. These facilities benefit Rebroadcasting Users by reducing their operational costs associated with retransmissions to Multicast End Users that are also Users. The network infrastructure has been expanded to keep pace with the increased number of services available to Users, including Rebroadcasting and Transmittal Users, which, in turn, has increased the administrative and operational costs associated with delivery by Rebroadcasting Users and Transmittal Users to their Multicast End Users and Unicast End Users, respectively. The Exchange believes that the proposed higher fees proposed in connection with the multicast format are reasonable because they reflect the Exchange's experience that there are higher maintenance costs associated with supporting and rebroadcasting the multicast format, largely due to bandwidth requirements.
In addition, based on its experience, the Exchange believes that the proposed fees are reasonable in that, as a general matter, the Exchange has a greater administrative burden and incurs greater operational costs to support Rebroadcasting Users and Transmittal Users than other Users. The Exchange generally provides more direct support to Rebroadcasting Users and Transmittal Users than other Users, typically in the
The Exchange believes that it is reasonable to charge Rebroadcasting Users and Transmittal Users the proposed fees irrespective of whether their Multicast or Unicast End User is a User, because the Exchange provides Rebroadcasting Users and Transmittal Users support related to their Multicast and Unicast End Users that are outside of co-location as well as those that are Users. If the proposed fees were limited to Rebroadcasting Users and Transmittal Users whose Multicast or Unicast End Users were themselves Users, no charges would be assess related to the benefit that end users outside of co-location received from these services through the rebroadcasting or transmitting User from whom they received data. As a result, the Rebroadcasting Users and Transmittal Users whose Multicast or Unicast End Users were themselves Users would support a disproportionate share of the Exchange's administrative burden and operational costs relating to end users, and the rebroadcasting or transmitting Users would receive disproportionate benefits.
In addition, the Exchange believes that it is reasonable to charge the same amount for one or two connections because it would encourage Users and their customers to establish two connections and thereby create redundancy in the connections.
The Exchange believes that the proposed amendments to the definition of Affiliates regarding the control relationship are reasonable because they would make the definition more accessible and transparent and provide market participants with clarity as to what entities are considered Affiliates, ensuring that Users exclude all possible Affiliates from the proposed fees and the existing fees for Partial Cabinet Solution bundles. The Exchange believes that setting the common ownership or control threshold in the definition of Affiliates of Multicast End Users and Unicast End Users at 50% is reasonable because it is the same threshold as in the current definition of Affiliates.
Expanding the definition of Affiliates, adding the definitions of Multicast End User, Rebroadcasting User, Unicast End User, and Transmittal User, and adding the proposed note on the reporting requirements to the Price List and Fee Schedule would make such definitions and requirements accessible and transparent and provide market participants with clarity as to the application of the proposed fees.. The Exchange believes that the proposal would remove impediments to, and perfect the mechanisms of, a free and open market and a national market system and, in general, protect investors and the public interest because by including the definitions and reporting requirements in the Price List and Fee Schedule, the proposed change would provide all Users with clarity as to the availability and application of co-location services and fees. Such end user-related definitions, fees and reporting requirements would be applied uniformly to all Users providing multicast and unicast connections and would not unfairly discriminate between similarly situated Users of co-location services.
The Exchange believes that excluding Affiliates from the definitions of Multicast End Users and Unicast End Users is reasonable because, in its experience, when the Exchange provides network support to a User rebroadcasting or transmitting multicast or unicast data to Affiliate end users, the Exchange's administrative burden and operational costs are reduced in comparison to when it supports a Rebroadcasting User or Transmittal User rebroadcasting or transmitting multicast or unicast data to a Multicast End User or Unicast End User, respectively. In its experience, entities that are Affiliates typically act as one entity, with one infrastructure, one administration, and one network support group. Accordingly, when the Exchange provides network support to a User rebroadcasting or transmitting multicast or unicast data to Affiliate end users, the Exchange is effectively supporting one entity, irrespective of how many Affiliate end users are involved.
The Exchange believes that having the definition of Affiliates encompass non-Users is reasonable because in its experience entities that are Affiliates typically act as one entity irrespective of whether one or more of them are not Users. If the definition did not encompass non-Users, a User would have to pay the proposed fee if it rebroadcast or transmitted multicast or unicast data to an end user that was not a User but otherwise met the definition of Affiliate. However, the Exchange would incur the same costs irrespective of whether the end user is itself a User or is located outside of co-location. Accordingly, the Exchange believes that having the definition of Affiliates encompass non-Users avoids disparate treatment of a Rebroadcasting User or Transmittal User that has a non-User as its Affiliate, as compared to one that has a User as its Affiliate.
The Exchange believes that it is reasonable that, under the proposed definition, two Multicast End Users or Unicast End Users would not be considered Affiliates even if they otherwise met the requirements of the definition. The Exchange has no direct contract with a Rebroadcasting User's Multicast End Users for connectivity to Exchange data, or with a Transmittal User's Unicast End Users for the transmission of messages to and from the Exchange. As a result, the Exchange would not be able to independently ascertain which Multicast and Transmittal Users met the definition of Affiliates, and would have no standing to require such Multicast and Unicast End Users to report their Affiliates. The Exchange believes it would create an unnecessary administrative burden on Users to require Rebroadcasting Users and Transmittal Users to determine which, if any, of their Multicast and Unicast End Users were affiliated, and to report such to the Exchange.
The Exchange believes that the proposal to exclude Affiliates from the definitions of Multicast End User and Unicast End User is not designed to permit unfair discrimination between customers, issuers, brokers or dealers because the proposed rule avoids disparate treatment of Users that have divided their various business activities among separate corporate entities, as compared to Users that operate those business activities within a single corporate entity. In addition, the inclusion of non-Users in the definition of Affiliates is not designed to permit unfair discrimination between customers, issuers, brokers or dealers because the proposed rule avoids disparate treatment of Users that have Affiliates that are not Users, as compared to Users whose Affiliates are all Users.
The Exchange believes that the proposal to exclude from the definition of Multicast End Users a User that normalizes raw data before rebroadcasting it to its customers is reasonable and is not designed to permit
The Exchange believes that the proposal to exclude from the definition of Unicast End User those customers of a Transmittal User (and customers of Users' customers) that send all orders to a Floor broker for representation on the Exchange is reasonable because it would encourage sending orders to Floor brokers for execution, thereby encouraging additional displayed liquidity on the Exchange. This would encourage the execution of transactions on a public registered exchange, thereby promoting public price discovery—an objective fully consistent with the Act.
The Exchange believes that the proposal to have Users report the number of their Multicast End Users and Unicast End Users and the number of connections to each such Multicast End User and Unicast End User is reasonable because it will ensure that the proposed fees are assessed accurately and will provide market participants with clarity as to how the fees will be assessed.
For the reasons above, the proposed change would not unfairly discriminate between or among market participants that are otherwise capable of satisfying any applicable co-location fees, requirements, terms and conditions established from time to time by the Exchange.
Finally, the Exchange believes that it is subject to significant competitive forces, as described below in the Exchange's statement regarding the burden on competition.
For these reasons, the Exchange believes that the proposal is consistent with the Act.
In accordance with Section 6(b)(8) of the Act,
In addition, the Exchange believes that the proposed end user fees would not impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act because they would fairly and equitably allocate the costs associated with maintaining the Data Center facility, hardware and equipment and related to personnel required for installation and ongoing monitoring, support and maintenance of such service among all Users, as well as applicable expenses incurred and resources expended by the Exchange in support of Rebroadcasting Users and Transmittal Users. In the absence of the proposed end user fees, no charges would be assessed related to the benefit that Multicast End Users and Unicast End Users receive from these services through the Rebroadcasting or Transmittal User from whom they receive data, and the Rebroadcasting or Transmittal Users would thus receive disproportionate benefits.
The Exchange believes that the proposed end user fees would not impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act because the Exchange has tailored the proposed definition of Affiliate to include User and non-User Affiliates. If the proposed fees were limited to Rebroadcasting Users and Transmittal Users whose Multicast or Unicast End Users were themselves Users, no charges would be assessed relating to the benefit that end users outside of co-location received from these services through the rebroadcasting or transmitting User from whom they received data. As a result, the Rebroadcasting Users and Transmittal Users whose Multicast or Unicast End Users were themselves Users would support a disproportionate share of the Exchange's administrative burden and operational costs relating to end users, and the rebroadcasting or transmitting Users would receive disproportionate benefits.
The Exchange believes that the proposed end user fees would not impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act because the Exchange has excluded Affiliates from the proposed definitions of Multicast End Users and Unicast End Users. As a result, the proposed end user fees exclude fees related to end users that, in the Exchange's experience, typically act as one entity, with one infrastructure and one administration.
The Exchange believes that the proposal to exclude from the definition of Unicast End User those customers of a Transmittal User (and customers of Users' customers) that send all orders to a Floor broker for representation on the Exchange is reasonable because it would encourage providing liquidity on the Exchange, thereby contributing to the Exchange's competitiveness with other markets. In addition, the Exchange believes that expanding the definition of Affiliates and adding the definitions of Multicast End User, Rebroadcasting User, Unicast End User, and Transmittal User to the Price List and Fee Schedule would make such definitions accessible and transparent and provide market participants with clarity as to the availability and application of the proposed fees.
Finally, the Exchange notes that it operates in a highly competitive market in which market participants can readily favor competing venues if, for example, they deem fee levels at a particular venue to be excessive or if they determine that another venue's products and services are more competitive than on the Exchange. In such an environment, the Exchange must continually review, and consider adjusting, the services it offers as well as any corresponding fees and credits to remain competitive with other exchanges. For the reasons described above, the Exchange believes that the proposed rule change reflects this competitive environment.
No written comments were solicited or received with respect to the proposed rule change.
Within 45 days of the date of publication of this notice in the
Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:
• Use the Commission's Internet comment form (
• Send an email to
• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.
For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
Pursuant to Section 19(b)(1)
The Exchange proposes to establish fees relating to end users and amend the definition of “affiliate,” as well as to amend the co-location section of the Exchange's Price List to reflect the changes. The Exchange proposes that the changes be effective the first of the month following approval by the Securities and Exchange Commission (“Commission”). The proposed rule change is available on the Exchange's Web site at
In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.
The Exchange proposes to establish fees relating to certain end users and amend the definition of “affiliate,” as well as to amend the co-location
Information flows over existing network connections in two formats:
• Multicast format, which is a format in which information is sent one-way from the Exchange to multiple recipients at once, like a radio broadcast; and
• Unicast format, which is a format that allows one-to-one communication, similar to a phone line, in which information is sent to and from the Exchange.
As a general matter, market data is broadcast to Users
A “Rebroadcasting User” would be a User that rebroadcasts to its customers data received from the Exchange in multicast format, unless such User normalizes the raw market data before sending it to its customers.
A “Multicast End User” would be a customer of a Rebroadcasting User, or a customer of a Rebroadcasting User's Multicast End User customer, to whom the Rebroadcasting User or its Multicast End User sends data received from the Exchange in multicast format, other than an Affiliate of the Rebroadcasting User. A Multicast End User may be, but is not required to be, another User or a Hosted Customer.
The Exchange proposes that a User that normalizes raw market data before sending it to its customers would not be a “Rebroadcasting User.” Such normalized data is altered before rebroadcasting, and is no longer in the form received from the Exchange. For example, a User may opt to normalize the raw data distributed by the Exchange and its affiliates by altering it to put it in viewable or algorithmic form, such as by putting it though a feed handler. In addition, the Exchange proposes that a User that rebroadcasts data received from third parties would not be a “Rebroadcasting User,” as the data would not be received from the Exchange.
A Rebroadcasting User may have more than one connection to a single Multicast End User. The multicast format permits a Multicast End User to rebroadcast the data received. Each of such customers is also considered a Multicast End User, irrespective of whether it receives the data from a Rebroadcasting User or another Multicast End User.
The Exchange proposes to charge Rebroadcasting Users fees relating to each Multicast End User as follows:
• If the Rebroadcasting User has one or two connections, either directly or through another Multicast End User, to a Multicast End User, the Rebroadcasting User would be subject to a $1,700 monthly charge.
• If the Rebroadcasting User has more than two connections to a Multicast End User, either directly or through another Multicast End User, the Rebroadcasting User would be subject to a $1,700 monthly charge for the first two connections (in the aggregate) and $850 for each additional connection.
Messages, such as those to send an order or related to clearing a trade, are transmitted in unicast format. A User may enable one or more of its customers to transmit messages in unicast format to and from the Exchange. For example, a User that is a service bureau or extranet may use such connections to facilitate order routing and clearing by its customers. The Exchange proposes to add to its co-location Price List definitions of a “Transmittal User” and a “Unicast End User.”
A “Transmittal User” would be a User that enables its customers, or the customers of its customers, to transmit messages to and from the Exchange using the unicast format.
A “Unicast End User” would be a customer of a Transmittal User, or a customer of a Transmittal User's Unicast End User customer, for whom the Transmittal User or its Unicast End User customer enables the transmission of messages to and from the Exchange in unicast format, other than a customer that (a) is an Affiliate of the Transmittal User or (b) sends all unicast transmissions through a floor participant, such as a floor broker. a Unicast End User may be, but is not required to be, a User or a Hosted Customer.
A Transmittal User may establish more than one connection for a single Unicast End User. The unicast format permits a Unicast End User to enable one or more of its customers to transmit messages to and from the Unicast End User. Each of such customers is also considered a Unicast End User.
The Exchange proposes to charge Transmittal Users fees relating to each Unicast End User as follows:
• If the Transmittal User has one or two connections to the Unicast End User, either directly or through another Unicast End User, the Transmittal User would be subject to a $1,500 monthly charge.
• If the Transmittal User has more than two connections to the Unicast End User, either directly or through another Unicast End User, the Transmittal User would be subject to a $1,500 monthly charge for the first two connections (in the aggregate) and $750 for each additional connection.
If a Transmittal User's customer sends all unicast transmissions through a floor participant, such as a floor broker, that customer would not be considered a Unicast End User even if such customer is enabled to use unicast communications. Accordingly, the Transmittal User would not be charged with respect to its connection to such customer.
A User may be both a Rebroadcasting User and a Transmittal User.
The proposed fees would not apply to a Multicast End User that is an “Affiliate” of a Rebroadcasting User or a Unicast End User that is an “Affiliate” of a Transmittal User.
Presently, for purposes of co-location fees the “Affiliate” of a User is defined as “any other User or Hosted Customer that is under 50% or greater common ownership or control of the first User.”
An “Affiliate” of a User is any other User or Hosted Customer that is under common control with, controls, or is controlled by, the first User, provided that: (1) An “Affiliate” of a Rebroadcasting User is any Multicast End User that is under common control with, controls, or is controlled by the Rebroadcasting User; and (2) an “Affiliate” of a Transmittal User is any Unicast End User that is under common control with, controls, or is controlled by the Transmittal User. For purposes of this definition, “control” means ownership or control of 50% or greater.
The Exchange proposes to amend the current definition of Affiliate to clarify that the control relationship does not exist only when a User or Hosted Customer is under the common ownership or control of the first User. Instead, an Affiliate relationship exists whenever the two entities are under common control and irrespective of which entity controls the other. In addition, the Exchange proposes to move the description of what “control” means to the end of the definition, to allow for addition of the definitions of Affiliate of Rebroadcasting Users and Transmittal Users.
By using the same concept of “control” for the definitions of Affiliate of Rebroadcasting Users and Transmittal Users as for the general definition, the Exchange believes that the expanded definition would be consistent in its application across the co-location related fees.
The Exchange incurs expenses and expends resources in connection with the support of Rebroadcasting Users and Transmittal Users. Some such costs are indirect, including those associated with overhead and technology infrastructure, administrative, maintenance and operational costs. Since the inception of co-location, there have been numerous network infrastructure improvements performed and administrative controls established. Additionally, the Exchange has automated retransmission facilities for most of its Users that receive multicast transmissions. These facilities benefit Rebroadcasting Users by reducing their operational costs associated with retransmissions to Multicast End Users that are also Users. The network infrastructure has been expanded to keep pace with the increased number of services available to Users, including Rebroadcasting and Transmittal Users, which, in turn, has increased the administrative and operational costs associated with delivery by Rebroadcasting Users and Transmittal Users to their Multicast End Users and Unicast End Users, respectively. The higher fees proposed in connection with the multicast format reflect the Exchange's experience that there are higher maintenance costs associated with supporting and rebroadcasting the multicast format, largely due to bandwidth requirements.
Based on its experience, the Exchange generally provides more direct support to Rebroadcasting Users and Transmittal Users than other Users, typically in the form of network support for the services that Rebroadcasting Users and Transmittal Users provide their Multicast End Users and Unicast End Users, respectively.
By contrast, in its experience the Exchange has found that entities that are Affiliates typically act as one entity, with one infrastructure, one administration, and one network support group. Accordingly, when the Exchange provides network support to a User rebroadcasting or transmitting multicast or unicast data to Affiliate end users, the Exchange is effectively supporting one entity, irrespective of how many Affiliate end users are involved. As a result, its administrative burden and operational costs are reduced in comparison to when it supports a Rebroadcasting User or Transmittal User rebroadcasting or transmitting to a Multicast End User or Unicast End User, respectively.
The Exchange does not provide network support for end users that receive normalized data. Because the normalized data is altered, the User that normalizes and then rebroadcasts normalized data acts as the source of the feed. As a result the User does not need the Exchange's assistance if an issue arises with its normalized feed. Accordingly, the Exchange proposes to exclude a User that normalizes data from the definition of Rebroadcasting User.
Rebroadcasting Users and Transmittal Users need network support, and the Exchange provides it, irrespective of whether their Multicast or Unicast End Users are Users. For this reason, the Exchange provides Rebroadcasting Users and Transmittal Users support related to their Multicast and Unicast End Users both inside and outside of co-location. Accordingly, the Exchange proposes not to limit the definitions of Multicast End Users and Unicast End Users to end users that are also Users.
In order to assess the proposed fees accurately, the Exchange proposes that Rebroadcasting Users and Transmittal Users be required to report the following to the Exchange on a monthly basis: (a) The number of their Multicast End Users and Unicast End Users, and (b) the number of connections to each such Multicast End User and Unicast End User. A User that excludes an Affiliate from its list of Multicast End Users or Unicast End Users consistent with the proposed definitions may be required to certify to the Exchange the Affiliate status of such end user.
Users that are not Rebroadcasting Users or Transmittal Users may be asked to certify as much to the Exchange.
Users may independently set fees that they charge Multicast End Users and Unicast End Users. The Exchange would not be a party to the contractual relationship between Rebroadcasting Users and Transmittal Users and their customers and would not receive a share of any fees charged by Rebroadcasting Users and Transmittal Users for their services.
As is the case with all Exchange co-location arrangements, (i) neither a User nor any of the User's customers would be permitted to submit orders directly to the Exchange unless such User or customer is a Member, a Sponsored Participant or an agent thereof (
Finally, the Exchange proposes to delete the obsolete text in the Price List related to the Hosting Fee of $500 per Hosted Customer that was in effect until December 31, 2015. In addition, the Exchange proposes to delete the “Effective January 1, 2016” text that precedes the current description of the $1,000 monthly charge per cabinet per Hosted Customer for each cabinet in which such Hosted Customer is hosted because it is no longer necessary as these fees are current fees.
The proposed change is not otherwise intended to address any other issues relating to co-location services and/or related fees, and the Exchange is not aware of any problems that Users would have in complying with the proposed change.
The Exchange believes that the proposed rule change is consistent with Section 6(b) of the Act,
The Exchange also believes that the proposed rule change is consistent with Section 6(b)(4) of the Act,
The Exchange believes that the proposal is not designed to permit unfair discrimination between customers, issuers, brokers or dealers. Co-location services would continue to be offered by the Exchange in a manner that would not unfairly discriminate between or among market participants that are otherwise capable of satisfying any applicable co-location fees, requirements, terms and conditions established from time to time by the Exchange. The proposed end user-related definitions, fees and reporting requirements would be applied uniformly to all Users providing multicast and unicast connections and would not unfairly discriminate between similarly situated Users of co-location services.
In addition, the proposed end user fees would fairly and equitably allocate the costs associated with maintaining the Data Center facility, hardware and equipment and related to personnel required for installation and ongoing monitoring, support and maintenance of such service among all Users. In the absence of the proposed end user fees, no charges would be assessed related to the benefit that Multicast End Users and Unicast End Users receive from these services through the Rebroadcasting or Transmittal User from whom they receive data, and the Rebroadcasting or Transmittal Users would thus receive disproportionate benefits.
The Exchange believes that the proposed fees are reasonable in that they are designed to defray applicable expenses incurred and resources expended by the Exchange in support of Rebroadcasting Users and Transmittal Users, including those associated with overhead and technology infrastructure, administrative, maintenance and operational costs, such as the costs of maintaining multiple connections with multiple providers. The Exchange incurs expenses and expends resources in connection with the support of Rebroadcasting Users and Transmittal Users. Some such costs are indirect, including those associated with overhead and technology infrastructure, administrative, maintenance and operational costs. Since the inception of co-location, there have been numerous network infrastructure improvements performed and administrative controls established. Additionally, the Exchange has automated retransmission facilities for most of its Users that receive multicast transmissions. These facilities benefit Rebroadcasting Users by reducing their operational costs associated with retransmissions to Multicast End Users that are also Users. The network infrastructure has been expanded to keep pace with the increased number of services available to Users, including Rebroadcasting and Transmittal Users, which, in turn, has increased the administrative and operational costs associated with delivery by Rebroadcasting Users and Transmittal Users to their Multicast End
In addition, based on its experience, the Exchange believes that the proposed fees are reasonable in that, as a general matter, the Exchange has a greater administrative burden and incurs greater operational costs to support Rebroadcasting Users and Transmittal Users than other Users. The Exchange generally provides more direct support to Rebroadcasting Users and Transmittal Users than other Users, typically in the form of network support for the services that Rebroadcasting Users and Transmittal Users provide their Multicast End Users and Unicast End Users, respectively. Typically when an issue arises, the Exchange and the applicable Rebroadcasting User or Transmittal User would conduct a review to determine the cause of an issue, with the participation of the relevant Multicast or Unicast End User. Based on its experience, the Exchange finds that when the User is a Rebroadcasting User or Transmittal User, pinpointing the issue and providing the needed network support becomes more complicated because each entity involved has its own infrastructure and administration.
The Exchange believes that it is reasonable to charge Rebroadcasting Users and Transmittal Users the proposed fees irrespective of whether their Multicast or Unicast End User is a User, because the Exchange provides Rebroadcasting Users and Transmittal Users support related to their Multicast and Unicast End Users that are outside of co-location as well as those that are Users. If the proposed fees were limited to Rebroadcasting Users and Transmittal Users whose Multicast or Unicast End Users were themselves Users, no charges would be assessed related to the benefit that end users outside of co-location received from these services through the rebroadcasting or transmitting User from whom they received data. As a result, the Rebroadcasting Users and Transmittal Users whose Multicast or Unicast End Users were themselves Users would support a disproportionate share of the Exchange's administrative burden and operational costs relating to end users, and the rebroadcasting or transmitting Users would receive disproportionate benefits.
In addition, the Exchange believes that it is reasonable to charge the same amount for one or two connections because it would encourage Users and their customers to establish two connections and thereby create redundancy in the connections.
The Exchange believes that the proposed amendments to the definition of Affiliates regarding the control relationship are reasonable because they would make the definition more accessible and transparent and provide market participants with clarity as to what entities are considered Affiliates, ensuring that Users exclude all possible Affiliates from the proposed fees and the existing fees for Partial Cabinet Solution bundles. The Exchange believes that setting the common ownership or control threshold in the definition of Affiliates of Multicast End Users and Unicast End Users at 50% is reasonable because it is the same threshold as in the current definition of Affiliates.
Expanding the definition of Affiliates, adding the definitions of Multicast End User, Rebroadcasting User, Unicast End User, and Transmittal User, and adding the proposed note on the reporting requirements to the Price List would make such definitions and requirements accessible and transparent and provide market participants with clarity as to the application of the proposed fees. The Exchange believes that the proposal would remove impediments to, and perfect the mechanisms of, a free and open market and a national market system and, in general, protect investors and the public interest because by including the definitions and reporting requirements in the Price List, the proposed change would provide all Users with clarity as to the availability and application of co-location services and fees. Such end user-related definitions, fees and reporting requirements would be applied uniformly to all Users providing multicast and unicast connections and would not unfairly discriminate between similarly situated Users of co-location services.
The Exchange believes that excluding Affiliates from the definitions of Multicast End Users and Unicast End Users is reasonable because, in its experience, when the Exchange provides network support to a User rebroadcasting or transmitting multicast or unicast data to Affiliate end users, the Exchange's administrative burden and operational costs are reduced in comparison to when it supports a Rebroadcasting User or Transmittal User rebroadcasting or transmitting multicast or unicast data to a Multicast End User or Unicast End User, respectively. In its experience, entities that are Affiliates typically act as one entity, with one infrastructure, one administration, and one network support group. Accordingly, when the Exchange provides network support to a User rebroadcasting or transmitting multicast or unicast data to Affiliate end users, the Exchange is effectively supporting one entity, irrespective of how many Affiliate end users are involved.
The Exchange believes that having the definition of Affiliates encompass non-Users is reasonable because in its experience entities that are Affiliates typically act as one entity irrespective of whether one or more of them are not Users. If the definition did not encompass non-Users, a User would have to pay the proposed fee if it rebroadcast or transmitted multicast or unicast data to an end user that was not a User but otherwise met the definition of Affiliate. However, the Exchange would incur the same costs irrespective of whether the end user is itself a User or is located outside of co-location. Accordingly, the Exchange believes that having the definition of Affiliates encompass non-Users avoids disparate treatment of a Rebroadcasting User or Transmittal User that has a non-User as its Affiliate, as compared to one that has a User as its Affiliate.
The Exchange believes that it is reasonable that, under the proposed definition, two Multicast End Users or Unicast End Users would not be considered Affiliates even if they otherwise met the requirements of the definition. The Exchange has no direct contract with a Rebroadcasting User's Multicast End Users for connectivity to Exchange data, or with a Transmittal User's Unicast End Users for the transmission of messages to and from the Exchange. As a result, the Exchange would not be able to independently ascertain which Multicast and Transmittal Users met the definition of Affiliates, and would have no standing to require such Multicast and Unicast End Users to report their Affiliates. The Exchange believes it would create an unnecessary administrative burden on Users to require Rebroadcasting Users and Transmittal Users to determine which, if any, of their Multicast and Unicast End Users were affiliated, and to report such to the Exchange.
The Exchange believes that the proposal to exclude Affiliates from the definitions of Multicast End User and Unicast End User is not designed to permit unfair discrimination between customers, issuers, brokers or dealers because the proposed rule avoids disparate treatment of Users that have
The Exchange believes that the proposal to exclude from the definition of Multicast End Users a User that normalizes raw data before rebroadcasting it to its customers is reasonable and is not designed to permit unfair discrimination between customers, issuers, brokers or dealers because a User that normalizes and then rebroadcasts normalized data acts as the source of the feed, and so does not need the Exchange's assistance if an issue arises with its normalized feed. As a result, the Exchange does not incur the same costs in relation to end users of normalized data as it does in relation to Multicast End Users.
The Exchange believes that the proposal to exclude from the definition of Unicast End User those customers of a Transmittal User (and customers of Users' customers) that send all orders to a Floor broker for representation on the Exchange is reasonable because it would encourage sending orders to Floor brokers for execution, thereby encouraging additional displayed liquidity on the Exchange. This would encourage the execution of transactions on a public registered exchange, thereby promoting public price discovery—an objective fully consistent with the Act.
The Exchange believes that the proposal to have Users report the number of their Multicast End Users and Unicast End Users and the number of connections to each such Multicast End User and Unicast End User is reasonable because it will ensure that the proposed fees are assessed accurately and will provide market participants with clarity as to how the fees will be assessed.
For the reasons above, the proposed change would not unfairly discriminate between or among market participants that are otherwise capable of satisfying any applicable co-location fees, requirements, terms and conditions established from time to time by the Exchange.
Finally, the Exchange believes that it is subject to significant competitive forces, as described below in the Exchange's statement regarding the burden on competition.
For these reasons, the Exchange believes that the proposal is consistent with the Act.
In accordance with Section 6(b)(8) of the Act,
In addition, the Exchange believes that the proposed end user fees would not impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act because they would fairly and equitably allocate the costs associated with maintaining the Data Center facility, hardware and equipment and related to personnel required for installation and ongoing monitoring, support and maintenance of such service among all Users, as well as applicable expenses incurred and resources expended by the Exchange in support of Rebroadcasting Users and Transmittal Users. In the absence of the proposed end user fees, no charges would be assessed related to the benefit that Multicast End Users and Unicast End Users receive from these services through the Rebroadcasting or Transmittal User from whom they receive data, and the Rebroadcasting or Transmittal Users would thus receive disproportionate benefits.
The Exchange believes that the proposed end user fees would not impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act because the Exchange has tailored the proposed definition of Affiliate to include User and non-User Affiliates. If the proposed fees were limited to Rebroadcasting Users and Transmittal Users whose Multicast or Unicast End Users were themselves Users, no charges would be assessed relating to the benefit that end users outside of co-location received from these services through the rebroadcasting or transmitting User from whom they received data. As a result, the Rebroadcasting Users and Transmittal Users whose Multicast or Unicast End Users were themselves Users would support a disproportionate share of the Exchange's administrative burden and operational costs relating to end users, and the rebroadcasting or transmitting Users would receive disproportionate benefits.
The Exchange believes that the proposed end user fees would not impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act because the Exchange has excluded Affiliates from the proposed definitions of Multicast End Users and Unicast End Users. As a result, the proposed end user fees exclude fees related to end users that, in the Exchange's experience, typically act as one entity, with one infrastructure and one administration.
The Exchange believes that the proposal to exclude from the definition of Unicast End User those customers of a Transmittal User (and customers of Users' customers) that send all orders to a Floor broker for representation on the Exchange is reasonable because it would encourage providing liquidity on the Exchange, thereby contributing to the Exchange's competitiveness with other markets. In addition, the Exchange believes that expanding the definition of Affiliates and adding the definitions of Multicast End User, Rebroadcasting User, Unicast End User, and Transmittal User to the Price List would make such definitions accessible and transparent and provide market participants with clarity as to the availability and application of the proposed fees.
Finally, the Exchange notes that it operates in a highly competitive market
No written comments were solicited or received with respect to the proposed rule change.
Within 45 days of the date of publication of this notice in the
Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:
• Use the Commission's Internet comment form (
• Send an email to
• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.
For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
Notice is hereby given that pursuant to the Paperwork Reduction Act of 1995 (“PRA”) (44 U.S.C. 3501
Rule 15a-6 provides conditional exemptions from the requirement to register as a broker-dealer pursuant to Section 15 of the Exchange Act (15 U.S.C. 78o) for foreign broker-dealers that engage in certain specified activities involving U.S. persons. In particular, Rule 15a-6(a)(3) provides an exemption from broker-dealer registration for foreign broker-dealers that solicit and effect transactions with or for U.S. institutional investors or major U.S. institutional investors through a registered broker-dealer, provided that the U.S. broker-dealer, among other things, obtains certain information about, and consents to service of process from, the personnel of the foreign broker-dealer involved in such transactions, and maintains certain records in connection therewith.
These requirements are intended to ensure (a) that the registered broker-dealer will receive notice of the identity of, and has reviewed the background of, foreign personnel who will contact U.S. investors, (b) that the foreign broker-dealer and its personnel effectively may be served with process in the event enforcement action is necessary, and (c) that the Commission has ready access to information concerning these persons and their U.S. securities activities. Commission staff estimates that approximately 2,000 U.S. registered broker-dealers will spend an average of two hours of clerical staff time and one hour of managerial staff time per year obtaining the information required by the rule, resulting in a total aggregate burden of 6,000 hours per year for complying with the rule. Assuming an hourly cost of $63
In general, the records to be maintained under Rule 15a-6 must be kept for the applicable time periods as set forth in Rule 17a-4 (17 CFR 240.17a-4) under the Exchange Act or,
An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information under the PRA unless it displays a currently valid OMB control number. The public may view background documentation for this information collection at the following Web site,
Notice is hereby given that, pursuant to the Paperwork Reduction Act of 1995 (44 U.S.C. 3501
The title for the collection of information is “Rule 204A-1 (17 CFR 275.204A-1) under the Investment Advisers Act of 1940.” (15 U.S.C. 80b-1
The respondents to this information collection are investment advisers registered with the Commission. The Commission has estimated that compliance with rule 204A-1 imposes a burden of approximately 118 hours per adviser annually based on an average adviser having 84 access persons. Our latest data indicate that there were 12,028 advisers registered with the Commission. Based on this figure, the Commission estimates a total annual burden of 1,418,703 hours for this collection of information.
Rule 204A-1 does not require recordkeeping or record retention. The collection of information requirements under the rule is mandatory. The information collected pursuant to the rule is not filed with the Commission, but rather takes the form of communications between advisers and their supervised persons. Investment advisers use the information collected to control and assess the personal trading activities of their supervised persons. Responses to the reporting requirements will be kept confidential to the extent each investment adviser provides confidentiality under its particular practices and procedures. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid control number.
The public may view the background documentation for this information collection at the following Web site,
Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (the “Act”),
The Exchange filed a proposal to adopt Exchange Rule 14.10 setting forth additional requirements for the listing of securities that are issued by the Exchange or any of its affiliates as well as the monitoring of such securities' trading activity on the Exchange. Proposed Rule 14.10 is based on Bats BZX Exchange, Inc. (“BZX”) Rule 14.3(e), which was recently amended and filed for immediate effectiveness with the Commission.
The text of the proposed rule change is available at the Exchange's Web site at
In its filing with the Commission, the Exchange included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in Sections A, B, and C below, of the most significant parts of such statements.
The Exchange is proposing to adopt Rule 14.10 setting forth reporting requirements on the Exchange should the Exchange or EDGX Affiliate list a security on the Exchange (the “Affiliate Security”). Proposed Rule 14.10(a)(1) would define “EDGX Affiliate” as “the Exchange and any entity that directly or indirectly, through one or more intermediaries, controls, is controlled by, or is under common control with the Exchange, where ‘control' means that one entity possesses, directly or indirectly, voting control of the other entity either through ownership of capital stock or other equity securities or through majority representation on the board of directors or other management body of such entity.” Proposed Rule 14.10(a)(2) would define “Affiliate Security” as “any security issued by an EDGX Affiliate or any Exchange-listed option on any such security, with the exception of Portfolio Depositary Receipts as defined in Rule 14.8(d) and Investment Company Units as defined in Rule 14.2.”
In the event that an EDGX Affiliate seeks to list an Affiliate Security, paragraph (b)(1) of proposed Rule 14.10 would require that prior to the initial listing of the Affiliate Security on the Exchange, Exchange personnel shall determine that such security satisfies the Exchange's rules for listing, and such finding must be approved by the Regulatory Oversight Committee of the Exchange's Board of Directors.
Proposed paragraph (b)(2) of proposed Rule 14.10 would state that throughout the continued listing of the Affiliate Security on the Exchange, the Exchange will prepare a quarterly report for the Regulatory Oversight Committee of the Exchange's Board of Directors and that such report describe the Exchange's monitoring of the Affiliate Security's compliance with the Exchange's listing standards. Sub-paragraph (A) of proposed Rule 14.10(b)(2) would require the report include a description of the Affiliate Security's compliance with the Exchange's minimum share price requirement, and, sub-paragraph (B) would require the report to describe the Affiliate Security's compliance with each of the quantitative continued listing requirements.
Sub-paragraph (3) of proposed Rule 14.10(b) would require the Exchange to commission an annual review and report by an independent accounting firm of the compliance of the Affiliate Security with the Exchange's listing requirements. The Exchange would be required to promptly furnish a copy of this annual report to the Regulatory Oversight Committee of the Exchange's Board of Directors.
Sub-paragraph (4) of proposed Rule 14.10(b) would state that in the event the Exchange determines that the EDGX Affiliate is not in compliance with any of the Exchange's listing standards, the Exchange is required to notify the issuer of such non-compliance promptly and request a plan of compliance. The Exchange would also be required to file a report with the Commission within five business days of providing such notice to the issuer of its non-compliance. The required report would identify the date of the non-compliance, type of non-compliance, and any other material information conveyed to the issuer in the notice of non-compliance. Within five business days of receipt of a plan of compliance from the issuer, the Exchange would again be required to notify the Commission of such receipt, whether the plan of compliance was accepted by the Exchange or what other action was taken with respect to the plan and the time period provided to regain compliance with the Exchange's listing standards, if any.
Sub-paragraph (c) of proposed Rule 14.10 would require that throughout the trading of an Affiliate Security on the Exchange, the Exchange prepare a quarterly report on the Affiliate Security for the Regulatory Oversight Committee of the Exchange's Board of Directors that describes the Exchange's monitoring of the trading of the Affiliate Security, including summaries of all related surveillance alerts, complaints, regulatory referrals, trades cancelled or adjusted pursuant to Exchange Rules, investigations, examinations, formal and informal disciplinary actions, exception reports and trading data used to ensure the Affiliate Security's compliance with the Exchange's listing and trading rules.
Lastly, paragraph (d) of proposed Rule 14.10 would require the Exchange to promptly provide a copy of the reports required by sub-paragraphs (b) and (c) described above to the Commission.
The listing of an Affiliate Security or where an Affiliate Security is traded on the Exchange could potentially create a conflict of interest between the Exchange's self-regulatory responsibility to vigorously oversee the listing and trading of the stock on its market, and its own commercial or economic interests. Such “self-listing” may raise questions as to the Exchange's ability to independently and effectively enforce its rules against an affiliate or the operator/owner of its facility. In addition, such listing has the potential to exacerbate possible conflicts that may arise when the Exchange oversees competitors that may also be listed or traded on the Exchange. The Exchange believes that the proposed rule change,
The Exchange believes that its proposal is consistent with the requirements of the Act and the rules and regulations thereunder that are applicable to a national securities exchange, and, in particular, with the requirements of Section 6(b) of the Act.
The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The proposed rule change is not designed to address any competitive issues, but rather set forth the Exchange's controls that are in place to address the potential conflicts of interest that may arise in the listing of Affiliate Securities on the Exchange.
Written comments were neither solicited nor received.
The Exchange has filed the proposed rule change pursuant to Section 19(b)(3)(A)(iii) of the Act
A proposed rule change filed under Rule 19b-4(f)(6) under the Act
At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings to determine whether the proposed rule should be approved or disapproved.
Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:
• Use the Commission's Internet comment form (
• Send an email to
• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.
For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
Notice is hereby given that Aldine Capital Fund II, L.P., 30 West Monroe Street, Suite 710, Chicago, IL 60603, a Federal Licensee under the Small Business Investment Act of 1958, as amended (“the Act”), in connection with the financing of a small concern, has sought an exemption under Section 312 of the Act and Section 107.730, Financings which constitute Conflicts of Interest of the U.S. Small Business Administration (“SBA”) Rules and Regulations (13 CFR 107.730). Aldine Capital Fund II, L.P. proposes to provide debt and equity financing to Rock Energy Systems, LLC, 1007 Church Street, Suite 420, Evanston, IL 60201.
The financing is brought within the purview of § 107.730(a) of the Regulations because Aldine SBIC Fund, L.P. and Aldine Capital Fund, L.P., Associates of Aldine Capital Fund II, L.P., hold an ownership interest in Rock Energy Systems, LLC of greater than 10 percent. Therefore, Rock Energy Systems, LLC is an Associate of Aldine Capital Fund II, L.P. and the transaction is considered financing an Associate. In addition, proceeds of this transaction will be used, in part, to discharge obligations to Associates Aldine SBIC Fund, L.P. and Aldine Capital Fund, L.P. Both characteristics of this transaction require prior SBA exemption.
Notice is hereby given that any interested person may submit written comments on the transaction, within fifteen days of the date of this publication, to the Associate Administrator for Investment and Innovation, U.S. Small Business Administration, 409 Third Street SW., Washington, DC 20416.
U.S. Small Business Administration.
Notice.
This is a notice of an Administrative declaration of a disaster for the State of OKLAHOMA dated 04/13/2016.
Submit completed loan applications to: U.S. Small Business Administration, Processing And Disbursement Center, 14925 Kingsport Road, Fort Worth, TX 76155.
A. Escobar, Office of Disaster Assistance, U.S. Small Business Administration, 409 3rd Street SW., Suite 6050, Washington, DC 20416.
Notice is hereby given that as a result of the Administrator's disaster declaration, applications for disaster loans may be filed at the address listed above or other locally announced locations.
The following areas have been determined to be adversely affected by the disaster:
The Interest Rates are:
The number assigned to this disaster for physical damage is 14696 B and for economic injury is 14697 0.
The State which received an EIDL Declaration # is Oklahoma.
U.S. Small Business Administration
Amendment 4.
This is an amendment of the Presidential declaration of a major disaster for the State of Mississippi (FEMA-4268-DR), dated 03/25/2016.
Submit completed loan applications to: U.S. Small Business Administration, Processing and Disbursement Center, 14925 Kingsport Road, Fort Worth, TX 76155.
A. Escobar, Office of Disaster Assistance, U.S. Small Business Administration, 409 3rd Street SW., Suite 6050, Washington, DC 20416.
The notice of the Presidential disaster declaration for the State of MISSISSIPPI, dated 03/25/2016 is hereby amended to include the following areas as adversely affected by the disaster:
All other information in the original declaration remains unchanged.
U.S. Small Business Administration.
Amendment 3.
This is an amendment of the Presidential declaration of a major disaster for the State of Mississippi (FEMA-4268-DR), dated 03/25/2016.
Submit completed loan applications to: U.S. Small Business Administration, Processing and Disbursement Center, 14925 Kingsport Road, Fort Worth, TX 76155
A. Escobar, Office of Disaster Assistance, U.S. Small Business Administration, 409 3rd Street SW., Suite 6050, Washington, DC 20416.
The notice of the President's major disaster declaration for the State of Mississippi, dated 03/25/2016 is hereby amended to establish the incident period for this disaster as beginning 03/09/2016 and continuing through 03/29/2016.
All other information in the original declaration remains unchanged.
U.S. Small Business Administration.
Notice.
This is a notice of an Administrative declaration of a disaster for the State of ILLINOIS dated 04/13/2016.
Submit completed loan applications to: U.S. Small Business Administration, Processing and Disbursement Center, 14925 Kingsport Road, Fort Worth, TX 76155.
A. Escobar, Office of Disaster Assistance, U.S. Small Business Administration, 409 3rd Street SW., Suite 6050, Washington, DC 20416
Notice is hereby given that as a result of the Administrator's disaster declaration, applications for disaster loans may be filed at the address listed above or other locally announced locations.
The following areas have been determined to be adversely affected by the disaster:
The Interest Rates are:
The number assigned to this disaster for physical damage is 14694 B and for economic injury is 14695 0.
The States which received an EIDL Declaration # are ILLINOIS and INDIANA.
Department of State.
Notice of release of the Department of State's FY 2015 Service Contract Inventory.
Acting in compliance with Sec. 743 of Division C of the Consolidated Appropriations Act of 2010 (Pub. L. 111-117), the Department of State is publishing this notice to advise the public of the availability of the FY 2015 Service Contract Inventory. The FY 2015 Service Contract Inventory includes the Planned Analysis, and Summary, Detailed, and Supplement Reports. The FY 2014 Meaningful Analysis is also available.
The inventory was developed in accordance with guidance issued on November 5, 2010, December 19, 2011, November 25, 2014, and September 8, 2015 by the Office of Management and Budget (OMB), Office of Federal Procurement Policy (OFPP). The Department of State has posted its FY 2015 Service Contract Inventory and FY 2014 Meaningful Analysis at the following link:
The inventory is available on the Department's Web site as of April 14, 2016.
Marlon Henry, Management and Program Analyst, A/EX/CSM, 202-485-7210,
Notice is hereby given of the following determinations: Pursuant to the authority vested in me by the Act of October 19, 1965 (79 Stat. 985; 22 U.S.C. 2459), E.O. 12047 of March 27, 1978, the Foreign Affairs Reform and Restructuring Act of 1998 (112 Stat. 2681,
For further information, including a list of the imported objects, contact the Office of Public Diplomacy and Public Affairs in the Office of the Legal Adviser, U.S. Department of State (telephone: 202-632-6471; email:
Notice is hereby given of the following determinations: Pursuant to the authority vested in me by the Act of October 19, 1965 (79 Stat. 985; 22 U.S.C. 2459), E. O. 12047 of March 27, 1978, the Foreign Affairs Reform and Restructuring Act of 1998 (112 Stat. 2681,
For further information, including an object list, contact the Office of Public Diplomacy and Public Affairs in the Office of the Legal Adviser, U.S. Department of State (telephone: 202-632-6471; email:
Notice is hereby given of the following determinations: Pursuant to
For further information, including a lists of the imported objects, contact the Office of Public Diplomacy and Public Affairs in the Office of the Legal Adviser, U.S. Department of State (telephone: 202-632-6471; email:
Notice is hereby given of the following determinations: Pursuant to the authority vested in me by the Act of October 19, 1965 (79 Stat. 985; 22 U.S.C. 2459), E. O. 12047 of March 27, 1978, the Foreign Affairs Reform and Restructuring Act of 1998 (112 Stat. 2681,
For further information, including a list of the imported objects, contact the Office of Public Diplomacy and Public Affairs in the Office of the Legal Adviser, U.S. Department of State (telephone: 202-632-6471; email:
Federal Aviation Administration (FAA), DOT.
Notice.
This notice contains a summary of a petition seeking relief from specified requirements of Title 14 of the Code of Federal Regulations. The purpose of this notice is to improve the public's awareness of, and participation in, the FAA's exemption process. Neither publication of this notice nor the inclusion or omission of information in the summary is intended to affect the legal status of the petition or its final disposition.
Comments on this petition must identify the petition docket number and must be received on or before May 12, 2016.
Send comments identified by docket number FAA-2002-12455 using any of the following methods:
•
•
•
•
For technical questions concerning this action, contact Nia Daniels, 800 Independence Avenue SW., Washington, DC 20591, (202) 267-7626.
This notice is published pursuant to 14 CFR 11.85.
Federal Aviation Administration (FAA), DOT.
Notice.
This notice contains a summary of a petition seeking relief from specified requirements of Title 14 of the Code of Federal Regulations. The purpose of this notice is to improve the public's awareness of, and participation in, the FAA's exemption process. Neither publication of this notice nor the inclusion or omission of information in the summary is intended to affect the legal status of the petition or its final disposition.
Comments on this petition must identify the petition docket number and must be received on or before May 12, 2016.
Send comments identified by docket FAA-2016-0030 using any of the following methods:
•
•
•
•
For technical questions concerning this action, contact Nia Daniels, 800 Independence Avenue SW., Washington, DC 20591, (202) 267-7626.
This notice is published pursuant to 14 CFR 11.85.
Federal Aviation Administration (FAA), DOT.
Notice.
This notice contains a summary of a petition seeking relief from specified requirements of Title 14 of the Code of Federal Regulations. The purpose of this notice is to improve the public's awareness of, and participation in, the FAA's exemption process. Neither publication of this notice nor the inclusion or omission of information in the summary is intended to affect the legal status of the petition or its final disposition.
Comments on this petition must identify the petition docket number and must be received on or before May 12, 2016.
Send comments identified by docket number FAA-2016-5003 using any of the following methods:
•
•
•
•
Alphonso W. Pendergrass II (202) 267-4713, Office of Rulemaking, Federal Aviation Administration, 800 Independence Avenue SW., Washington, DC 20591. This notice is published pursuant to 14 CFR 11.85.
Federal Aviation Administration (FAA), DOT.
Notice.
This notice contains a summary of a petition seeking relief from specified requirements of Title 14 of the Code of Federal Regulations. The purpose of this notice is to improve the public's awareness of, and participation in, the FAA's exemption process. Neither publication of this notice nor the inclusion or omission of information in the summary is intended to affect the legal status of the petition or its final disposition.
Comments on this petition must identify the petition docket number and must be received on or before May 12, 2016.
Send comments identified by docket number FAA-2016-0363 using any of the following methods:
•
•
•
•
For technical questions concerning this action, contact Joshua Parker, (202-267-1538), 800 Independence Avenue SW., Washington, DC 20591.
This notice is published pursuant to 14 CFR 11.85.
Federal Aviation Administration (FAA), DOT.
Request for Public Comments.
Under the provisions of Title 49, U.S.C. Section 47153(d), notice is being given that the FAA is considering a property swap at Augusta State Airport in Augusta, ME.
The purpose of the land swap between the State of Maine (Airport Sponsor) and Dragon Products Company, Inc., to resolve a compliance issue. The 13 acre parcel is at the bottom of the slope on the departure end of RW 35, and lies approximately 300' below the elevation of the end of the Runway. This portion of land is not considered useable for aeronautical purposes based upon its location and elevation. The parcel currently contains a pile of hardened concrete spoils placed there by Dragon Products Company, Inc. The solutions to mitigate this situation include removal of the spoils pile, which would be cost prohibitive, or release the land to Dragon Products Company, Inc. as part of an equal value parcel exchange. The State of Maine determined the parcel exchange as the best alternative. The parcel that Dragon has offered for exchange abuts the Augusta State Airport property on one side and City of Augusta property on another. The Offered Parcel would be advantageous to the State of Maine for potential non-aeronautical airport revenue generating purposes. The State of Maine would retain all avigation rights over both parcels.
Comments must be received on or before May 23, 2016.
You may send comments using any of the following methods:
•
•
•
•
Interested persons may inspect the request and supporting documents by contacting the FAA at the address listed under
Mr. Jorge E. Panteli, Compliance and Land Use Specialist, Federal Aviation Administration New England Region Airports Division, 1200 District Avenue, Burlington, Massachusetts, Telephone 781-238-7618.
Federal Aviation Administration (FAA), DOT.
Notice.
This notice contains a summary of a petition seeking relief from specified requirements of Title 14 of the Code of Federal Regulations. The purpose of this notice is to improve the public's awareness of, and participation in, the FAA's exemption process. Neither publication of this notice nor the inclusion or omission of information in the summary is intended to affect the legal status of the petition or its final disposition.
Comments on this petition must identify the petition docket number and must be received on or before May 12, 2016.
Send comments identified by docket number FAA-2016-0934 using any of the following methods:
•
•
•
•
Alphonso W. Pendergrass II, (202) 267-4713, Office of Rulemaking, Federal Aviation Administration, 800 Independence Avenue SW., Washington, DC 20591.
This notice is published pursuant to 14 CFR 11.85.
Federal Aviation Administration (FAA), DOT.
Notice.
This notice contains a summary of a petition seeking relief from specified requirements of title 14 of the Code of Federal Regulations. The purpose of this notice is to improve the public's awareness of, and participation in, the FAA's exemption process. Neither publication of this notice nor the inclusion or omission of information in the summary is intended to affect the legal status of the petition or its final disposition.
Comments on this petition must identify the petition docket number and must be received on or before May 12, 2016.
Send comments identified by docket number FAA-2016-4676 using any of the following methods:
•
•
•
•
For technical questions concerning this action, contact Nia Daniels, (202) 267-9677, 800 Independence Avenue SW., Washington, DC, 20591.
This notice is published pursuant to 14 CFR 11.85.
The Department of Veterans Affairs gives notice under the Federal Advisory Committee Act, 5 U.S.C. App. 2, that the Clinical Science Research and Development Service Cooperative Studies Scientific Evaluation Committee will hold a meeting on June 29, 2016, at the American Association of Airport Executives, 601 Madison Street, Alexandria, VA. The meeting will begin at 8:30 a.m. and end at 2:30 p.m.
The Committee advises the Chief Research and Development Officer through the Director of the Clinical Science Research and Development Service on the relevance and feasibility of proposed projects and the scientific validity and propriety of technical details, including protection of human subjects.
The session will be open to the public for approximately 1 hour and 45 minutes at the start of the meeting for the discussion of administrative matters and the general status of the program. The remaining portion of the meeting will be closed to the public for the Committee's review, discussion, and evaluation of research and development applications.
During the closed portion of the meeting, discussions and recommendations will deal with qualifications of personnel conducting the studies, staff and consultant critiques of research proposals and similar documents, and the medical records of patients who are study subjects, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy. As provided by section 10(d) of Public Law 92-463, as amended, closing portions of this meeting is in accordance with 5 U.S.C. 552b(c)(6) and (c)(9)(B).
The committee will not accept oral comments from the public for the open portion of the meeting. Those who plan to attend or wish additional information should contact Dr. Grant Huang, Acting Director, Cooperative Studies Program (10P9CS), Department of Veterans Affairs, 810 Vermont Avenue NW., Washington, DC 20420, at (202) 443-5700 or by email at
The Department of Veterans Affairs (VA) gives notice under the Federal Advisory Committee Act, 5 U.S.C. App. 2 that a meeting of the National Academic Affiliations Council will be held May 5, 2016-May 6, 2016 in the Office of Academic Affiliations (OAA) Conference Room, 1800 G Street NW., Suite 870, Washington, DC. The May 5, 2016 session will begin at 9:00 a.m. and end at 4:30 p.m. The May 6, 2016 session will begin at 9 a.m. and adjourn at 12:00 p.m. The meeting is open to the public.
The purpose of the Council is to advise the Secretary on matters affecting partnerships between VA and its academic affiliates.
On May 5, 2016, the Council will host two expert panels with representatives from veterans' service organizations and professional staff from the House and Senate Veterans' Affairs Committees. Following the expert panels, the Council will receive updates on the Graduate Medical Education (GME) expansion authorized by the 2014 Veterans Access, Choice, and Accountability (VACAA) Act; the progress towards the establishment of joint ventures with academic affiliates; the role of academic affiliates in the proposed VA tiered networks; and challenges involving the timely issuance of personal identity verification cards to trainees. In the afternoon, the Council will host a conversation with Dr. David A. Shulkin, the Under Secretary for Health. On May 6, 2016, the Council will receive updates on the Veterans Equitable Resource Allocation methodology, and VA policy guidance on Deferred Action for Childhood Arrivals. At the conclusion of the May 6, 2016 session, the VA Advisory Committee Management Office will provide an informational briefing to Council members. The Council will receive public comments from 4:15 p.m. to 4:30 p.m. on May 6, 2016 and again from 11:15 a.m. to 11:30 a.m. on May 6, 2016.
Interested persons may attend and present oral statements to the Council. A sign-in sheet for those who want to give comments will be available at the meeting. Individuals who speak are invited to submit a 1-2 page summary of their comments at the time of the meeting for inclusion in the official meeting record. Oral presentations will be limited to five minutes or less, depending on the number of participants. Interested parties may also provide written comments for review by the Council prior to the meeting or at any time, by email to,
Federal Highway Administration (FHWA), Department of Transportation (DOT).
Notice of proposed rulemaking (NPRM).
This NPRM is the third in a series of three related NPRMs that together establishes a set of performance measures for State departments of transportation (State DOT) and Metropolitan Planning Organizations (MPO) to use as required by Moving Ahead for Progress in the 21st Century Act (MAP-21). The measures proposed in this third NPRM would be used by State DOTs and MPOs to assess the performance of the Interstate and non-Interstate National Highway System (NHS) for the purpose of carrying out the National Highway Performance Program (NHPP); to assess freight movement on the Interstate System; and to assess traffic congestion and on-road mobile source emissions for the purpose of carrying out the Congestion Mitigation and Air Quality Improvement (CMAQ) Program. This third performance measure NPRM also includes a discussion that summarizes all three of the national performance management measures proposed rules and the comprehensive regulatory impact analysis (RIA) to include all three NPRMs.
Comments must be received on or before August 20, 2016. Late comments will be considered to the extent practicable.
You may submit comments identified by the docket number FHWA-2013-0020 by any one of the following methods:
For technical information: Francine Shaw Whitson, Office of Infrastructure, (202) 366-8028; for legal information: Anne Christenson, Office of Chief Counsel, (202) 366-0740, Federal Highway Administration, 1200 New Jersey Avenue SE., Washington, DC 20590. Office hours are from 8:00 a.m. to 4:30 p.m. ET, Monday through Friday, except Federal holidays.
The FHWA has published two additional NPRMs to establish the remaining measures required under 23 U.S.C. 150(c). The first performance measure NPRM proposed establishment of measures to carry out the Highway Safety Improvement Program (HSIP) and to assess serious injuries and fatalities, both in number and expressed as a rate, on all public roads. On March 15, 2016, FHWA published a final rule (FR Vol. 81 No. 50) covering the safety-related elements of the Federal-aid Highway Performance Measures Rulemaking. The second performance measure NPRM proposed establishment of performance measures to assess pavement and bridge conditions on the Interstate System and non-Interstate NHS for the purpose of carrying out the NHPP. This NPRM, the third performance measure NPRM, focuses on measures for the performance of the NHS, freight movement on the Interstate System, and the CMAQ Program.
This last NPRM includes a discussion that summarizes all three of the rulemakings, both finished and underway, that will establish the measures required under 23 U.S.C. 150(c).
The MAP-21 (Pub. L. 112-141) transforms the Federal-aid highway program by establishing new requirements for performance management to ensure the most efficient investment of Federal transportation funds. Performance management increases the accountability and transparency of the Federal-aid highway program and provides for a framework to support improved investment decisionmaking through a focus on performance outcomes for key national transportation goals. As part of performance management, recipients of Federal-aid highway funds would make transportation investments to achieve performance targets that make progress toward the following national goals:
• Congestion reduction.—To achieve a significant reduction in congestion on the NHS.
• System reliability.—To improve the efficiency of the surface transportation system.
• Freight movement and economic vitality.—To improve the national freight network, strengthen the ability of rural communities to access national and international trade markets, and support regional economic development.
• Environmental sustainability.—To enhance the performance of the transportation system while protecting and enhancing the natural environment.
The purpose of this rulemaking is to implement MAP-21 performance management requirements. Prior to MAP-21, there were no explicit requirements for State DOTs to demonstrate how their transportation program supported national performance outcomes. State DOTs were not required to measure condition/performance, to establish targets, to assess progress toward targets, or to report condition/performance in a nationally consistent manner that FHWA could use to assess the condition/performance of the entire system. Without States reporting on the above mentioned factors, it is difficult for FHWA to look at the effectiveness of the Federal-aid highway program as a means to address surface transportation performance at a national level.
This proposed rule is one of several rulemakings that DOT is or will be conducting to implement MAP-21's new performance management framework. The collective rulemakings will establish the regulations needed to more effectively evaluate and report on surface transportation performance across the country. This rulemaking proposes regulations that would:
• Provide for greater consistency in the reporting of condition/performance;
• Require the establishment of targets that can be aggregated at the national level;
• Require reporting in a consistent manner on progress achievement; and
• Require State DOTs to make significant progress.
State DOTs would be expected to use the information and data generated as a result of the new regulations to better inform their transportation planning and programming decisionmaking. The new performance aspects of the Federal-aid program that would result from this rulemaking would provide FHWA the ability to better communicate a national performance story and to more reliably assess the impacts of Federal funding investments. The FHWA is in the process of creating a new public Web site to help communicate the national performance story. The Web site will likely include infographics, tables, charts, and descriptions of the performance data that the State DOTs would be reporting to FHWA.
The FHWA is required to establish performance measures through a rulemaking to assess performance in 12 areas
This rulemaking seeks to establish national measures for areas 8, 9, 10, 11, and 12, in the above list. This NPRM proposes to establish performance measures to assess the performance of the Interstate System and non-Interstate NHS for the purpose of carrying out the NHPP; to assess freight movement on the Interstate System; and to assess traffic congestion and on-road mobile source emissions for the purpose of carrying out the CMAQ program areas. The two proposed measures to assess performance of the Interstate are (1) Percent of the Interstate System providing for Reliable Travel, and (2) Percent of the Interstate System where peak hour travel times meet expectations. The two proposed measures to assess performance of the non-Interstate NHS are (1) Percent of the non-Interstate NHS providing for Reliable Travel and (2) Percent of the non-Interstate NHS where peak hour travel times meet expectations. The two proposed measures to assess freight movement on the Interstate System are (1) Percent of the Interstate System Mileage providing for Reliable Truck Travel Time, and (2) Percent of the Interstate System Mileage Uncongested. The proposed measure to assess traffic congestion is Annual Hours of Excessive Delay per Capita. Lastly, the proposed measure to assess on-road mobile source emissions is Total Tons of Emissions Reduced from CMAQ Projects for Applicable Criteria Pollutants and Precursors.
In addition, this NPRM builds on the framework of the previous performance rulemakings and the process proposed for State DOTs and MPOs to establish targets for each of the measures; the methodology to determine whether State DOTs have achieved or made significant progress toward their NHPP or National Highway Freight Program (NHFP) targets (targets for national measures areas 5, 6, 7, 10, 11, and 12, in the above list); and the process for State DOTs to use to report on progress toward achieving their targets.
The first performance rule established measures to be used by State DOTs to assess performance and to carry out the HSIP; the process for State DOTs and MPOs to use to establish safety targets; the methodology to determine whether State DOTs have achieved their safety targets; and the process for State DOTs to report on progress toward achieving their safety targets. The second performance rule proposed the
With this third rule, FHWA proposes the establishment of: Performance measures to be used by State DOTs and MPOs to assess performance of the Interstate System and non-Interstate NHS, traffic congestion, on-road mobile source emissions, and freight movement on the Interstate System; the process for State DOTs and MPOs to use to establish targets; the methodology to determine whether State DOTs have achieved or made significant progress toward their NHPP and NHFP performance targets; and the process for State DOTs to report on progress toward achieving their targets. This NPRM includes one general information area (Subpart A) that covers definitions, target establishment, reporting on progress, and how determinations would be made on whether State DOTs have achieved or made significant progress toward NHPP and NHFP targets. Subparts E through H propose performance measures in four areas: (1) National Highway Performance Program—Performance of the NHS covered in Subpart E; (2) Freight Movement on the Interstate System, covered in Subpart F; and two measures relating to the CMAQ Program: (3) Traffic Congestion covered in Subpart G, and (4) On-Road Mobile Source Emissions, covered in Subpart H.
The FHWA had proposed in the prior performance management NPRMs to establish one common effective date for its three performance measure final rules. While FHWA recognizes that one common effective date could be easier for State DOTs and MPOs to implement, the process to develop and implement all of the Federal-aid highway performance measures required in MAP-21 has been lengthy. It is taking more than 3 years since the enactment of MAP-21 to issue all three performance measure NPRMs (the first performance management NPRM was published on March 11, 2014; the second NPRM was published on January 5, 2015). Rather than waiting for all three rules to be final before implementing the MAP-21 performance measure requirements, FHWA has decided to phase in the effective dates for the three final rules for these performance measures so that each of the three performance measures rules will have individual effective dates. This allows FHWA and State DOTs to begin implementing some of the performance requirements much sooner than waiting for the rulemaking process to be complete for all the rules. The FHWA believes that individual implementation dates will also help State DOTs transition to performance based planning.
On March 15, 2016, FHWA published a final rule (FR Vol. 81 No. 50) covering the safety-related elements of the Federal-aid Highway Performance Measures Rulemaking. With the staggered effective dates, this Rule will be implemented in its entirety before the other two rules are finalized.
Based on the timing of each individual rulemaking, FHWA would provide additional guidance to stakeholders on how to best integrate the new requirements into their existing processes. Under this approach, FHWA expects that even though the implementation for each rule would occur after each final rule is published, implementation for the second and the third performance measure final rules would ultimately be aligned through a common performance period. In the second performance management measure NPRM, FHWA proposed that the first 4-year performance period would start on January 1, 2016. However, FHWA proposes in this NPRM that the first performance period would begin on January 1, 2018. This would align the performance periods and reporting requirements for the proposed measures in the second and third performance management measure NPRMs. The FHWA has placed on the docket a timeline that illustrates how this transition could be implemented.
This NPRM proposes to add to Subpart A general information applicable to all of 23 CFR part 490. This section includes requirements for data, target establishment, reporting on progress, and how to determine whether State DOTs have made significant progress toward achieving targets (for applicable measures). Subpart A also includes definitions and clarifies terminology associated with target establishment, reporting, and making significant progress for the performance measures specific to this NPRM. Subparts B, C and D were previously published in separate rulemaking documents.
Subpart B covered the proposed measures for the HSIP (RIN 2125-AF49); Subpart C proposed measures to assess pavement conditions on the NHS and the non-Interstate NHS (RIN 2125-AF53); and Subpart D proposed measures to assess bridge conditions on the NHS (RIN 2125-AF53).
Subpart E proposes a travel time reliability measure and a peak hour travel time measure to assess the performance of the Interstate System and non-Interstate NHS. Subpart F establishes a travel time reliability measure and a congestion measure to assess freight movement on the Interstate System. Subpart G proposes an excessive delay measure to assess traffic congestion to carry out the CMAQ program. Subpart H proposes measures that will be used to assess the reduction of the criteria pollutants and applicable precursors to carry out the CMAQ program.
In section 490.101, FHWA proposes to add definitions for “attainment area,” “criteria pollutant,” “Highway Performance Monitoring Systems (HPMS),” “freight bottleneck,” “full extent,” “mainline highways,” “maintenance area,” “measure,” “metric,” “Metropolitan Planning Organization (MPO),” “National Ambient Air Quality Standards (NAAQS),” “National Performance Management Research Data Set (NPMRDS),” “nonattainment area,” “non-urbanized area,” “reporting segment,” “target,” “Transportation Management Area (TMA),” “Travel Time Data Set,” “Travel Time Reliability,” and “Travel Time Segment,” which would be applicable to all subparts within Part 490.
In section 490.103, FHWA proposes data requirements that apply to more than one subpart in Part 490. Additional proposed data requirements unique to each subpart are included and discussed in each respective subpart. This section proposes the source of urbanized area boundaries as the most recent U.S. Decennial Census unless FHWA approves adjustments to the urbanized area. These boundaries are to be reported to HPMS. The boundaries in place at the time of the Baseline Performance Report are to apply to an entire performance period. Boundaries for the nonattainment and maintenance areas are proposed to be as designated and reported by the U.S. Environmental Protection Agency (EPA) for any of the criteria pollutants applicable under the CMAQ program. The FHWA is proposing that State DOTs and MPOs use the NPMRDS to calculate the travel time and speed related metrics (a metric means a quantifiable indicator of performance or condition that is used to develop the measures defined in this
The NPMRDS is a dataset based on actual, observed data collected from probes, such as cell phones, navigation units, and other devices, in vehicles that travel along the NHS roadways. The dataset includes travel time information collected from probes that is available at 5 minute intervals for all segments of the Interstate and NHS where probes were present. The advent of readily available vehicle-based probe travel time data in recent years has led to a transformation in information available to the traveler and the ability for State DOTs and MPOs to develop performance measures based on this data. Because travel time data on the entire NHS is available from actual measurements tied to a date, time, and location on specific roadway segments, measuring the performance of the system, freight movement, and monitoring traffic congestion can be much more accurate, widespread, and detailed. The availability of this data also provides the potential to undertake before and after evaluations of transportation projects and strategies. These data requirements are detailed in proposed section 490.103.
The FHWA is proposing State DOTs and MPOs coordinate to develop reporting segments that would be used as the basis for calculating and reporting metrics to FHWA for the measures proposed in Subparts E, F, and G to assess the performance of the NHS, freight movement on the Interstate System, and traffic congestion. It is proposed that these reporting segments must be submitted to FHWA no later than the November 1 before the beginning of each performance period, and the same segments be used for Subparts E, F, and G for the entire performance period.
In section 490.105, FHWA proposes the minimum requirements that would be followed by State DOTs and MPOs to establish targets for all measures identified in section 490.105(c), which includes proposed measures both in this performance management NPRM and the second performance management NPRM. These requirements are being proposed to implement the 23 U.S.C. 150(d) and 23 U.S.C. 134(h)(2) target establishment provisions to provide for consistency necessary to evaluate and report progress at a State, MPO, and national level, while also providing a degree of flexibility for State DOTs and MPOs.
In section 490.107, FHWA proposes the minimum requirements that would be followed by State DOTs and MPOs in the reporting targets for all proposed measures identified in both this performance management NPRM and the second performance management NPRM.
Section 490.109 proposes the method FHWA would use to determine if State DOTs have achieved or made significant progress toward their NHPP and NHFP targets. Significant progress would be determined by comparing the established target with the measured condition/performance associated with that target. If applicable, State DOTs would have the opportunity to discuss why targets were not achieved or significant progress was not made. For the NHPP and NHFP measures, if FHWA determines that a State DOT fails to make significant progress over each of the biennial performance reporting periods, then the State DOT is required to document in their next biennial performance report, though encouraged to document sooner, the actions they will undertake to achieve their targets.
The NPRM gives details on specific measures, which are proposed to be added to four new Subparts of Part 490 that include:
Subpart E proposes two types of measures that reflect the
Subpart F proposes two measures that reflect the
Subpart G proposes a measure that reflects the amount of
Subpart H proposes a measure that reflects the
Subpart F proposes a reliability measure to reflect the consistency of travel times on the system as experienced by shippers and suppliers. In this case the measure is a comparison of the longest travel times as compared to the time normally expected for the trip to take. The measure considers travel occurring at all hours of the day since this measure is designed to represent the perception of shippers and suppliers. In addition, this proposed freight movement measure is limited to the reliability of the Interstate System. As with all vehicles, the system is considered to be unreliable when the longest trip takes 50 percent more time than what would be normally expected. “Longer” and “Longest” trip travel times are described in more detail in the discussions of Section 490.505 and 490.607.
Also in Subpart E, as a complement to the reliability measure, the NPRM proposes a measure that evaluates the travel times experienced by all traffic during peak hours of the day. In contrast to the reliability measure which focuses on travel time variability, the peak hour measure is designed to measure the travel time during certain peak hours during the day, and how that compares to the desired travel time for that roadway at that time of day. The desired travel time is defined by the State DOT and MPO. It is expected that the desired time would be based on an analysis of how the roadway operates, its design features, any policy considerations, and how it functions within the larger system. As discussed previously, reliability reflects the consistency of trip time durations (
As a complement to the truck reliability measure, in Subpart F the NPRM is proposing a measure that reflects where trucks are experiencing congestion on the Interstate System. This measure identifies the portions of the Interstate System where actual truck travel speeds throughout the year are at least 50 mph. This measure considers use of the system every day throughout the year.
The NPRM includes two proposed measures that would be needed to carry out the CMAQ program. The first is a measure proposed in Subpart G that reflects traffic congestion and the second is a measure proposed in Subpart H that reflects emission reductions through the delivery of CMAQ funded projects.
The proposed traffic congestion measure reflects the total amount of time during the year when highway users have experienced excessive delay. The measure identifies times during the day when vehicles are travelling at speeds below 35 mph for freeways/expressways or 15 mph for all other NHS roadways. The proposed measure is designed to sum the additional travel times weighted by traffic volumes that occur during these excessive delay conditions throughout the year. Additionally, the measure is proposed to be expressed as a rate calculated by dividing the total excessive delay time by the population in the area.
The proposed emission reduction measure reflects the reductions in particular pollutants resulting from the delivery of CMAQ funded projects. The measure focuses on the total emissions reduced per fiscal year, by all CMAQ-funded projects by criteria pollutant and applicable precursors in nonattainment and maintenance areas.
More specific details on each of these measures, including information on the areas where the measure is applicable, are included in both the Performance Management Measure Analysis Section (Section V) and the Section-by-Section Discussion of the General Information and Proposed Performance Measures Sections (Section VI). In addition, FHWA has developed short fact sheets for each of these measures that will be available on the docket.
On December 4, 2015, the President signed the Fixing America's Surface Transportation (FAST) Act (Pub. L.114-94; Dec. 4, 2015) into law. For the most part, the FAST Act is consistent with the performance management elements introduced by MAP-21. For convenience, this NPRM will refer to MAP-21 throughout the preamble to signify the fundamental changes MAP-21 made to States' authorities and responsibilities for overseeing the implementation of performance management.
For the purposes of this NPRM, the FAST Act made two relevant changes to the performance management requirements. The first is 23 U.S.C. 119(e)(7), which relates to the requirement for a significant progress determination for NHPP targets. The FAST Act amended this provision to remove the term “2 consecutive reports.” The FHWA has incorporated this change into this NPRM by removing the term “2 consecutive determinations,” which was proposed in section 490.107(b)(3)(ii)(G), as well as 490.109(f) of the second NPRM, published January 5, 2015, at 80 FR 326. In section 490.109(f) of the second NPRM, FHWA stated that if a State DOT does not achieve or make significant progress for its NHS performance targets for two consecutive reporting periods (4-year period), then the State DOT must document in its Biennial Report the actions it will take to achieve the targets. The FAST Act has changed this. As a result, this NPRM proposes to require State DOTs to take action when they do not make significant progress over one reporting period, which looks back over 2 years. With this change, the significant progress determination is still made every 2 years, but it looks back over a 2-year period instead of a 4-year period.
The second change the FAST Act made is the addition of 23 U.S.C. 167(j), which requires FHWA to determine if a State has made significant progress toward meeting the performance targets related to freight movement, established under section 150(d) and requires a description of the actions the State will undertake to achieve the targets if significant progress is not made. To meet the these requirements, FHWA has incorporated language throughout this NPRM proposing to require the targets established for the measures in section 490.105(c)(6) to be included in the significant progress process and identifying the actions the State DOT will undertake to achieve the targets if significant progress is not made. The FHWA has called these the NHFP targets. The NHPP and NHFP use the same process for assessing significant progress and determining if significant progress is made.
The FHWA estimated the incremental costs associated with the new requirements proposed in this regulatory action. The new requirements represent a change to the current practices of State DOTs and MPOs. The FHWA derived the costs of the new requirements by assessing the expected increase in the level of effort from labor for FHWA, State DOTs and MPOs to standardize and update data collection and reporting systems, as well as establish and report targets.
To estimate costs, FHWA multiplied the level of effort, expressed in labor hours, with a corresponding loaded wage rate
The FHWA performed three separate break-even analyses as the primary approach to quantify benefits. The FHWA focused its break-even analyses
The aforementioned benefits are quantified within the analysis, however, there are other qualitative benefits which apply to the proposed rule as a whole that result from more informed decisionmaking on congestion and emissions-reducing project, program, and policy choices. The proposed rule also would yield greater accountability because MAP-21-mandated reporting would increase visibility and transparency of transportation decisionmaking. The data reported to FHWA by the States would be available to the public and would be used to communicate a national performance story. The FHWA is developing a public Web site to share performance related information. In addition, the proposed rule would help focus the Federal-aid highway program on achieving balanced performance outcomes.
The results of the break-even analyses quantified the dollar value of the benefits that the proposed rule must generate to outweigh the cost of the proposed rule. The FHWA believes that the proposed rule would surpass these thresholds and, as a result, the benefits of the rule would outweigh the costs.
Table 1 displays the Office of Management and Budget (OMB) A-4 Accounting Statement as a summary of the cost and benefits calculated for this rule.
This section of the NPRM summarizes DOT's engagement and outreach with the public and with affected stakeholders during the NPRM development process and the viewpoints they shared with DOT during these consultations. Section III includes three sub-sections:
• Sub-section A provides a general description of the stakeholder consultation process;
• Sub-section B describes the broader public consultation process; and
• Sub-section C summarizes stakeholder viewpoints shared with DOT. This sub-section is organized sequentially around the three major measurement focus areas of this rulemaking, including: (1) system performance and traffic congestion measures, (2) freight movement measures, and (3) on-road mobile source emissions measures.
Stakeholder engagement in developing the NPRMs is required by 23 U.S.C. 150(c) to enable DOT to obtain technical information as well as information on operational and economic impacts from stakeholders and the public. State DOTs, MPOs, transit agencies, and private and non-profit constituents across the country participated in the outreach efforts. A listing of each contact or series of contacts influencing the agency's position can be found in the docket.
In accordance with 23 U.S.C. 150(c)(1), DOT consulted regularly with affected stakeholders (including State DOTs, MPOs, industry groups, advocacy organizations, etc.) to better understand the operational and economic impact of this proposed rule. In general, these consultations included:
• Conducting listening sessions and workshops to clarify stakeholder sentiment and diverse opinions on the interpretation of technical information on the potential economic and operational impacts of implementing 23 U.S.C. 150;
• Conducting listening sessions and workshops to better understand the state-of-the-practice on the economic
• Hosting webinars with targeted stakeholder audiences to ask for their viewpoints through a chat pod or conference call;
• Attending meetings with non-DOT subject matter experts, including task forces, advocacy groups, private industry, non-DOT Federal employees, academia, etc., to discuss timelines, priorities, and the most effective methods for implementing 23 U.S.C. 150; and to discuss and collect information on the issues that need to be addressed or the questions that need to be answered in the NPRMs to facilitate efficient implementation.
It is DOT's policy to provide for and encourage public participation in the rulemaking process. In addition to the public participation that was coordinated in conjunction with the stakeholder consultation discussed above, DOT provided opportunities for broader public participation. The DOT invited the public to provide technical and economic information to improve the agency's understanding of a subject and the potential impacts of rulemaking. This was done by providing an email address (
In accordance with 23 U.S.C. 150(c)(2)(A), FHWA will “provide States, metropolitan planning organizations, and other stakeholders not less than 90 days to comment on any regulation proposed by the Secretary . . .” During the notice and comment period, FHWA plans to hold public meetings to explain the provisions contained in these NPRMs, including this NPRM. All such meetings will be open to the public. However, all comments regarding the NPRM must be submitted in writing to the rulemaking docket.
This section summarizes some of the common themes identified during the stakeholder outreach. It is important to note that some of the stakeholder comments related to more than one topic. In that case, the comments were placed under the theme most directly affected. The three themes include:
• Subparts E and G: Performance Management Measures to Assess Performance of the National Highway System and for Assessing Traffic Congestion.
• Subpart F: National Performance Management Measures to Assess Freight Movement on the Interstate System, and
• Subpart H: National Performance Management Measures for the Congestion Mitigation and Air Quality Improvement Program—On-Road Mobile Source Emissions.
The FHWA separated the stakeholder comments on the performance and congestion measures into four general areas, listed below and the comments are summarized in each of those areas.
• Stakeholders' Viewpoints on Measurement Approaches
• Stakeholders' Viewpoints on Measurement Calculation Methods
• Stakeholders' Viewpoints on Measurement Principles
• Stakeholders' Viewpoints on Measurement Challenges
Stakeholders provided input to DOT on many different measure approaches for assessing either performance on the Interstate System and non-Interstate NHS for the purpose of carrying out the NHPP or assessing traffic congestion for the purpose of carrying out the CMAQ program. In general, stakeholders' suggested approaches fell within the following categories:
•
•
•
•
•
Stakeholders provided considerable input to DOT on detailed aspects of measure calculation methods. In general, stakeholders' suggestions fell within the following categories:
•
•
•
•
•
Stakeholders provided DOT with input on general principles for selecting measures. In general, stakeholders' suggestions fell within the following categories:
•
•
•
•
•
•
•
•
•
•
Stakeholders provided DOT with input on perceived measurement challenges. In general, stakeholders' suggestions fell within the following categories:
•
•
•
•
•
Freight movement is multidimensional and includes a variety of public and private stakeholders with unique perspectives. In addition to the public participation and stakeholder consultation described in Section III.A., of this NPRM, DOT held listening sessions with representatives of the freight stakeholder community from the private and public sectors. Outreach to stakeholders through these sessions provided valuable information for FHWA to consider in developing the proposed measures. The major themes collected from each session and relevant academic research are detailed below.
The FHWA held a Freight Roundtable event that brought together membership of the Freight Policy Council, a group of the executive leadership in each
The FHWA held a listening session for State-level stakeholder organizations as these organizations have followed MAP-21's development and DOT's implementation activities and will have responsibility for reporting on the measures. These State-level stakeholders have advocated transportation-related policies and developed a significant amount of transportation research and findings that have contributed to the performance measure discussions surrounding MAP-21 implementation. Their suggestions included measures such as travel time, reliability, and bottleneck identification. Specifically, participants described travel time, reliability and speed as important to understand economic efficiency. Concern was expressed regarding data collection, cost, and burden to the States. Additionally, participants noted concern about external factors that are harder to measure or consider, as well as a lack of control over measures for safety or economics, where States do not want to be evaluated because they have little control in how to influence the measure. There was some discussion on targets and thresholds, noting that measuring speed and travel time against posted speed would be challenging due to regulators on trucks that limit speed, and variations in external factors would need to be considered by States in setting targets.
In addition to the listening session, the American Association of State Highway and Transportation Officials (AASHTO) performed a comprehensive analysis of the MAP-21 provisions and wrote a letter that contained recommendations approved by their membership for the MAP-21 Performance Measure Rulemaking. Other stakeholders and individuals provided recommendations as well. These letters are all posted on the docket for review. For freight movement on the Interstate, these recommendations included the following:
• National level performance measures may not be the same performance measures State DOTs would use for planning and programming of transportation projects and funding.
• National level performance measures should be specific, measurable, attainable, realistic, timely, and simple.
• National level performance measures should focus on areas and assets where State DOTs have control.
• The initial set of national-level performance measures should build upon existing performance measures, management practices, data sets, and reporting processes.
• National level measures should be forward thinking to allow continued improvement over time.
• Messaging the impact and meaning of the national-level measures to the public and other audiences is vital to the success of this initiative.
• Flexibility in target setting to allow States to set their own thresholds and targets.
Like State-level stakeholders, MPO and regional organization freight representatives provided input in the MAP-21 outreach process for freight movement on the Interstate performance measures. In a listening session held with these representatives, key themes were consideration of hours of service for truck operators, economic efficiency, job creation measures, environmental measures, congestion, travel speed, and reliability. These stakeholders also identified information from shippers as necessary for interpreting the user perspective. Representatives supported travel time and reliability as most critical for measurement and indicated that these measures were most important for businesses in their regions.
Additional regional organization stakeholders, representing both urban and rural areas, further called for consistency in the adoption of measures that could best describe the freight system while considering differences in mode, geography, locations of freight facilities, and practices. Additional concerns were related to how to adapt freight performance measures to current measures that may not provide the correct picture of freight movement even though they are good measures for passenger transport or some other function. Finally, representatives supported measures that identified reliability and the refinement and use of data for measuring reliability on freight corridors.
The FHWA held listening sessions with stakeholders representing a subset of the freight industry, primarily trucking, whose performance would be measured as part of this rule. These stakeholders represent various parts of the flow of goods from origin to destination and depend on the freight system for on-time deliveries of goods. More specifically, these stakeholders include professional truckers such as corporate drivers, owner-operators, and retired truckers, representatives of trucking companies, shippers, and related businesses.
The main comments received from these stakeholders related to truck parking, highway average speeds, bottlenecks, safety, oversize and overweight inconsistencies, tolls, and delay. Average speed was important to stakeholders because it provided drivers and industrial planners with the information they needed to plan routes and delivery schedules. Stakeholders identified reliability as important because it provides the driver with the flexibility to plan routes and deliveries by knowing what to expect at what time. One participant noted that it is very difficult for a driver to say that average speed is more important than travel time or reliability—this depends on time of day or where the driver needs to go. The participant gave examples where he could drive in and out of a metropolitan area without issue at one time of day but have significant delays at other times. Time of day and other external factors were said to be important when measuring performance.
Some shipper and business owner comments, as well as those of their own drivers, suggested that performance measures for freight include safety, travel time, hours of service, trends of delay, speeds, and connections to other modes or access. They said time was critical because travel times are useful in planning deliveries. Further, measuring trends of delay could help identify better opportunities for route plans. These stakeholders noted that bottlenecks, speed, and travel time information were important to measure and further, identified speed as a useful measure for determining bottlenecks.
In April 2013, FHWA sought clarification from stakeholders on
Freight stakeholders provided diverse perspectives on approaches for assessing freight movement on the Interstate System including the use of measures based on accessibility, delay, speed, safety, parking availability, bottleneck identification, accident recovery, consistency in oversize/overweight vehicle practices, tolling practices, hours-of-service for truck operators, environmental impacts, and economic impacts. A common theme was the importance of speed, reliability, and travel time measures to freight system users because they can use this information to plan freight movements.
Stakeholders provided input to DOT on the following perceived measurement challenges:
•
•
•
Stakeholders provided input to DOT on detailed aspects of measure calculation methods. In general, stakeholders' suggestions fell within the following categories:
•
•
•
Stakeholders provided DOT with some general principles for selecting measures. In general, stakeholders' suggestions fell within the following categories:
•
•
•
•
•
•
•
•
Stakeholders provided DOT with input on data collection and reporting related to on-road mobile source emissions. Suggestions generally fell in the following categories:
•
•
•
•
•
•
The cornerstone of MAP-21's Federal-aid highway program transformation is the transition to a performance and outcome-based program. As part of this transformation, and for the first time, recipients of Federal-aid highway funds make transportation investments to achieve individual targets that collectively make progress toward national goals.
The MAP-21 provisions that focus on the achievement of performance outcomes are contained in a number of sections of the law that are administered by different DOT agencies. Consequently, these provisions require an implementation approach that includes a number of separate but related rulemakings, some from other modes within DOT. A summary of the rulemakings related to this proposed rule is provided in this section and additional information regarding all related implementation actions is available on the FHWA Web site.
The DOT's proposal regarding MAP-21's performance requirements will be presented through several rulemakings. As a brief summary, these rulemaking actions are listed below and should be referenced for a complete picture of performance management implementation. The summary below describes the main provisions that DOT plans to propose for each rulemaking. The DOT has sought or plans to seek comment on each of these rulemakings.
The FHWA organized the many performance-related provisions within MAP-21 into six elements as defined below:
•
•
•
• Plans—Development of strategic and/or tactical plans by recipients of Federal-aid highway funding to identify strategies and investments that will address performance needs.
•
•
The following provides a summary of MAP-21 provisions, as they relate to the six elements listed above, including a reference to other related rulemakings that should be considered for a more comprehensive view of MAP-21 performance management implementation.
The MAP-21 sec. 1203 establishes national goals to focus the Federal-aid highway program. The following national goals are codified at 23 U.S.C. 150(b):
•
•
•
•
•
•
•
These national goals will largely be supported through the metropolitan and statewide planning process, which is discussed under a separate rulemaking (RIN: 2125-AF52) to update the Metropolitan and Statewide Planning Regulations at 23 CFR part 450.
The MAP-21 requires the establishment of performance measures, in consultation with State DOTs, MPOs, and other stakeholders, that would do the following:
• Carry out the NHPP and assess the condition of pavements on the Interstate System and the NHS (excluding the Interstate System), the condition of bridges on the NHS, and performance of the Interstate System and NHS (excluding the Interstate System);
• Carry out the HSIP and assess serious injuries and fatalities per VMT and the number of serious injuries and fatalities;
• Carry out the CMAQ program and assess traffic congestion and on-road mobile source emissions; and
• Assess freight movement on the Interstate System.
The MAP-21 also requires the Secretary to establish the data elements necessary to collect and maintain standardized data to carry out a performance-based approach.
The FHWA proposed to issue three rulemakings in sequence to implement the measures for the areas listed above. The first rulemaking, issued as a NPRM on March 11, 2014 and published as a final rule on March 15, 2016, focused on the performance measures, for the purpose of carrying out the HSIP, to assess the number of serious injuries and fatalities and serious injuries and fatalities per VMT. The second NPRM focused on the measures to assess the condition of pavements and bridges, and this third NPRM proposes measures for the remaining areas under 23 U.S.C. 150(c).
The FHWA had proposed in the prior performance management NPRMs to establish one common effective date for its three performance measure final rules. While FHWA recognizes that one common effective date could be easier for State DOTs and MPOs to implement, the process to develop and implement all of the Federal-aid highway performance measures required in MAP-21 has been lengthy. It is taking more than 3 years since the enactment of MAP-21 to issue all three performance measure NPRMs (the first performance management NPRM was published on March 11, 2014; the second NPRM was published on January 5, 2015). Rather than waiting for all three rules to be final before implementing the MAP-21 performance measure requirements, FHWA has decided to phase in the effective dates for the three final rules for these performance measures so that each of the three performance measures rules will have individual effective dates. This allows FHWA and State DOTs to begin implementing some of the performance requirements much sooner than waiting for the rulemaking process to be complete for all the rules. The FHWA believes that individual implementation dates will also help State DOTs transition to performance based planning.
On March 15, 2016, FHWA published a final rule (FR Vol. 81 No. 50) covering the safety-related elements of the Federal-aid Highway Performance Measures Rulemaking. With the staggered effective dates, the Rule will be implemented in its entirety before the other two rules are finalized.
Based on the timing of each individual rulemaking, FHWA would provide additional guidance to stakeholders on how to best integrate the new requirements into their existing processes. Under this approach, FHWA expects that even though the implementation for each rule would occur as each final rule is published, implementation for the second rule would ultimately be aligned with the third rule through a common
The MAP-21 also requires FHWA to establish minimum levels for the condition of pavements for the Interstate System necessary to carry out the NHPP, which was proposed in the second rulemaking.
Separate sections of MAP-21 require the establishment of additional measures to assess public transportation performance.
In regard to the Federal Lands Transportation Program, FHWA anticipates working with eligible Federal entities to establish performance measures.
The MAP-21 requires State DOTs to establish performance targets reflecting measures established for the Federal-aid highway program
Further, MAP-21 requires State Highway Safety Offices to establish targets for 11 core highway safety program outcome measures in the State HSP, which NHTSA has implemented through an Interim Final Rule,
A number of provisions within MAP-21 require States and MPOs to develop plans that provide strategic direction for addressing performance needs. For the Federal-aid highway program these provisions require: State DOTs to develop an Asset Management Plan;
The MAP-21 sec. 1203 requires State DOTs to submit biennial reports to FHWA on the condition and performance of the NHS, the effectiveness of the investment strategy documented in a State DOT's asset management plan for the NHS, progress in achieving targets, and ways in which a State DOT is addressing congestion at freight bottlenecks.
Additional progress reporting is required under the CMAQ program, Metropolitan transportation planning, elements of the Public Transportation Act of 2012, and the Motor Vehicle and Highway Safety Improvement Act of 2012. Also, State DOTs should include a system performance report in their statewide transportation plan. These reporting provisions are discussed in separate rulemakings and guidance and are not discussed in this rulemaking, with the exception of some reporting required by MPOs as part of the CMAQ program.
Two provisions within MAP-21, specifically 23 U.S.C. 119(e)(7) under the NHPP and 23 U.S.C. 148(i) under the HSIP, and one provision within FAST Act (Section 1116 codified at 23 U.S.C. 167(j)) under NHFP require the State DOT to undertake actions if significant progress is not made toward the achievement of State DOT targets established for these respective programs. The FAST Act Section 1406 modified the NHPP significant progress language and added language for the NHFP. Accordingly, for NHPP and NHFP, if the State DOT has not achieved or made significant progress toward the achievement of applicable targets in a single FHWA biennial determination, then the State DOT must document in its next biennial report the actions it will take to achieve the targets.
Please note that FHWA proposes in section 490.109(e) that FHWA would consider a State DOT has made significant progress toward the achievement of an NHPP or NHFP target when either: (1) The actual condition/performance level is equal to or better than the State DOT established target; (2) or the actual condition/performance is better than the State DOT identified baseline of condition/performance. So the term “achieved or made significant progress” is synonymous with the term “made significant progress” throughout this NPRM. This provision is discussed in the second performance measure NPRM and in this NPRM.
For the HSIP, if the State DOT does not achieve or make significant progress for its HSIP safety targets, then the State DOT must dedicate a specified amount of obligation limitation to safety projects and prepare an annual implementation plan.
In addition, MAP-21 requires that each State DOT maintain a minimum condition level for Interstate System pavement and NHS bridge conditions. If a State DOT falls below either standard, then the State DOT must spend a specified portion of its funds for that purpose until the minimum standard is exceeded.
The FHWA recognizes that there is a limit to the direct impact that State DOTs can have on performance outcomes within the State and that State DOTs need to consider this uncertainty in their establishment of targets. The FHWA encourages State DOTs to consult with relevant entities (
Further, MAP-21 includes special safety rules to require each State DOT to maintain or improve safety performance on high risk rural roads and for older drivers and pedestrians.
The FHWA will implement the performance requirements within section 1203 of MAP-21 in a manner that results in a transformation of the Federal-aid highway program so that the program focuses on national goals, provides for a greater level of accountability and transparency, and provides a means for the most efficient investment of Federal transportation funds. In this regard, FHWA plans to implement these new requirements in a manner that will provide Federal-aid highway fund recipients the greatest opportunity to fully embrace a performance-based approach to transportation investment decisionmaking that does not hinder performance improvement. In this regard, FHWA carefully considered the following principles in the development of proposed regulations for national performance measures under 23 U.S.C. 150(c):
• Provide for a National Focus—focus the performance requirements on outcomes that can be reported at a national level.
• Minimize the Number of Measures—identify only the most necessary measures that will be required for target establishment and progress reporting. Limit the number of measures to one or no more than two per area specified under 23 U.S.C. 150(c).
• Ensure for Consistency—provide a sufficient level of consistency, nationally, in the establishment of measures, the process to establish targets and report expectations, and the approach to assess progress so that transportation performance can be presented in a credible manner at the national level.
• Phase in Requirements—allow for sufficient time to comply with new requirements and consider approaches to phase in new approaches to measuring, target establishment, and reporting performance.
• Increase Accountability and Transparency—consider an approach that would provide the public and decisionmakers a better understanding of Federal transportation investment returns and needs.
• Consider Risk—recognize that risks in the target establishment process are inherent and that many factors, outside the control of the entity required to establish the targets, can impact performance.
• Understand that Priorities Differ—recognize that targets need to be established across a wide range of performance areas and that performance trade-offs would need to be made to establish priorities, which would be influenced by local and regional needs.
• Recognize Fiscal Constraints—provide for an approach that encourages the optimal investment of Federal funds to maximize performance but recognize that, when operating with scarce resources, performance cannot always be improved.
• Provide for Flexibility—recognize that the MAP-21 requirements are the first steps that will transform the Federal-aid highway program to a performance-based program and that State DOTs, MPOs, and other stakeholders will be learning a great deal as implementation occurs.
The FHWA considered these principles in this and previous NPRMs and encourages comments on the extent to which the approach to performance measures set forth in this NPRM supports the principles discussed above.
The FHWA is committed to providing stewardship to State DOTs and MPOs assisting them as they take steps to
This section of the NPRM summarizes the process FHWA used to consider potential performance measures, including alternate data sources and potential measures. The FHWA's analysis was based on consideration of viewpoints from several sources including:
• Knowledge of technical experts within DOT and FHWA on the current state of practice for measuring system performance, freight movement, traffic congestion, and on-road mobile source emissions;
• Information provided by external stakeholders received directly or captured as part of organized stakeholder listening sessions;
• Information provided by external stakeholders received indirectly through informal contact such as telephone calls, email, or letters; and
• Measures that have been recommended and documented in nationally recognized reports such as the assessment of measurement readiness documented in the 2011 final report for NCHRP Project 20-24(37)G, “Technical Guidance for Deploying National Level Performance Measurements.”
Compared with the two previous NPRMs in this series, the measurement areas covered by this NPRM are more varied from State to State; consequently, stakeholders' consensus about approaches for measuring performance is inconsistent. To aid its analysis of alternate measurement options for this NPRM specifically, FHWA relied on an expanded set of qualitative criteria (which supplement the assessment factors/criteria utilized in the other performance measure NPRMs) to ensure that a set of measures established through this rulemaking would allow for:
• A national performance story to be communicated in a credible and reliable manner;
• State DOTs and MPOs to consider their unique expectations of desirable performance;
• The potential for use across multiple surface transportation modes;
• One core set of data to be used to assess system performance, traffic congestion, and freight movement; and
• The potential utilization of new data as technology progresses.
Section V includes three sub-sections, which describe FHWA's assessment of measures using the expanded set of criteria as well as the assessment factors and criteria used in the two previous performance measure NPRMs:
• Sub-Section A—Analysis and assessment of potential data sources, measurement methodologies, and proposed measures for measuring system performance and traffic congestion;
• Sub-Section B—Analysis and assessment of potential data sources, measurement methodologies, and proposed measures for measuring freight movement, and
• Sub-Section C—Analysis and assessment of potential data sources, measurement methodologies, and proposed measures for measuring on-road mobile source emissions.
Also, each sub-section below describes FHWA's evaluation of the measures using a common methodology to identify gaps that could impact successful implementation of proposed performance measures.
This sub-section describes FHWA's analysis of data types, sources, and measurement methods to support potential measures. We also include a brief history of, and lessons learned from, FHWA's research on congestion and reliability performance measures. Lastly, this sub-section describes FHWA's assessment of proposed measures including: (1) Percentage of system providing for reliable travel times; (2) percentage of system providing where peak hour travel times meet expectations; and (3) annual excessive delay per capita.
The FHWA considered several potential data sources for use in measuring system performance and traffic congestion including travel speed and time data, travel volume data, vehicle throughput data, and other trip information on data.
To measure throughput on the NHS would require near constant vehicle count/volume data that does not exist today except for a very limited number of locations (usually those locations where HPMS requires reporting of volume). Person count data, which would be used for measuring person throughput, is typically based on vehicle occupancy which is typically reported as an average based on surveys (including the U.S. Census) or as a set multiplier to vehicles (
The FHWA concludes that an almost complete lack of data availability makes throughput data impractical as a measure of performance. The FHWA recognizes, however, that improvements in traffic data collection technologies could offer the potential to measure throughput on a system-wide basis in the future.
A summary of FHWA's analysis of the viability of various data types to support national measures to assess system performance and traffic congestion is provided in Table 3 below:
Based on the discussion in this section, FHWA considered use of travel time, speed, or traffic volume data to support measures for system performance and traffic congestion.
Request for comments: FHWA recognizes limitations in the availability of data could be resolved in the future with technology advancement. The FHWA seeks comments on potential data sources and technologies related to system performance and traffic congestion measures, including:
1.
2.
3.
The FHWA identified and considered a variety of approaches to express travel time, speed, or traffic volume data as measures of system performance or traffic congestion including travel delay, a travel time index, travel time, travel time reliability, or Level of Service. A summary of how these suggestions and approaches were considered by FHWA is provided below:
A summary of FHWA's analysis of the different approaches for expressing travel time, travel speed, and/or traffic volume considered as part of its efforts to develop measures to assess system performance and traffic congestion is provided in Table 4 below.
The FHWA has been researching performance measures for congestion, mobility, and reliability for over 10 years. The Urban Congestion Report
Two issues identified through this research are important to understanding the ultimate approach FHWA proposes for the MAP-21 performance measures related to congestion and system reliability. First, the advent of readily available vehicle-based probe travel time data in recent years has led to a transformation of traveler information and performance measure development. Vehicle-based probe travel time data is derived from in-vehicle, GPS-based probes, including track fleet management devices, navigation units, and cell phones that report location information and time. The travel times are either derived directly from speed data provided or calculated based on a probe's trip progress (deriving speeds from the amount of time taken to travel between two locations and the distance between the two locations). Because data on the entire NHS is available from actual measurements tied to a date, time, and location on specific roadway segments, congestion performance measurement can be much more accurate, widespread, and detailed. This data also provides the potential to undertake before/after evaluations of transportation projects and strategies.
Since the passage of MAP-21, the FHWA acquired vehicle-based probe travel time data from a private vendor
The second issue FHWA identified is that aggregating measures up to a national level provides important national trend information but has limited direct correlation to how money is being spent on road improvements that may actually affect changes in the measure. The FHWA has been advocating the use of performance measures at a local level as best practice in recent years. Operating and planning agencies can better understand how a project affects performance on a section of roadway or how a facility or corridor operates during peak periods or weather events using local performance measures, rather than aggregating measure up to a regional, State, or national level.
The FHWA analysis of measures included applicability of measures to the transportation network or geographic area. Section 1203 of MAP-21 directed FHWA to establish measures for States to use to assess the performance of the Interstate System and the non-Interstate NHS. For assessing performance of the non-Interstate NHS, FHWA believes it is important that at least one of the selected measures relate to the entire NHS. Since system reliability is identified as one of the National Goals (23 U.S.C. 150(b)(4)), FHWA decided it was appropriate to establish a reliability-based measure for the entire NHS. Accordingly, the NHPP Performance of the System reliability measure is calculated for the entire NHS.
Another important component of System Performance is congestion, and typically, but not exclusively, the worst congestion occurs on high-volume roads in urbanized areas. The FHWA thought it was important to capture this type of congestion in a measure so that urbanized areas would be able to monitor and address congestion issues. The Peak Hour Travel Time measure was developed to provide this information, limiting the reporting to the largest urbanized areas (over 1,000,000 in population). In selecting this measure, FHWA considered the national goal of congestion reduction, which asks to achieve a significant reduction in congestion on the NHS. 23 U.S.C. 150(b)(3). The FHWA believes the Peak Hour Travel Time measure is consistent with this national goal. The Peak Hour Travel Time measure also gives agencies in the affected urbanized areas the ability to relate their measure to their NHS roadway operational and investment policies by allowing them to set the “Desired Peak Period Travel Time” on their NHS roadways.
Consistent with the purpose of the CMAQ program to fund transportation projects and programs that will contribute to attainment or maintenance of the NAAQS in areas designated as nonattainment and maintenance, FHWA believes that the CMAQ Traffic Congestion measure should apply to nonattainment and maintenance areas and relate to the goals of the CMAQ Program (to improve air quality and relieve congestion). To reduce the burden on some States DOTs and MPOs and to focus on areas where typically the worst congestion occurs, like the System Performance congestion measure, FHWA chose to limit this measure to urbanized areas over 1,000,000 in population as well, since those agencies typically have more capability and experience in assessing traffic congestion. In addition, these areas are the same areas where MPOs will need to report on the CMAQ measures as part of a performance plan under 23 U.S.C. 149(l). Similar to the System Performance congestion measure, FHWA also chose a measure that would be consistent with the national goal of congestion reduction.
Based on a thorough review of data, measure definitions, calculation methods, applicability, and national goals, FHWA identified three potential measures to assess system performance and traffic congestion that deserved further consideration including: Percentage of system providing for reliable travel times; percentage of system where peak hour travel times meet expectations; and annual excessive delay per capita.
The FHWA analyzed these proposed measures for system performance and traffic congestion in tandem as part of this rulemaking so they would provide (1) a complete national picture of system reliability; (2) a focus on urbanized area peak hour congestion; and (3) a focus on the worst traffic delays in air quality nonattainment areas and maintenance areas. In addition, FHWA ensured that the proposed measures (and related metrics) were defined so that their methodologies could be applicable at the same segment, corridor, facility, or other level, resulting in fine grain performance information suitable for supporting the investment decisionmaking process at the statewide, metropolitan, and local levels. Finally, FHWA focused on using as much actual, observed data as is available to develop these measures. Together, these three measures provide a comprehensive picture of system performance, reliability and traffic congestion nationwide, both on the entire NHS and with a focus on areas that typically have the worst congestion.
The FHWA used a common methodology of 12 criteria to assess the appropriateness of each measure for national use and the readiness to implement the performance measure accurately and reliably.
Each performance measure, as used in current practice, was assessed against the 12 criteria using the following three ratings for each criterion.
The FHWA used the results of this assessment to identify gaps that FHWA could address through this rulemaking to improve the effectiveness of the measures in this NPRM. The rulemaking docket contains a description of the methodology used for this assessment. Table 5 below summarizes the results of the assessment for the proposed performance management measures for system performance and traffic congestion.
The factors that were assessed at a green level for the proposed measures were considered by FHWA in its choice of approach for system performance and traffic congestion measures. The FHWA also considered the factor assessed at yellow (B3—completeness) for all three measures as probe data is available on most of the NHS, but there are still some times of day and locations where data is not consistently available via the NPMRDS data set that FHWA is requiring for use for these measures. The FHWA believes that over time, as more probe data sources are added to the data set, that missing travel times will be minimized.
The FHWA proposal outlined in this NPRM attempts to address some of the gaps that exist today for the lower rated factors so that, when the new requirements are implemented, the measures result in an improved assessment rating, thereby better supporting national programs. In particular, FHWA factored the following considerations in its decision:
• Criterion A1—recognize that the Traffic Congestion measure (Annual Hours of Excessive Delay Per Capita) should ideally reflect the movement of all travelers and the performance of all modes. As proposed, the measure may not capture modal options or better accessibility. The FHWA is seeking comment on methods that can be used reliably to achieve this outcome.
• Criterion A2—recognize that a national measure is not in place for either system performance or traffic congestion and no national pilot studies have been conducted. However, FHWA and many State DOTs and MPOs have developed their own system performance/congestion measures and these were considered in developing the national measures.
This sub-section describes the FHWA's analysis of a range of data types and sources and measurement methods to support potential freight movement-related measures and describes FHWA's assessment of two proposed measures including: (1) Percent of Interstate System mileage meeting the goal for reliability; and (2) percent of Interstate System mileage considered uncongested (by speed). The FHWA assessed both these proposed measures in terms of appropriateness as national measures and readiness for implementation.
The FHWA selected reliability and average speed measures because they offered the best understanding of freight performance at the national level and had the widest support from stakeholders. The FHWA seeks to refine the use of freight-related measures in the future and broaden measures and data sources that can better inform future policy, programming, and investment decisions and provide a multimodal consideration of freight flow.
The FHWA recognizes that the efficient movement of freight is important to the Nation's economy. Efficiency is hindered by slow speeds and unreliable travel times caused by congested highways. For the freight industry, slow and unreliable travel results in diminished productivity by reducing the efficiency of operations, increasing costs of goods, increasing fuel costs, reducing drivers' available hours for service, and reducing equipment productivity. Reducing highway congestion could produce important benefits for the freight industry and contribute to our Nation's growing economy. Solutions must address the long-term and short-term freight needs and depend on participation from both the public and private sectors to fully understand performance and develop strategic solutions.
Historically, congestion data collection efforts focused exclusively on commuting in urbanized areas. To improve availability of freight data, FHWA launched the FPM program in 2002. This program collects truck travel-time data on major freight-significant corridors, intercity pairs along those corridors, and major U.S. international land-border crossings. Data are collected from embedded probe technology in approximately 600,000 trucks and are used to provide a range of performance measures including but not limited to travel times, speeds, congestion points, incident analysis, and diversions. Although FPM itself is not a system improvement, it is a mechanism for collecting and analyzing data to assist national, State, regional, and local transportation agencies in better measuring and managing highway transportation system performance. The availability of FPM data has the potential to inform future investment decisions that produce benefits of regional and national significance.
The FPM program complements other efforts by FHWA to monitor and measure urban congestion. Combining FPM data with urban congestion data such as HPMS data, economic data from the Freight Analysis Framework, and other relevant data provides a more complete picture of surface transportation system performance and identifies areas where performance could be improved. To provide a comprehensive understanding of freight performance in concert with passenger and total traffic congestion and performance, FHWA procured the NPMRDS in 2013, which provides travel times for all traffic, passenger, and freight with an archive of data beginning in October 2011. The FPM probe data is the freight data that is included in the NPMRDS travel time data. States and MPOs are currently using this data set to develop performance measures and support freight planning and other transportation plans. This data set allows a more comprehensive understanding of congestion for all types of traffic through the calculation of speed, reliability, and travel time on corridors with significant freight movement. As mentioned above, there is widespread support among stakeholders for these types of measures (
The FHWA focused its evaluation of measures for 23 U.S.C. 150 for freight movement on Interstate on its significant research and leadership in FPM development through the FPM program, and stakeholder input. The FHWA recognizes that freight performance is best depicted by a series of measures to provide a comprehensive picture of freight movement. Stakeholders discussed multimodal measures and suites of measures to show performance in all aspects of freight movement. As the measures required for this rulemaking are only for freight movement on the Interstate System, FHWA is addressing stakeholder requests for multimodal and multiarea measures through other MAP-21 freight requirements such as freight planning and the development of a Freight Conditions and Performance Report (see MAP-21, Section 1115). An additional factor in FHWA's assessment was the varying practices for FPM among stakeholders, including State DOTs and MPOs, resulting in a lack of national consistency on data and measurement. After considering the ongoing research in this area and stakeholder support for FHWA's FPM efforts, FHWA believes that its proposed use of a nationally consistent data set is the most consistent, efficient, and reliable means of understanding Interstate freight movement at the local, State, and national levels.
The FHWA identified two proposed measures: (1) Percent of Interstate System mileage meeting the goal for reliability; and (2) percent of Interstate System mileage considered uncongested (by speed). The two measures proposed by FHWA were evaluated, based on existing state-of-practice, using the assessment process described in Section V.A of this section. Table 6 includes a summary of this assessment.
The measures proposed by FHWA were considered against the criteria presented in Table 6. For all of the assessment factors except completeness, FHWA ranked these measures as “green.” The FHWA considered the measures against all of the criteria and weighed public and private stakeholder input along with FHWA's experience in applying the measures. These measures were determined to be the two measures that most appropriately met all of the assessment factors and provide a comprehensive assessment of performance for freight so that public and private decisionmakers can identify policy and operational improvements for goods movement. The FHWA considered the measures to be “yellow” for completeness only because they are proposed to rely on data from the NPMRDS, which has limited missing data that could impact the ability to conduct a complete assessment of
The following section includes an overview of the factors FHWA considered in the selection of a proposed measure for the assessment of on-road mobile source emissions as required to administer the CMAQ program under 23 U.S.C. 149. (The previous section discusses proposed measures for Traffic Congestion to carry out the CMAQ program.) The FHWA wants the measure established through this rulemaking to:
• Meet CMAQ program performance requirements in 23 U.S.C. 149 and 150.
• Be mindful of existing emissions reduction reporting practices and data sets, thereby minimizing any additional burden on State DOTs and MPOs.
• Apply to CMAQ-funded projects instead of focusing on one project type (
• Apply to CMAQ-funded projects only in areas designated as nonattainment and maintenance for pollutants applicable to the CMAQ program (ozone (O
The FHWA received viewpoints on suggested measures as discussed above in Section III, Discussion of Stakeholder Engagement and Outreach. In addition, FHWA considered measures in use today to report on-road mobile source emissions reduction estimates. After consideration, FHWA identified four possible measures for preliminary consideration:
The FHWA assessed the four potential on-road mobile source emission measures based on state-of-practice among States and MPOs and using the 12 criteria described in Section V.A. Table 7 below summarizes the results of this assessment.
Based on the assessment summarized above and the additional principles described in this section, FHWA concluded that the last three measures were not suitable because they did not provide useful information for establishing targets, were not developed with key stakeholders, or in the case of cost effectiveness, data was not readily available. The measure that best fits the criteria established by FHWA was emissions reduction by pollutant. With respect to this measure, FHWA considered the following:
• Criterion B1—Measure recognizes that emissions are estimated, not measured, based on the expected benefit from building the project. Collecting emissions data on a project-by-project basis through vehicle probing or another means would be cost prohibitive and would take years to collect useable data.
• Criteria B2 and B3—Measure recognizes that no consistent method is being used across the country to estimate CMAQ project emission reductions and that although quantitative emissions analyses of air quality impacts is expected for almost all project types, qualitative assessments are acceptable when it is not possible to accurately quantify emissions reductions (
• Criterion B6—While the CMAQ Public Access System does include estimated emissions reductions by pollutant by project for each MPO and State that receives CMAQ funds, this database is not integrated with performance-related data such as a spatial component. Work is underway to improve and increase the functionalities of the database to support the performance planning activities.
The FHWA is proposing this approach to define the on-road mobile source emissions measure in a manner that is consistent with and reflects the various methods used today by State DOTs and MPOs to calculate on-road mobile source emissions and is consistent with the information received from stakeholders. The specifics of this proposal are described in the Section-by-Section portion of this proposed rule.
The FHWA is seeking comment on whether and how to establish a CO
According to the Intergovernmental Panel on Climate Change (IPCC), human activity is changing the earth's climate by causing the buildup of heat-trapping greenhouse gas emissions through the burning of fossil fuels and other human processes.
A well-established scientific record has linked increasing GHG concentrations with a range of climatic effects, including increased global temperatures that have the potential to result in dangerous and potentially irreversible changes in climate and weather. In December 2015, the Conference of Parties nations recognized the need for deep reductions in global emissions to hold the increase in global average temperature to well below 2 °C above pre-industrial levels, and are pursuing efforts to limit temperature increases to 1.5 °C. To that end, the accord calls on developed countries to take a leadership role in identifying economy-wide absolute emissions reduction targets and implementing mitigation programs. Also, as part of a 2014 bilateral agreement with China, the U.S. pledged to reduce GHG emissions to 26-28 percent below 2005 levels by 2025, with this emissions reduction pathway intended to support economy-wide reductions of 80 percent or more by 2050.
The FHWA recognizes that achieving U.S. climate goals will likely require significant GHG reductions from on-road transportation sources. To support the consideration of GHG emissions in transportation planning and decisionmaking, FHWA has developed a variety of resources to quantify on-road GHG emissions, evaluate GHG reduction strategies, and integrate climate analysis into the transportation planning process. The FHWA already encourages transportation agencies to consider GHG emissions as part of their performance-based decisionmaking, and has developed a handbook to assist State DOTs and MPOs interested in addressing GHG emissions through performance-based planning and programming.
The FHWA is considering how GHG emissions could be estimated and used to inform planning and programming decisions to reduce long term emissions. If FHWA were to establish a measure, we believe that, in the context of this rulemaking, GHG emissions would be best measured as the total annual tons of CO
• Should the measure address all on-road mobile sources or should it focus only on a particular vehicle type (
• Should the measure be normalized by changes in population, economic activity, or other factors (
• Should the measure be limited to emissions coming from the tailpipe, or should it consider emissions generated upstream in the life cycle of the vehicle operations (
• Should the measure include non-road sources, such as construction and maintenance activities associated with Title 23 projects?
• Should CO
• Due to the nature of CO
• Would a performance measure on CO
• The target establishment framework proposed in this rulemaking requires that States and MPOs would establish 2 and 4 year targets that lead to longer term performance expectations documented in longer range plans. Is this framework appropriate for a CO
• Should short term targets be a reflection of improvements from a baseline (
• What data sources and tools are readily available or are needed to track and report CO
• What tools are needed to help transportation agencies project future emissions and establish targets for a CO
• How long would it take for transportation agencies to implement such a measure?
• Additionally, the FHWA requests data about the potential agency implementation costs and public benefits associated with establishing a CO
This section discusses how the proposed regulations address MAP-21's charge to establish performance measures for State DOTs and MPOs to use to assess: The performance of the Interstate System and non-Interstate NHS for the purpose of carrying out the NHPP; freight movement on the Interstate System; and traffic congestion and on-road mobile source emissions for the purpose of carrying out the CMAQ program. Subpart A discusses common aspects of the proposed rulemaking related to definitions, reporting, significant progress determination, and target establishment. Discussion of the performance measures is organized into four subparts covering three performance areas, including: Subpart E, which discusses proposed measures to assess performance of the NHS; Subpart F, which discusses the proposed measure to assess freight movement on the Interstate System; and Subparts G and H, which discuss the proposed CMAQ measures to assess traffic congestion and on-road mobile source emissions, respectively.
Subparts E, F, G, and H of the proposed regulations provide the requirements for the system performance, traffic congestion, freight movement, and on-road mobile source emissions measures, including any required methodologies for data collection, data requirements, and processes for calculating the measures. The Section-by-Section discussion also addresses procedural discrepancies in data collection and reporting, and attempts to align them using the latest research and state-of-the-practice experience to provide consistent national performance measures.
The FHWA established and followed certain standards in the development of the requirements proposed in Subparts E, F, and G. For example, for the proposed rules associated with assessing the performance of the NHS, freight movement on the Interstate, and traffic congestion, FHWA attempted to use a consistent framework and structure, to the extent possible, because the performance measures associated with these subparts are largely based on vehicle travel times and speeds. The following sub-sections summarize the overarching framework and guiding principles used across these subparts. Information related to the development of the requirements proposed in Subpart H is discussed separately.
Transportation performance outcomes can be impacted through the use of a wide range of strategies that support the transportation priorities and policies of local areas. In its decisionmaking to develop proposed measures, FHWA was careful to avoid any measures that would impact the ability of a State DOT or MPO to make decisions that work for the local area. For this reason, FHWA focused only on measures that track transportation performance where outcomes could tell a national story.
The proposed measures in Subparts E, F, and G of this rulemaking focus primarily on the consistency and efficiency of travel times on our Nation's highways. Improvements to this outcome could be the result of a wide range of strategies such as those that would improve the operations of highway facilities and those that would decrease the demand on highway facilities by providing alternative transportation choices. The FHWA believes that the selection of these strategies is a local decision and should not be influenced directly by the measure itself. For this reason, FHWA elected not to propose measures that would directly measure the implementation of strategies to improve system operations (
This rulemaking's proposals for subparts E, F, and G (performance of the NHS, freight movement on the Interstate, and traffic congestion-related measures) are based on travel times or travel speeds of highway users. Travel times and speeds are being proposed as the basis for these measures as FHWA feels that this information accurately reflects highway operational performance and that the data can be captured across the full NHS in an accessible national data source in a timely and reliable manner. The FHWA is proposing the use of the new NPMRDS as the data source to calculate the metrics for the seven travel time/speed based measures to ensure consistency and coverage at a national level. This data set provides travel times representative of all traffic (freight and passenger vehicles) traveling on the NHS and captures this information every 5 minutes throughout every day of the year. The FHWA expects to continue to provide this data set to State DOTs and MPOs as long as there is a need at a national level for this information. The proposed regulations allow State DOTs to use alternative data sources provided the data set is considered at least equivalent in quality, coverage, and timeliness to the NPMRDS and is approved by FHWA. States DOTs and MPOs have the option to relate the travel time data provided in the NPMRDS to their relevant location referencing system (typically used for transportation planning).
As proposed in section 490.103, States and MPOs shall cooperatively develop and share information related to transportation systems performance data. The transportation systems performance data would include the travel time data set, the selected reporting segments, and the desired peak period travel time required for use under subparts E, F, and G.
When the State DOT selects the travel time data set, it must coordinate with the MPOs in the State that are subject to creating the metrics and measures in subparts E, F, and G. When the State selects the reporting segments and the Desired Peak Period Travel Time for a particular reporting segment, State DOTs must coordinate with the applicable MPOs that contain the reporting segment within their metropolitan planning area boundary. States and MPOs must use the same data (the travel time data set, the reporting segments, and the desired peak period travel time for a reporting segment) for the purposes of calculating the metrics and measures.
Travel times and speeds of highway users may be captured from a variety of sources such as mobile phones, vehicle transponders, portable navigation devices, roadway sensors, and cameras. It is possible that during the day, during specific 5-minute intervals, travel time or speed data cannot be captured. Five-minute bins without data would not be reported in the NPMRDS, and would therefore be considered missing. This can occur due to one of the following reasons:
• Reason 1—No users traveled on the roadway during the 5-minute interval, or
• Reason 2—Travel occurred on the roadway but no sources of data were recognized (
• Reason 3—Equipment failure (
The FHWA believes that, although missing data is possible due to Reason 2 listed above, the likelihood of this condition occurring will decrease over time as data capture technologies advance and as a greater percentage of highway users carry equipment that allows them to become viable travel time data sources. The FHWA also believes that it is valid to assume that travel occurring under the conditions that would result in missing data for Reason 1 would be consistent with free flow travel speeds. Lastly, for Reason 3, FHWA realizes that there are times when equipment used to capture data may fail because of usage, damage, or other causes. The FHWA believes this will be a more infrequent cause of missing information than Reason 1. For these reasons, FHWA is proposing in this rulemaking that missing travel time data be assumed to be occurring due to Reason 1 for purposes of the reliability measures (both freight and system performance) on the Interstate and, consequently, assumes travel times that are consistent with posted speed limits when data is missing.
The FHWA found, after analysis of missing data in the NPMRDS (a white-paper on missing data/outliers' impact on proposed measures is included in the docket), that there was currently sufficient data for the Interstate so States and MPOs could establish reasonable targets. However, the analysis also demonstrated that at the current time there is enough missing data for the non-Interstate NHS that it could impact the ability of States and MPOs to establish targets. Accordingly, FHWA is proposing that the non-Interstate reliability measures would be phased in, giving the States and MPOs an opportunity to understand the impact of missing data on target establishment and time for the NPMRDS to become more complete.
Regarding the peak hour travel time measures, which include both the Interstate and non-Interstate NHS, the measures rely on hourly average travel times. Missing data does not have the same impact on target establishment for the peak hour travel time measures as it does for the reliability measures. So, FHWA proposes no replacement of missing data for either of the peak hour measures. However, in its analysis of the data, FHWA noted that outliers could have an effect on these measures, so FHWA is proposing that States and MPOs remove extreme outliers (
Missing data potentially could have an impact on target establishment for the traffic congestion measure (Annual Hours of Excessive Delay Per Capita). Because this is a delay measure that sums all the delay identified on segments, missing data could mean missing some delay in calculating the measure. This could make it difficult for States and MPOs to achieve targets due to more complete data may be available in the future. The FHWA is proposing that this measure would be phased in, to allow States and MPOs time to understand the impact of missing data on establishing targets, and for the NPMRDS to become more complete.
As mentioned, a white-paper on missing data/outliers' impact on proposed measures is included in the docket. This paper includes information on options such as applying a path-type processing that uses the actual observations of the vehicles on segments adjacent to those segments with missing data and that traversed the segment with missing data to fill in the missing travel times, and the impacts of trimming the data at 2 and 100 mph. The FHWA is seeking comment on this process and other processes that FHWA should consider to improve missing data and outlier impacts.
The FHWA is proposing a phased-in approach to the establishment of targets for both the non-Interstate NHS reliability measure and the traffic congestion (excessive delay) measure. The phased-in approach would provide 2 years for data coverage on non-Interstate NHS roadways to be more complete and for States and MPOs to understand the impacts of missing data on establishing targets. The completeness of travel time data in the NPMRDS is greater for the Interstate as compared to other NHS roadways. The FHWA believes that the completeness of data in the NPMRDS will improve over time as sources become more prevalent (missing data is discussed in a white paper provided on the docket). The FHWA also believes that State DOTs have more experience in collecting and reporting reliability and congestion performance on the Interstate as compared to other NHS roadways and, as a result, are more readily capable to establish targets for the Interstate System. However, missing data for the non-Interstate NHS may lead to uncertainty for State DOTs and MPOs as they establish targets. Giving time to State DOTs and MPOs to establish targets for the non-Interstate NHS may help them learn how to manage that uncertainty. For these reasons, FHWA believes that a phased approach to target establishment is appropriate for those measures that are derived from data on the non-Interstate NHS.
The FHWA heard consistently from stakeholders that managing the travel time reliability of the highway network is important and should be considered as part of this rulemaking. For this reason, as part of this rulemaking FHWA is proposing the establishment of travel time reliability measures. In general, the proposed reliability measures address: (1) The reliability of the entire NHS for all travelers; and (2) the reliability of the Interstate System for longer haul freight movements. Reliability focuses on variability in travel times, and the travel time measures in this rulemaking focus on identifying portions of the NHS and Interstate (for freight) that have high levels of unreliable travel. An example of unreliable travel is a trip that takes 30 minutes on a typical day but could take over 45 minutes on a random day. This extra trip time might be due to a road or lane closure, a traffic accident, or bad weather. The FHWA intends that the measure for reliability of the NHS for all travelers would be used to identify the areas of the transportation network where there are the greatest impacts on travel when non-recurring incidents occur. Non-recurring incidents include temporary disruptions, such as incidents ranging from a flat tire to an overturned hazardous material truck, work zones, weather, and special events. In contrast, the proposed measure for freight travel time reliability is based only on freight travel and considers the longest travel times experienced as compared to travel times more likely during normal travel time conditions throughout all hours of the day. The index provided by this reliability measure is an important piece of information for shippers and suppliers so they can plan for a higher likelihood of on-time arrivals of deliveries. These reliability measures are discussed in more detail in the section-by-section portion of this NPRM.
The FHWA is proposing two measures to assess traffic congestion: (1) One measure to represent congestion impacting freight movement, which is proposed in Subpart F; and (2) One measure to represent overall traffic congestion, which is proposed in Subpart G. Although both proposed measures use delay as the basis for determining congestion, the two differ in design and intended purpose.
The first proposed congestion measure related to freight movement is focused on delay and is intended to be used to assess delay that could occur on the Interstate System. This proposed delay measure represents the percentage of the Interstate System that is uncongested as defined by a speed threshold of 50 mph. The FHWA aimed to understand the point of inflection to consider speeds and viewed 50 mph as appropriate for this measure. This is due in part because trucks often have speed governors installed on them so that they cannot travel much faster than 55 mph. Additionally, freight stakeholders commented that 50 mph or greater is where they would like to be in terms of average speed. The FHWA is seeking comment on this threshold.
The second proposed measure, related to traffic congestion and focused on Annual Hours of Excessive Delay Per Capita, is intended to be used to assess delays that FHWA believes would be considered excessive by users of the NHS roadways in large urbanized areas. This proposed delay measure is an indication of the additional time spent by all users of the system (quantified by the total estimated vehicles using the system) when traveling at speeds considerably lower than typical speed limits. In addition, this measure is proposed to be only applicable to the largest urbanized areas in the country: The portion of those that exceed a population of 1 million.
Three of the eight measures proposed in this rulemaking focus on measuring reliable performance: (1) Section 490.507(a)(1) Percent of the Interstate System providing for reliable travel times, (2) Section 490.507(a)(2) Percent of the non-Interstate NHS providing for reliable travel times, and (3) Section 490.607(a) Percent of the Interstate System Mileage providing reliable truck travel times. The discussions provided in this section provide an explanation of how “reliable” performance is defined, understanding that the meaning of this term can be very subjective, especially when discussing outcomes that are derived from travel time and speed data. Each of the measures that focus on “reliable” performance includes a clearly defined calculation to remove any subjectivity in the meaning of the term. As discussed above, FHWA is proposing measures that, although they include similar methods of calculation, would be used to assess different aspects of highway performance. In general, reliable performance for the five proposed measures can be grouped as follows:
• Subpart E—Travel time reliability as being
• Subpart F—Truck travel time reliability as being
Additional discussion is provided in each subpart to explain the method used to identify the percentage of the transportation network that would be considered “reliable” to these different users and stakeholders.
The measures being proposed in this rulemaking that are derived from travel times reflect: System reliability, peak hour travel times, truck congestion, and excessive delay. With the exception of excessive delay, FHWA did not factor the volume of traffic in the calculations for these proposed measures. Consequently, these measures do not directly capture the weight of traffic volumes in the results. Rather, the measures are calculated based on the
In this simplified example using a mileage based approach 13 direction-miles, or 65.0 percent (13/20), of the network would be considered “reliable,” and using a volume weighted approach 239,500 VMT, or 74.2 percent (239,500/322,700), of the VMT would have been “reliable.” This example illustrates the differences in these two approaches.
Except for the excessive delay measure, FHWA elected to use a mileage based approach and not to weigh the measures by volume due to the absence of data regarding actual traffic volumes particularly for the level of roadway coverage and granularity needed (entire NHS and 5-minute temporal granularity). The system reliability, peak hour travel times, and truck congestion measures are intended to evaluate system performance. This objective can be achieved by analyzing performance on roadway segments and then indicating, via roadway segment length, whether or not a segment is performing to a satisfactory level (based on thresholds defined in this rule). If actual, observed volumes were available at these roadway segment levels every 5 minutes as well, an optional approach would be to identify the amount of VMT that met the measure thresholds, as demonstrated in Table 8. This would require actual volume counts every 5 minutes for every NHS road segment, data which do not currently exist. The FHWA believes it would be inappropriate to introduce estimated data for these measures, which are otherwise focused on actual data. As a result, FHWA is proposing the use of roadway segment length as the means for reporting the metrics and measures.
In addition, FHWA believes performance expressed as the percent of the system mileage is more easily understood by the public as compared to measures that would be expressed as the percentage of vehicle miles traveled. The FHWA encourages State DOTs and MPOs to consider strategies that would provide the greatest impact to improving the performance of overall traffic volumes by focusing on roadway segments that carry higher volumes of traffic.
The Total Excessive Delay measure, on the other hand, needs to be weighted by something to be meaningful, as it is basically a sum of all the excessive travel times on the NHS in an urban area. If excessive delay during a 5 minute period (say 5 seconds) were simply totaled for every 5 minute period and roadway segment, then the excessive delay travel time on a roadway segment with one car would be equivalent to a roadway segment with 110 cars. Such an analysis would not capture the scope of the delay (how many vehicles are actually experiencing that 5 second excessive travel time). Hourly volumes (of vehicles) are a typical means of weighting delay measures. Therefore, for the Total Excessive Delay measure, FHWA requires development of hourly volumes based on actual vehicle counts or estimated from AADT (an estimated number from limited vehicle count data). State DOTs and MPOs can develop hourly volume estimates with AADT information provided to HPMS every year for their NHS roadways. In this case, using the best-available data, even if it is estimated, is preferable than not using such data, because DOTs and MPOs would have difficulty setting targets for this measure without weighting it by the number of vehicles experiencing the delay.
The FHWA is seeking comments on this approach and encourages comments suggesting alternative methods that may more effectively capture the impact of performance changes on differing levels of system use.
In addition to travel time reliability, FHWA is proposing travel time or speed based measures to assess and manage the worst areas of delay or congestion in large urbanized areas. The FHWA felt that this type of measure was most applicable to urbanized areas where populations are greater than 1 million, as these areas are where delay is most likely to occur, and where State DOTs and MPOs likely have a greater level of capability, experience, and need to manage the traffic operations. As proposed, three of the seven travel time or speed based measures are limited to these large urbanized areas. They are: (1) Section 490.507(b)(1) Percent of the Interstate System where peak hour travel times meet expectations, (2) section 490.507(b)(2) Percent of the non-Interstate NHS where peak hour travel times meet expectations, and (3) section 490.707 Annual Hours of Excessive Delay Per Capita. The peak hour travel time measures capture congestion only during peak periods of use (commute-related congestion) and the annual hours of excessive delay per capita captures congestion throughout the day (overall delay).
The FHWA is proposing that only urbanized areas over 1 million in population would be subject to these measures because of the additional performance-reporting requirements that these areas, which are also nonattainment or maintenance areas, have to complete for the CMAQ-related measures (23 U.S.C. 149(l)) including Annual Hours of Excessive Delay per Capita. By requiring MPOs in these areas to do additional CMAQ performance reporting, Congress placed a special emphasis on these larger urbanized areas. The FHWA considered this emphasis when it evaluated
In FHWA's experience, areas over 1 million in population are generally more complex from a transportation perspective. Those areas have more population, resulting in more trips. These areas also tend to have a variety of transportation options available, including highways, airports, commercial rail. In more concentrated urban environments, the areas may also be more constrained in terms of where any new facilities to accommodate demand can be located. There also may be higher costs for right-of-way acquisition. For all these reasons, FHWA's experience is that transportation planning in these larger urban areas is generally more complex than in areas less than 1 million in population, resulting in a greater need to manage the transportation system and, specifically, traffic operations. In addition, these larger areas do receive more Surface Transportation Program suballocated funding than smaller areas (see 23 U.S.C. 133(d)). For all these reasons, FHWA believe it is important that these areas look more closely peak hour travel times and excessive delay as they are managing traffic operations.
The FHWA also considered whether the measure should apply: To another subset of areas within the State, such as areas where MPOs serve a TMA
Within the United States there are 42 urbanized areas that have populations greater than 1 million based on the most recent U.S. Census (2010). These 42 areas are included within or intersect with 35 State and 67 metropolitan planning area boundaries. The FHWA is proposing that for these measures (traffic congestion measure and the peak hour travel time measures for system performance), one single target be established for the roadways within the urbanized area, including those areas that intersect with multiple State and metropolitan planning area boundaries. This single target would need to be agreed upon and shared by all of the entities in the urbanized area. For example, one target would be established for the Philadelphia urbanized area that would be shared by the four States and four MPOs that collectively make transportation investment decisions for the area. The FHWA recognizes that for these large areas, performance is not constrained by political boundaries and that strategies to address performance should be addressed regionally and across political boundaries. For these measures, strategies taken in one political jurisdiction can have direct and indirect impacts when measuring performance in another proximate political jurisdiction. The FHWA felt that this approach would increase the potential for coordination across jurisdictions to manage the overall performance of the region.
The FHWA heard from many stakeholders that the traffic congestion measure should consider the mobility of travelers using all modes of surface transportation such as highways, commuter railways, bikeways, and walkways. The measure proposed in this rulemaking to assess traffic congestion does not fully address this as it is focused only on vehicle delays on NHS highways. The FHWA elected to propose a vehicle delay measure at this time due to the limited availability of reliable, accurate, comprehensive, and timely data for the other surface transportation modes. This type of data would be needed to calculate a more comprehensive delay measure that considers all travelers and all surface modes of transportation. However, FHWA would like to move to a measure in the future that would consider the mobility of travelers using all surface modes of transportation and is seeking comment on feasible approaches that can be taken to move toward the development of such as measure. The CMAQ traffic congestion delay measure proposed in this rulemaking does consider the travel times of vehicles and passengers to the extent they are captured as sources during data collection. In addition, the CMAQ traffic congestion delay measure is expressed as a rate by dividing the total vehicle delay in the area by the total population of the area, which would potentially reflect successful implementation of strategies to provide transportation choices other than highway travel. This proposal is discussed in more detail in the Section-by-Section portion of this preamble for Subpart G.
The FHWA heard from many stakeholders that the traffic congestion measure should directly capture the impact of transportation network connectivity issues and land use decisionmaking to improve public accessibility to essential services. The FHWA believes that the delay measure proposed in this rulemaking to assess traffic congestion will reflect these types of strategies to the degree they minimize impacts on highway traffic operations. However, FHWA is not proposing a measure to directly assess transportation connectivity or accessibility. The focus of the proposed measure is to improve the operations of the existing network by reducing congestion, and does not assess if the network or use of land, as designed, is providing for the most efficient connections to adequately move people and goods from their origin to their destination. The FHWA believes that the scope of 23 U.S.C. 150(c) relates to establishing measures for State DOTs and MPOs to use to assess traffic congestion for the purpose of carrying out section 149, which is a component of the Federal-aid highway program. Improving overall network connectivity is a priority for DOT and FHWA. Outside of this rulemaking, FHWA, in cooperation with FTA, is actively working with transportation operating agencies and planning organizations on efforts to understand and advance best practices in assessing and managing transportation network connectivity to improve public accessibility to essential services.
In the development of the requirements in Subpart H, FHWA attempted to use a similar approach as in other subparts. Subpart H is focused on emissions reduced by CMAQ-funded projects in a nonattainment or maintenance area. A summary of the framework used is discussed below.
This rulemaking proposes to use data included in the existing CMAQ Public Access System to calculate the metric for the on-road mobile source emissions measure. The CMAQ Public Access System is a database of CMAQ project information reported by each State DOT as part of the CMAQ annual reports to FHWA. The Public Access System contains all CMAQ-funded projects by Federal fiscal year and their estimated emissions reductions by pollutant and precursor applicable to the CMAQ program. For purposes of calculating the on-road mobile source emissions measure, use of this existing data set provides a national data source for emissions reductions estimates and will not require a new data collection process.
While quantitative emissions reductions are expected for most projects entered into the CMAQ Public Access System, it is not required nor has it been possible for some pollutants, especially PM emissions. Project sponsors have always had the option to provide a qualitative assessment based on a reasoned and logical evaluation of a project or programs emission benefits. Also, prior to December 20, 2012, EPA's emission model had significant limitations that made it unsatisfactory for use in microscale analyses of PM
In order to reflect the performance of the CMAQ program in reducing on-road mobile source emissions, FHWA is proposing to include only projects with quantitative emissions estimates in the proposed measure. The FHWA understands that State DOTs and/or MPOs may want to amend their project information with quantitative emissions estimates so the emissions reductions can be included in the performance measure. The FHWA is proposing that State DOTs and/or MPOs be allowed to amend their emissions information for projects in the CMAQ Public Access System to include a quantitative emissions estimate where a qualitative analysis may have been used in the past or, in the case of PM emissions, where an appropriate model was not available. State DOTs and/or MPOs would not be required to amend their project information, but we are also soliciting comments on other ways State DOTs and/or MPOs may update or amend their project information with quantitative emissions estimates for use in implementing this performance measure.
The FHWA heard from stakeholders that while all States receive some level of CMAQ funding, the CMAQ on-road mobile source emissions measure should only apply in nonattainment and maintenance areas. The main purpose of the CMAQ program is to fund transportation projects or programs that will contribute to attainment or maintenance of the NAAQS for O
While the CMAQ Public Access System has been available since summer 2011, and FHWA has been keeping a database of CMAQ projects and their estimated emissions since the beginning of the program, there are opportunities to improve the data. In addition to increasing the number of projects with quantitative emissions estimates, the quality of the data and methods used to calculate emissions can also be improved. The FHWA is developing a tool kit, that will be released in modules beginning late spring 2016, of best practices for estimating emissions by project type for project sponsors to improve the assumptions and calculations used in their quantitative estimates. The FHWA developed cost effectiveness tables
The elements discussed above were used by FHWA to develop the proposed regulations presented in this rulemaking. The next sections of this NPRM provide detailed discussions on each of the proposed measures and how they could be used by State DOTs and MPOs to establish and report on targets and by FHWA to assess progress made toward the achievement of targets.
In this section, FHWA describes the proposed additions to Subpart A, which covers general information, target establishment, reporting, and NHPP and NHFP significant progress determination. This section builds on the proposal introduced in the second NPRM that covered measures to assess pavement and bridge condition on the NHS. For a complete picture, readers are directed to the docket which contains the regulatory text for Subpart A in its entirety. In addition, this section also incorporates the FAST Act changes to the NHPP significant progress determination, and the addition of a requirement for a NHFP significant progress determination. The discussions of the proposed requirements are organized as follows:
• Section 490.101 discusses proposed definitions;
• Section 490.103 describes the proposed data requirements;
• Section 490.105 presents the proposed requirements related to establishing performance targets;
• Section 490.107 discusses reporting on performance targets;
• Section 490.109 describes assessing significant progress toward achieving the performance targets for the NHPP and NHFP; and,
• Section 490.111 discusses the material FHWA would incorporate by reference into the proposed rule.
The proposed measures in this NPRM are summarized in Table 9 below. The proposed measures are grouped in 490.105(c) to better reference the proposed measures throughout Subpart A.
In this section, FHWA proposes to define and describe the proposed use of key terms that will be used throughout this NPRM. The first NPRM and the second NPRM included several definitions (full extent, HPMS, measure, metric, National Bridge Inventory (NBI), non-urbanized area, performance period, and target) that are repeated in this NPRM to clarify the proposed implementation of the performance measures. Please see the docket for the entire listing of proposed definitions and for any additional information.
The FHWA proposes to define “criteria pollutant” in the same way as this term is defined in the general conformity rule at 40 CFR part 93, subpart B (specifically, 40 CFR 93.152). As part of this definition, FHWA proposes to list the transportation-related criteria pollutants from the transportation conformity rule at 40 CFR 93.102(b)(1).
The FHWA proposes to include a definition for “freight bottleneck” for use in Part 490. A freight bottleneck is a segment of the Interstate System not meeting thresholds for freight reliability and congestion, as identified in section 490.613, and any other locations the
The FHWA proposes to include a definition for “Full Extent” to delineate data collection methods that utilize a sampling approach versus those that use a continuous form of data collection.
The FHWA proposes to include a definition for “Highway Performance Monitoring System (HPMS)” because it will be one of the data sources used in establishing a measure and establishing a target. The HPMS is an FHWA maintained, national level highway information system that includes State DOT-submitted data on the extent, condition, performance, use, and operating characteristics of the Nation's highways. The HPMS database was jointly developed and implemented by FHWA and State DOTs beginning in 1974 and it is a continuous data collection system serving as the primary source of information for the Federal Government about the Nation's highway system. Additionally, the data in the HPMS is used for the analysis of highway system condition, performance, and investment needs that make up the biennial Condition and Performance Reports to Congress. These Reports are used by the Congress in establishing both authorization and appropriation legislation, activities that ultimately determine the scope and size of the Federal-aid highway program. Increasingly, State DOTs, as well as the MPOs, have utilized the HPMS as they have addressed a wide variety of concerns about their highway systems.
The FHWA proposes to define “mainline highway” to limit the extent of the highway system to be included in the scope of the proposed pavement performance measures. The proposed definition for mainline highway includes the primary traveled portion of the roadway and excludes ramps, climbing lanes, turn lanes, auxiliary lanes, shoulders, and non-normally traveled pavement surfaces.
The FHWA proposes to include a definition for “measure” because establishing measures is a critical element of an overall performance management approach and it is important to have a common definition that FHWA can use throughout the Part. To have a consistent definition for “measure,” FHWA proposes to make a distinction between “measure” and “metric.” Hence, FHWA proposes to define “metric” as a quantifiable indicator of performance or condition and to define “measure” as an expression based on a metric that is used to establish targets and to assess progress toward achieving the established targets.
The FHWA proposes to include a definition of the “National Performance Management Research Data Set (NPMRDS)” because use of this FHWA-furnished data set by States and MPOs is proposed for calculating metrics to assess: Performance of the Interstate System and non-Interstate NHS in Subpart E; freight movement on the Interstate System in Subpart F; and traffic congestion for the purpose of carrying out the CMAQ Program in Subpart G. The FHWA's proposed definition of the NPMRDS is a data set derived from vehicle-based probe data that includes average travel times representative of all segments of the NHS for all traffic and for freight traffic. It is important to note that for the purpose of this rulemaking, the freight measures require the use of the freight traffic travel times that are representative of freight trucks for those segments that are on the Interstate System only. The NPMRDS includes freight trucks for all segments of the NHS. Segments are defined by the Traffic Message Channel (TMC) location referencing system used by private sector probe data providers. Segment lengths are typically set as the distance between interchanges, intersections, etc., on roadways, and can be as small as 1/10th of a mile or longer than 10 miles, depending on location. The data set contains records that include average travel times for every 5 minutes of every day (24 hours) of the year, recorded and calculated for every travel time segment where probe data is available. The NPMRDS does not include any imputed travel time data (
The FHWA proposes to include a definition for “non-urbanized areas” to provide clarity in the implementation of the provision in 23 U.S.C. 150(d)(2) that allows the State DOTs the option of selecting different targets for “urbanized and rural areas.” As written, the statute is silent regarding the small urban areas that fall between “rural” and “urbanized” areas. Instead of only giving the State DOTs the option of establishing targets for “rural” and “urbanized” areas, FHWA proposes to define “non-urbanized” area include a single geographic area that includes all “rural” areas and small urban areas that are larger than “rural” areas but do not meet the criteria of an “urbanized area” (as defined in 23 U.S.C. 101(a)(34)). This would then allow State DOTs to establish different targets throughout the entire State for urbanized areas and a target for a non-urbanized area. For target establishment purposes, FHWA believes that these small urban areas are best treated with the “rural” areas, as non-urbanized areas, because both of these areas do not have the same complexities that come with having the population and density of urbanized areas and are generally more rural in characteristic. In addition, neither of these areas are treated as MPOs in the transportation planning process or given the authority under MAP-21 to establish their own targets.
The FHWA proposes to include a definition for “Performance period” to establish a definitive period of time during which condition/performance would be measured, evaluated, and reported. The frequency of measurement and target establishment for the measures proposed to implement 23 U.S.C. 150 is not directly or indirectly defined in statute. The FHWA proposes a consistent time period of 4 years that would be used to assess non-safety
The FHWA proposes to include a definition of “Reporting Segment” because, with FHWA's approval, State DOTs and MPOs may choose to combine individual Travel Time Segments (such as the TMC codes referenced in the prior paragraph) into longer, contiguous reporting segments. The FHWA's proposed definition of “Reporting Segment” is the length of roadway that is comprised of one or more contiguous Travel Time Segments that the State DOT and MPOs coordinate to define for metric calculation and reporting.
The FHWA proposes to include a definition for “target” to indicate how measures will be used for target establishment by State DOTs and MPOs to assess performance or condition.
The FHWA proposes to include a definition of “Transportation Management Area (TMA)” consistent with the definition in 23 CFR 450.104.
The FHWA proposes to include a definition of “Travel Time Data Set” because in the event that either (1) NPMRDS data is unavailable, or (2) a State DOT requests, and FHWA approves the use of an equivalent data set, then the approved equivalent set of travel time data can be used to calculate metrics to assess performance of the Interstate System and non-Interstate NHS, freight movement on the Interstate System, and traffic congestion for the purpose of carrying out the CMAQ Program. The FHWA's proposed definition of “Travel Time Data Set” is either the NPMRDS or an FHWA-approved equivalent data set that is used to carry out the requirements in Subparts E, F, and G of Part 490.
The FHWA proposes to include a definition of “Travel Time Reliability” since this term is used to describe proposed measures for the performance of the Interstate System and non-Interstate NHS and for freight movement on the Interstate System. The FHWA's proposed definition for Travel Time Reliability is consistency or dependability of travel times from day to day or across different times of the day. The definition is based on one that FHWA has used in prior research and studies. The FHWA believes that Travel Time Reliability is important to many transportation system users, including vehicle drivers, public transit riders, and freight shippers. All of these users value Travel Time Reliability, or consistent travel times, more than average travel time because it provides reliability and efficiency when planning for trip times.
The FHWA's proposed definition of “Travel Time Segment” is a set length, which is contiguous, of the NHS for which average travel time data are summarized in the Travel Time Data Set (in the NPMRDS, this would be the TMC codes).
The FHWA proposes to incorporate definitions for “attainment area,” “maintenance area,” “metropolitan planning organization (MPO),” “National Ambient Air Quality Standards (NAAQS),” “nonattainment area,” and “Transportation Management Area (TMA)” as these terms are defined in the Statewide and Nonmetropolitan and Metropolitan Transportation Planning Regulations in 23 CFR 450.104.
The FHWA is proposing in section 490.103 data requirements that apply to more than one subpart in Part 490. Additional proposed data requirements that are unique to each subpart are included and discussed in their respective subpart.
In this section, FHWA is proposing that State DOTs would submit urbanized area boundaries in accordance with the HPMS Field Manual. The boundaries of urbanized areas would be as identified through the most recent U.S. Decennial Census unless FHWA approves adjustments to the urbanized area, as submitted by State DOTs and allowed for under 23 U.S.C. 101(a)(34). These boundaries would be maintained in the HPMS and used to calculate measures that are applicable to specific urbanized areas or to assess State DOT progress toward the achievement of targets established for urbanized and non-urbanized areas. These boundaries are to be reported to HPMS in the year the State DOT Baseline Performance Report is due (required in section 490.107(b)), and are applicable to the entire performance period (defined in section 490.101 and described in section 490.105(e)(4)), regardless of whether or not FHWA approved adjustments to the urbanized area boundary during the performance period. The FHWA proposes that the State DOT submitted boundary information would be the authoritative data source for the target scope for the additional targets for urbanized and non-urbanized areas (section 490.105(e)(3)), and progress reporting (section 490.107(b)) for the measures identified in section 490.105(c). As discussed in section 490.105(d)(3), any changes in urbanized area boundaries during a performance period would not be accounted for until the following performance period. The FHWA approved urbanized area data available in HPMS on June 15th (HPMS due date) prior to the due date of the Baseline Performance Report is to be used for this purpose. For example, State DOTs shall submit their first Baseline Performance Period Report to FHWA by October 1, 2018. The FHWA approved urbanized area data available in HPMS on June 16, 2018, is to be used.
In section 490.103(c), FHWA is proposing that the boundaries for the nonattainment and maintenance areas be identified for the entire performance period as they are designated and reported by the EPA under the NAAQS for any of the criteria pollutants applicable under the CMAQ program.
In section 490.103(d), FHWA proposes that State DOTs would continue to submit NHS limit data in accordance with HPMS Field Manual. The FHWA proposed that the State DOT submitted NHS information would be the authoritative data source for determining measure applicability (section 490.105(c)), target scope (section 490.105(d)), progress reporting (section 490.107(b)), and determining significant progress (section 490.109(d)) for the measures identified in section 490.105(c)(1) through (c)(7). As discussed in section 490.105(e)(3)(i), the NHS limits dataset referenced in the Baseline Performance Report is to be applied to the entire performance period, regardless of changes to the NHS approved and submitted to HPMS during the performance period.
Depending on when the final rule for this proposal is effective, FHWA plans to determine and publish which State DOTs and MPOs are required to establish targets for each of the proposed measures in Subparts C through H 1 year prior to State DOT's reporting of the targets for the first performance period. The FHWA plans to make the determination based on the following information: Population data from the latest Decennial Census from the U.S. Census Bureau, NHS data from HPMS, and the EPA designated nonattainment and maintenance area published in the
Beginning with the second performance period and continuing with each performance period thereafter, at the start of each performance period, FHWA will extract the population data from the latest Decennial Census from the U.S. Census Bureau, NHS data from HPMS, and the EPA designated nonattainment and maintenance areas published in the
In section 490.103(e), FHWA is proposing for State DOTs and MPOs to use the NPMRDS data to calculate the metrics defined in sections 490.511, 490.611, and 490.711 to ensure all data used by State DOTs to calculate travel time and speed related metrics are consistent and complete. If more detailed and accurate travel time data exists locally, FHWA is proposing that this data could be used in place of, or in combination with the NPMRDS, provided it is first approved by FHWA.
The NPMRDS is a data set that includes travel times representative of all traffic using the highway system, including a breakdown of travel times of freight vehicles and passenger vehicles. Travel times are recorded on contiguous segments of roadway covering the entire mainline NHS. For the NPMRDS the sources of vehicle probes could include mobile phones, vehicle transponders, and portable navigation devices. Within this data set, the average travel time derived from all vehicle probes traversing each Travel Time Segment is recorded for every 5 minute period throughout every day of the year. This recorded average travel time is referenced as being stored in a “5 minute bin” in this rulemaking. Travel times are only included in the data set if during the 5 minute interval vehicle probes were present to measure travel speeds; consequently, there are no imputed (averaged from similar historical travel periods or estimated) travel times in the data set. The NHS data used in the NPMRDS dataset will be extracted from HPMS on August 15 each year. State DOTs are to provide the necessary NHS information to HPMS in accordance with the HPMS Field Manual. States should make every effort to submit NHS data to HPMS in a timely manner to ensure the NPMRDS dataset is as complete as possible. The NPMRDS is provided monthly and made available to State DOTs and MPOs for their use in managing the performance of the highway system. The FHWA expects to continue to provide for this data at a national level and to make it available to State DOTs and MPOs to ensure the data consistency and coverage needed to assess system performance at a national level.
The FHWA recognizes that some State DOTs and MPOs have developed robust programs to manage system operations, including collection of travel time data that may be more appropriate and effective to use as an alternative source to the NPMRDS. Considering this, FHWA is proposing that State DOTs and MPOs may utilize alternative data sources, referred to hereafter as “equivalent data source(s),” to calculate the travel time metrics proposed in this rulemaking provided the alternative data source is at least “equivalent” in the design and structure of the data as well as extent of coverage both spatially and temporally to the NPMRDS to ensure for consistency in performance assessment at a national level. The FHWA expects that the travel time data set could include a combination of equivalent data source data and NPMRDS data, as long as the combination covers the full NHS. The FHWA is also proposing that State DOTs request and receive approval from FHWA to use equivalent data source(s), to ensure data quality is maintained. The same travel time data for each travel time segment must be used by both State DOTs and MPOs in all measure calculation (in other words, the following must not happen: The State DOT uses NPMRDS and the MPO uses an equivalent data source for the same travel time segment). The FHWA expects that State DOTs and MPOs will work collaboratively to come to agreement on the data sources to use to meet the requirements proposed in this rulemaking.
The FHWA is proposing in section 490.103(e) that the use of equivalent data source(s) be requested by State DOTs and approved by FHWA before the beginning of a performance period. The FHWA anticipates that State DOTs could change their data source during a performance period, recognizing that over this period a State DOT may elect to use an equivalent data source(s) or change back to the NPMRDS based on future data options, quality, and availability. The FHWA is proposing
For example, a State DOT can elect to use the NPMRDS for the first performance period (anticipated to begin on January 1, 2018). If the State DOT acquires the resources to collect more accurate and complete data in 2019, the State DOT would need to submit a request for FHWA's approval of the equivalent data source(s), including the travel time segment(s) it is being used on, no later than October 1, 2019, and FHWA would have to approve its use. The State DOT could then use the FHWA approved equivalent data source(s) to calculate the travel time and speed metrics beginning on January 1, 2020.
The FHWA is proposing that for each performance year, the same data sources (
The FHWA is proposing for State DOTs to establish, in coordination with applicable MPOs, and submit reporting segments as discussed in section 490.103 of this rulemaking. State DOTs and MPOs must use the same reporting segment for the purposes of calculating the metrics and measures proposed in subparts E, F, and G.
The State DOT and MPO must use the same reporting segments for all subparts. Several measures would use the information calculated from the reporting segments and convert segment length into mileage to calculate the actual measure, which is described in more detail for each specific measure.
Reporting segments would be distinct sections of roadway that could include one or more contiguous travel time segments. This requirement is being proposed as FHWA anticipates that State DOTs would prefer to join shorter travel time segments into more logical lengths of roadway for reporting purposes. To maintain the granularity needed to capture performance changes, FHWA is proposing that in urbanized areas, reporting segments would not exceed
In order to ensure that the reporting segments cover the complete NHS within a State, FHWA is proposing that the reporting segments be continuous and cover the full extent of the mainline highways of the NHS. The FHWA considered alternative approaches to defining reporting segments that would represent roadway key corridors to show travel time performance for the Interstate System and non-Interstate NHS. Although FHWA believes that corridor level evaluations are effective in managing system operations, we did not feel that a corridor based approach could be designed and implemented in manner that would provide for the consistency and reliability needed to report on performance at a State and national level. For this reason, FHWA is proposing that the reporting segments represent 100 percent of the mainline highways on the NHS applicable to the measures in subparts E, F, and G.
Although the State DOTs would be the entity required to submit reporting segments, MPOs would need to coordinate with State DOTs on defining these reporting lengths for those roadways that are within the portion of the metropolitan planning area included within the State boundary. In addition, it is recommended that States DOTs coordinate with any local transportation operating agencies that have influence over the management of traffic operations in making the final decision on reporting segment lengths.
In section 490.103(g), FHWA is proposing that the State DOT would submit its reporting segments to FHWA no later than November 1, prior to the beginning of the calendar year in in which they will be used. These reporting segments would be used throughout the performance period. If the State DOT requests and FHWA approves an equivalent travel time data source during the performance period, the State DOT would need to submit a new set of reporting segments that would correspond to the new travel time data source segmentation. These reporting segments are to be submitted to FHWA by November 1 prior to the beginning of the calendar year in which they will be used. For the purposes of carrying out the requirements proposed in Subpart E, FHWA is proposing that the State DOT submit the travel times desired for each reporting segment that is fully included within urbanized areas with populations over 1 million during the peak period travel times (both morning and evening). The FHWA is proposing that State DOTs would submit reporting segments and the desired travel times to HPMS. The FHWA intends to issue additional guidance on how State DOTs could report these data to HPMS. Finally, the State DOT would be required to submit documentation to demonstrate the applicable MPOs' agreement on the travel time data set used, the defined reporting segments, and the desired travel times.
Performance target requirements specific to HSIP-related measures would be established in accordance with section 490.209 of the first performance management NPRM; and performance target requirements specific to pavement condition measures in sections 490.307(a) and bridge condition measures in sections 490.407(c) are included in the second performance management NPRM. The discussions specific to those measures will not be repeated in this NPRM. For additional information, please see the docket for the proposed regulatory text for Part 490, in its entirety that covers both prior NRPMs.
The declared policy under 23 U.S.C. 150(a) transforms the Federal-aid highway program and encourages the most efficient investment of Federal transportation funds by refocusing on national transportation goals, increasing accountability and transparency in the Federal-aid highway program, and improving investment decisionmaking. To this end, FHWA encourages State DOTs and MPOs to establish targets that would support the national transportation goals while improving investment decisionmaking processes.
A number of considerations were raised during the performance management stakeholder outreach sessions regarding target establishment, such as: Providing flexibility for State DOTs and MPOs, coordinating through the planning process, allowing for appropriate time for target achievement, and allowing State DOTs and MPOs to incorporate risks. Using these considerations, FHWA created a set of principles to develop an approach to implement the target establishment requirements in MAP-21. These principles aimed to develop an approach that:
• Provides for a new focus for the Federal-aid program on the MAP-21 national goals under 23 U.S.C. 150(b);
• improves investment and strategy decisionmaking;
• considers the need for local performance trade-off decisionmaking;
• provides for flexibility in the establishment of targets;
• allows for an aggregated view of anticipated condition/performance; and
• considers budget constraints.
In section 490.105, FHWA proposes the minimum requirements for State DOTs and MPOs to follow in the establishment of targets for all measures identified in section 490.105(c), which include the proposed measures both in this performance management NPRM and the second performance management NPRM. This regulatory text, in its entirety, can be found in the docket. These requirements are being proposed to implement the 23 U.S.C. 150(d) and 23 U.S.C. 134(h)(2) target establishment provisions in a manner that provides for the consistency necessary to evaluate and report progress at a State, MPO, and national level, while also providing a degree of flexibility for State DOTs and MPOs.
The FHWA proposes in section 490.105(a) for State DOTs and MPOs to establish targets for each performance measure identified in section 490.105(c). In section 490.105(b), the performance targets for carrying out the HSIP would be established in accordance with section 490.209 of the first performance management NPRM.
In section 490.105(c), FHWA proposes that State DOTs and MPOs that include, within their respective geographic boundaries, any portion of the applicable transportation network or projects would establish performance targets for the performance measures identified in Subparts C through H. The transportation network or geographic areas applicable to each measure is specified in Subparts C through H under sections 490.303, 490.403, 490.503, 490.603, 490.703, and 490.803, respectively. It is possible that for some measures, the applicable transportation network or geographic area may not be contained within the State or metropolitan planning area geographic boundary. In these cases State DOTs and MPOs would not be required to establish targets. The performance target requirements established by Congress in 23 U.S.C. 135(d)(2)(B)(i)(I) and 23 U.S.C. 134(h)(2)(B)(i)(I) require State DOTs and MPOs to establish targets for the measures described in 23 U.S.C. 150(c), where applicable. Consequently, State DOTs and MPOs are only required to establish targets where their respective geographic boundary contains portions of the transportation network or geographic area that are applicable to the measure. For example, the proposed measure Percent of the Interstate System providing for Reliable Travel Times specified in section 490.507(a)(1) is applicable, as proposed in section 490.503(a)(1), to “mainline highways on the Interstate System.” In this example, if Interstate System mainline highways are not contained within the boundary of an MPO's metropolitan planning area the measure would not be applicable to that MPO. As a result, that MPO would not be required to establish a target for the proposed measure Percent of the Interstate System providing for Reliable Travel Times specified in section 490.507(a)(1).
The FHWA proposes in section 490.105(d)(1) that State DOTs establish statewide targets that represent performance outcomes of the transportation network or geographic area within their State boundary, and MPOs establish targets that represent performance outcomes of the transportation network or geographic area within their respective metropolitan planning area for the proposed NHS travel time reliability measures (section 490.507(a)), freight movement on the Interstate System measures (section 490.607), and on-road mobile source emissions measure (section 490.807). State DOTs and, if applicable, MPOs are encouraged to coordinate their target-establishment with neighboring States and MPOs to the extent practicable.
The FHWA proposes in section 490.105(d)(2) that State DOTs and MPOs would establish a single urbanized area target, as described in sections 490.105(e)(8) and 490.105(f)(4), respectively, that would represent the performance of the transportation network in each area applicable to the peak hour travel time measures (section 490.507(b)) and traffic congestion measure (section 490.707) as proposed in sections 490.503(a)(2) and 490.703, respectively. The applicable areas for the peak hour travel time measures are proposed to be urbanized areas with a population greater than 1 million. A subset of these areas would be applicable to the traffic congestion measure: Those areas that also contain any part of an area designated as nonattainment or maintenance for any of the criteria pollutants applicable under the CMAQ program. Based on the 2010 U.S. Census,
In section 490.105(d), FHWA recognizes that there is a limit to the direct impact the State DOT and the MPO can have on the performance outcomes within the State and the MPO, respectively, and recognizes that the State DOT and the MPO need to consider this uncertainty when establishing targets. For example, some Federal and tribal lands include roads and bridges on the NHS that State DOTs would need to consider (as appropriate) when establishing targets. The FHWA anticipates that State DOTs and MPOs would need to consult with relevant entities (
The FHWA also recognizes that the limits of the NHS could change between the time of target establishment and the time of progress evaluation and reporting for the targets for measures specified in sections 490.105(c)(1)
In section 490.105(e), FHWA proposes the State DOT requirements for the establishment of targets for all measures identified in section 490.105(c), with applicable transportation network for those targets (target scope) defined in section 490.105(d). As defined in section 490.101, a target is a numeric value that represents a quantifiable level of condition/performance in an expression defined by a measure. The FHWA proposes that a target would be a single numeric value representing the intended or anticipated condition/performance level at a specific point in time. For example, the proposed measure, Percent of the Interstate System providing for Reliable Travel Times (in section 490.507(a)(1)), would be a percentage of directional mainline highways on the Interstate System providing for Reliable Travel Times (sections 490.503(a)(1) and 490.513(b)) expressed in one tenth of a percent. Thus, FHWA proposes that a target for this measure would be a percentage of directional mainline highways on the Interstate System providing for Reliable Travel Times expressed in one tenth of a percent. As a hypothetical example, a 2-year target and a 4-year target would be 39.5 percent and 38.5 percent, respectively for the proposed measure Percent of the Interstate System providing for Reliable Travel Times.
Pursuant to 23 U.S.C. 150(d)(1) and (e), FHWA proposes in section 490.105(e)(1) that State DOTs would establish targets within 1 year of the effective date of this rule, and for each performance period thereafter the State DOTs would establish and report the targets to FHWA by the due date provided in section 490.107(b)(1). The FHWA is proposing that this rule would have an individual effective date. Accordingly, FHWA anticipates the final rule for this proposal would be effective no later than October 1, 2017. This would provide for at least a 1-year period for States to establish targets so that they can be reported in the first State Biennial Performance Report which would be due to FHWA by October 1, 2018. The FHWA recognizes that if the final rule is effective after October 1, 2017, the due date to report State DOT targets for the first performance period may need to be adjusted. If it becomes clear that the final rule will not be effective until after October 1, 2017, FHWA will consider adjusting the due date in the final rule or issuing implementation guidance that would provide State DOTs a 1-year period to establish and report targets.
The proposed schedule would require the establishment and reporting of targets at the beginning of each performance period or every 4 years. With the exception of the allowance proposed in section 490.105(e)(6), FHWA is proposing that State DOTs will not have the ability to change targets reported for a performance period. Considering this proposed limitation, State DOTs would need to provide for sufficient time to fully evaluate their targets before they are due to be reported to FHWA.
Pursuant to 23 U.S.C. 135(d)(2)(B)(i)(II), FHWA proposes in section 490.105(e)(2) that State DOTs coordinate with relevant MPOs to establish consistent targets, to the maximum extent practicable. The coordination would be accomplished in accordance with 23 CFR 450. The FHWA recognizes the need for State DOTs and MPOs to have a shared vision on expectations for future condition/performance in order for there to be a jointly owned target establishment process. This coordination is particularly needed for the establishment of the targets for the peak hour travel time and traffic congestion measures since a single target will be established for each applicable
Traffic congestion measure: Urbanized area with a population greater than 1 million and also any part of the urbanized area is designated as nonattainment or maintenance for any of the criteria pollutants applicable under the CMAQ Program.
The FHWA proposes in section 490.105(e)(3) to allow State DOTs to establish additional targets, beyond the required statewide target, for any of the proposed measures for the travel time reliability measures and freight movement on Interstate System measures described in sections 490.507(a) and 490.607, respectively. This is intended to give the State DOT flexibility when setting targets and to aid the State DOT in accounting for differences in urbanized areas and the non-urbanized area. The State DOT could establish additional targets for any number and combination of urbanized areas and could establish a target for the non-urbanized area for any or all of the proposed measures. For instance, a State DOT could choose to establish additional targets for a single
As proposed in section 490.105(e)(3)(v), for some measures State DOTs will not be able to establish additional targets. Since peak hour travel time measures and traffic congestion measures are proposed to apply only to certain urbanized areas
Traffic congestion measure: Urbanized area with a population greater than 1 million and also any part of the urbanized area is designated as nonattainment or maintenance for any of the criteria pollutants applicable under the CMAQ Program.
If a State DOT chooses to establish additional performance targets, it would increase the number of performance targets that it reports. For example, at a minimum, State DOTs would be required to establish two statewide targets for NHS travel time reliability measures (separate target for each of the two measures identified in section 490.507(a)). If a State DOT chooses to establish additional targets for the two NHS travel time reliability measures for the single largest urbanized area in its State, the State DOT would increase the total number of NHS travel time reliability targets to four (2 required targets + 2 additional urbanized area targets = 4).
For each additional target established, State DOTs would evaluate whether they have made progress toward achieving each target and report on that progress in their biennial performance report in accordance with sections 490.107(b)(2)(ii)(B) and 490.107(b)(3)(ii)(B).
Any additional targets the State DOT chooses to establish would not be subject to the significant progress assessment in section 490.109. Because these additional targets are optional and subcomponents of targets established under section 490.105(d), including them in the significant progress assessment proposed in section 490.109 could result in “double counting” during that assessment. The FHWA believes that excluding these additional targets from the significant progress assessment in section 490.109 provides an opportunity for some flexibility with respect to establishing the targets and may encourage State DOTs to establish these additional targets.
Historically, the Census has defined urbanized areas every 10 years, and these boundaries can be adjusted (see 23 U.S.C. 101(a)(34)). The FHWA recognizes that the urbanized area boundaries and resulting non-urbanized area boundary have the potential to change on varying schedules. Changing a boundary during a performance period may lead to changes in the measures reported for the area, and could impact how an established target relates to actual measured performance. Thus, FHWA proposes that State DOTs would need to describe the urbanized area boundaries and the non-urbanized area boundary in place at the start of a performance period in the Baseline Performance Period Report, and use those same boundaries throughout a performance period. This will eliminate the potential for inconsistencies in the extent of the network used to establish targets and calculate measures in urbanized areas and the non-urbanized area, and provide consistency in reporting established targets for those areas.
The urbanized area boundaries are to be reported to HPMS in the year the Baseline Performance Report is due, and are applicable to the entire performance period, regardless of whether or not FHWA approved adjustments to an area boundary during the performance period for other reasons. Any changes in area boundaries during a performance period would not be accounted for until the following performance period.
The FHWA is seeking comments on this approach for establishing optional additional targets for urbanized areas and the non-urbanized area. The FHWA would also like comments on any other flexibility it could provide to or identify for State DOTs related to the voluntary establishment of additional targets. Some examples include:
• Providing options for establishing different additional targets throughout the State, particularly for the States' non-urbanized area; and
• Expanding the boundaries that can be used in establishing additional targets (
As described in section 490.105(f), an MPO would have the option to establish a quantifiable target for their metropolitan planning area. As provided in 23 CFR 450.312, the boundaries of the metropolitan planning area include, at a minimum, the entire existing urbanized area (as defined by the Census Bureau) plus the contiguous area expected to become urbanized within a 20-year forecast period. The FHWA recognizes the challenges in coordinating targets between State DOTs and MPOs, especially in cases where urbanized and metropolitan planning areas cross multiple State boundaries. The FHWA intends for State DOTs and the MPOs to collectively consider boundary differences when establishing both State DOT and MPO targets. For reporting purposes, FHWA expects MPOs to report progress to the relevant State DOT for the entire metropolitan planning area. Multistate MPOs would also be expected to provide the data stratified by State. The FHWA seeks comments on target establishment options and coordination methods that could be used by MPOs and State DOTs in areas where the MPO metropolitan planning area crosses multiple States.
To illustrate the differences in boundaries and how they might be addressed for one of the travel time reliability measures, the following example is provided regarding the target establishment boundary differences that could exist in the State of Maryland today.
• Urbanized Areas: Based on the 2010 Decennial Census, the State of Maryland
• Metropolitan Planning Areas: Currently, the State contains part or all of six metropolitan planning areas. Of these areas, four metropolitan planning areas are shared with neighboring States (A map of Metropolitan Planning Areas and Urbanized Areas of the State of Maryland is included in the docket).
• Statewide Urbanized Area Target Extent: An optional State target for the Percentage of Interstate System lane-miles in Good condition within the State's urbanized areas would represent those portions of the 11 urbanized areas within the geographic boundary of the State of Maryland, in aggregate.
• Single Urbanized Area Target Extent: An optional urbanized area target for a single urbanized area would represent the anticipated Percentage of Interstate System lane-mileage in Good condition within the identified urbanized area, based on the corresponding boundary described in the Baseline Performance Period Report. In the case of the Hagerstown urbanized area, the target would be established for the portion of the urbanized area in the State of Maryland.
• MPO Target Extent: Each of the six MPOs would establish individual targets for representing the anticipated percentage of the Interstate System providing for Reliable Travel Times within their entire metropolitan planning area, regardless of State boundary. In the case of the Hagerstown—Eastern Panhandle MPO in Maryland/Pennsylvania/West Virginia, the MPO would establish target for the Interstate System providing for Reliable Travel Times within its metropolitan planning boundary that extends beyond Maryland State boundary and into Pennsylvania and West Virginia State boundaries, while the Maryland DOT would establish its target for the area only within its State boundary.
The FHWA is seeking comment on alternative approaches that could be considered to effectively implement 23 U.S.C. 134(h)(2)(B)(i)(I) and 23 U.S.C. 150(d)(2) considering the need for coordination required under 23 U.S.C. 134(h)(2)(B)(i)(II) and 23 U.S.C. 135(d)(2)(B)(i)(II). The FHWA is also requesting comment on whether the regulations should include more information or specificity about how the MPOs and States should coordinate on target establishment. For some measures proposed in this NPRM, MPOs could establish targets up to 180 days after the State DOT establishes its targets.
The FHWA proposes in section 490.105(e)(4) that State DOTs establish targets with a 2-year time horizon (
The FHWA is proposing this definitive performance period while recognizing that planning cycles and time-horizons for long-term performance expectations differ among State DOTs. The FHWA believes that although differences exist, it was necessary to utilize a 4-year performance period considering the following implementation expectations:
• Provide for a link between the interim, short-term targets (
• Ensure the time horizon is long enough to allow for condition/performance change to occur through the delivery of programmed projects;
• Align the schedule of reporting on targets and the evaluation of progress toward achieving the targets with the biennial performance reporting requirements under 23 U.S.C. 150(e); and
• Report targets using a consistent performance period as part of the evaluation of the State DOT's effectiveness of performance-based planning process to the Congress by October 1, 2017, as required by 23 U.S.C. 135(h).
The FHWA anticipates that the State DOTs would establish targets for the measures listed in section 490.105(c) and report the established targets to FHWA by the statutory deadline for the first biennial report of October 1, 2018.
In addition, FHWA considered the data collection and reporting cycles associated with proposed measures. For example, the timeframe of collected data used for calculating a measure for the proposed measures in paragraphs (c)(1) through (c)(7) is on a calendar year basis, but the timeframe of reported data used for calculating a measure for the proposed on-road mobile source emissions measure in paragraph (c)(8) is on a Federal fiscal year basis. The FHWA also assessed the inherent time lag between data collection and target establishment due to necessary data processing, data quality management,
As shown in Figure 1, for the first performance period for all measures except on-road mobile source emissions measure in paragraph (c)(8), the latest measured condition/performance data through December 31, 2017, is the baseline condition/performance. The State DOTs would establish 2-year targets as the condition/performance anticipated at a midpoint, which would be indicated by the latest measured condition/performance data through the midpoint of the performance period (December 31, 2019, for the first performance period). Similarly, the State DOTs would establish 4-year targets as the condition/performance anticipated at the end of a performance period which would be indicated by the latest measured condition/performance data through the end of the performance period (December 31, 2021, for the first performance period). The FHWA recognizes that the previously programmed projects may have an impact on the target a State DOT establishes for the first performance period. State DOTs should consider the impact of previously programmed projects on future performance outcomes when establishing their targets.
As illustrated in Figure 2, the latest 4-year cumulative emissions reductions results from CMAQ projects from fiscal year 2014 through fiscal year 2017, is the baseline condition/performance. For the first performance period for the on-road mobile source emissions measure, State DOTs would establish 2-year targets which would reflect the anticipated cumulative emissions reductions resulting from CMAQ projects to be reported in the CMAQ Public Access System (described in section 490.809) for the Federal fiscal years 2018 and 2019. Thus, the 2-year target would be the anticipated sum of total emission reductions in the CMAQ Public Access System for the Federal fiscal years 2018 and 2019 for each criteria pollutant and applicable precursors for which the area is nonattainment or maintenance. Similarly, the State DOTs would establish 4-year targets as the anticipated cumulative emissions reductions resulting from CMAQ projects to be reported in the CMAQ Public Access System for the Federal fiscal years 2018 through 2021. Thus, the 4-year target would be the anticipated sum of total emission reductions in the CMAQ Public Access System for the Federal fiscal years 2018 through 2021 for each criteria pollutant and applicable precursors for which the area is nonattainment or maintenance. Similar to other measures, FHWA recognizes that the previously programmed CMAQ projects may have an impact on target a State DOT establishes for the first performance period. State DOTs should consider the impact of previously programmed CMAQ projects on future performance outcomes when establishing their targets.
It is important to note that the timeframe of collected data used for calculating a measure depends on the individual measure. Data collection frequency requirements and the timeframe for when State DOTs and MPOs would collect data used for calculating a measure are proposed in the Data Requirement and Calculation of Performance Measure Sections for each measure in the relevant Subparts. This proposed timeline, depicted in Figures 1 and 2, is intended to: (1) Satisfy the first State DOT biennial performance
The FHWA proposes in section 490.105(e)(5) that State DOTs report their established targets (2-year and 4-year) and progress toward achieving their targets in the biennial performance report required by 23 U.S.C. 150(e) as specified in section 490.107. As discussed in section 490.105(e)(2), State DOT coordination with relevant MPOs is required for selection of targets. Thus, FHWA proposes that the State DOTs would be able to provide relevant MPOs' targets to FHWA, upon request, each time the relevant MPOs establish or adjust MPO targets as described in section 490.105(f).
The FHWA recognizes that State DOTs would need to consider many factors in establishing targets that could impact progress such as uncertainties in funding, changing priorities, and external factors (see section 490.109(e)(5)) outside the control of the State DOTs.
Thus, FHWA proposes in section 490.105(e)(6) that State DOTs may adjust their established 4-year targets when they submit their State Biennial Performance Report just after the midpoint of the performance period (
In section 490.105(e)(7), FHWA proposes a phase-in for the establishment of targets for the non-Interstate NHS travel time reliability measure, provided in section 490.507(a)(2). This phase-in would require only State DOTs to establish 4-year targets for the first performance period for this measure (reported in the 1st State Biennial Performance Report as illustrated in Figure 1) for non-Interstate NHS travel time reliability measure, provided in section 490.507(a)(2). The FHWA is proposing this phase-in to allow sufficient time for State DOTs and MPOs to become more proficient in managing performance of non-Interstate roadways and for the coverage of the data, during peak periods, to become more complete in the NPMRDS. At the midpoint of the first performance period State DOTs would have the option to adjust the 4-year targets they established at the beginning of the performance period in their State Biennial Performance Report (report due in October 2020 as illustrated in Figure 1). This will allow State DOTs to consider more complete data in their decision on the 4-year targets for non-Interstate NHS travel time reliability. Although 2-year targets would not be established in the first performance period, FHWA is proposing that State DOTs still would report metrics annually, as required in section 490.511(d)), for the non-Interstate NHS travel time reliability measure.
Similarly FHWA is proposing to phase-in the reporting of baseline travel time reliability performance for the non-Interstate NHS travel time reliability measure. The FHWA proposes that State DOTs would report baseline performance in the 2nd State Biennial Performance Report in 2020 (instead of the 1st report due in 2018) for non-Interstate NHS travel time reliability. This baseline would represent the performance through the end of 2019 (
In section 490.105(e)(8), as discussed in sections 490.507(b) and 490.707, FHWA proposes that the peak hour travel time measure would apply to the roadway transportation network in urbanized areas with a population over 1 million and the traffic congestion measure would include these same areas that also contain areas designated as nonattainment or maintenance areas for any of the criteria pollutants applicable under the CMAQ program. The FHWA proposes that State DOTs, with mainline highways on the Interstate System that cross any part of an urbanized area with a population more than 1 million within its geographic State boundary, would establish a target for peak-hour travel time for the Interstate System for that urbanized area. Similarly, FHWA proposes that State DOTs, with mainline highways on the non-Interstate NHS that cross any part of an urbanized area with a population more than 1 million within its geographic State boundary, would establish a target for peak-hour travel time for the non-Interstate NHS for that urbanized area. The FHWA proposes that if a State DOT is required to establish targets for either of the peak hour travel time measures for an urbanized area and that urbanized area contains any part of a nonattainment or maintenance area for any one of the criteria pollutants, as specified in section 490.703, then that State DOT would also be required establish targets
In deciding to limit the applicability of these performance measures, FHWA considered a number of factors. In general, the boundary limits of large urbanized areas are representative of population size and density. The FHWA believes that the need to plan for and manage transportation demand is greatest in areas of the country where populations are high and more densely located. The FHWA also believes that in these largest urbanized areas State DOTs and MPOs have the experience and capability needed to plan and manage high levels of transportation demand. For these reasons, FHWA is proposing, as discussed in Subparts E and G, an approach to limit the applicability of the peak hour travel time and traffic congestion measures to only those roadway networks that are contained in very large urbanized areas. The FHWA believes that the MAP-21 statewide and metropolitan target establishment provisions
The FHWA is proposing that the applicable areas would be determined at the beginning of a performance period and remain for the duration of the performance period regardless of changes that could result from U.S. Census or EPA designation changes during the performance period.
As population continues to grow there will be an increased potential for large urbanized areas to extend across State borders and/or metropolitan planning area boundaries necessitating an increased level of coordination of multiple entities to plan for and manage transportation demand. The FHWA believes that State DOTs and MPOs should collectively work together to support a common transportation performance vision for the area. The FHWA also believes that, through congestion management planning being done by MPOs serving a TMA as part of the planning process,
State DOTs and MPOs would also be required to establish targets for peak hour travel time and traffic congestion measures for more than one urbanized area if their respective boundaries intersect or include multiple applicable urbanized areas. For example, based on the most recent U.S. Census, Maryland DOT would be required to establish targets for three applicable urbanized areas: Baltimore, Washington, DC, and Philadelphia. As discussed above, the targets established for these three areas would be shared by the other applicable State DOTs and MPOs.
In section 490.105(e)(8)(vi), FHWA proposes a phase-in for the establishment of targets for the traffic congestion measure in section 490.707. As discussed previously for the non-Interstate NHS travel time reliability targets, this phase-in is being proposed to provide sufficient time for State DOTs and MPOs to become more proficient in managing traffic congestion performance and for the travel time data coverage to be more complete in the NPMRDS. The proposed traffic congestion measure requires complete data coverage to capture all excessive delay occurrences throughout the day at a 5-minute level of granularity. In addition, as indicated in section
The FHWA is aware that the NPMRDS will be lacking data on the non-Interstate NHS roadways in the short-term (missing data is discussed in a white paper provided on the docket). If 2-year targets were to be established in the first performance period, the NPMRDS will be lacking data on the non-Interstate NHS roadways. The FHWA anticipates that enough data would be missing to make it difficult for States to establish reasonable targets. By the time the 2-year condition/performance are calculated, FHWA expects the NPMRDS data to have improved to an acceptable level for this measure. Also, States would have time to understand the impact of missing data on target establishment. Full compliance is required starting from the second performance period. Thus, FHWA proposes that for the first performance period, as with the non-Interstate travel time reliability measure, State DOTs would only be required to establish their 4-year targets for the traffic congestion measure in the beginning of the first performance period (
For the first performance period only, the baseline traffic congestion performance would be reported by the State DOT at the midpoint of the performance period in their 2nd State Biennial Performance Report in 2020 (illustrated in Figure 1). This baseline report would represent traffic congestion performance through 2019 (
The FHWA proposes in section 490.105(e)(9) the State DOT target establishment requirements for the proposed on-road mobile source emission measure, identified in section 490.807. In paragraph (i) of this section, FHWA proposes that State DOTs would establish a statewide target for all areas within the State geographic boundaries designated as nonattainment or maintenance for the O
In section 490.105(e)(9)(ii), FHWA proposes that State DOTs would establish separate statewide targets for each of the applicable criteria pollutant and precursor (PM
As proposed in section 490.105(e)(4)(iii) and (e)(4)(iv), the 2-year targets for this measure would reflect the anticipated cumulative emissions reduction to be reported for the first 2 years of a performance period by (
To implement the flexibility in 23 U.S.C. 150(d)(2) that provides State DOTs the option for establishing different targets for different areas of the State and in consideration of the measure that FHWA is proposing for on-road mobile source emissions, FHWA proposes in section 490.105(e)(9)(iv) that State DOTs would have the option of establishing additional targets, beyond the statewide targets, for any number and combination of nonattainment and maintenance areas by applicable criteria pollutant and precursors. For instance, a State DOT could choose to establish additional targets for a single nonattainment and maintenance area and a single applicable criteria pollutant or precursor, a number of areas and applicable pollutants or precursors, or each of the areas and applicable pollutants or precursors separately. A State DOT that has multiple nonattainment and maintenance areas for multiple criteria pollutants could decide to establish a target for one of the areas and for only one of the applicable pollutants or precursors within that area. If a State DOT decides to establish these additional targets, the requirements for these targets are similar to those provided in section 490.105(e)(3). The additional targets would need to be described in the State Baseline Performance Period Report. For each additional target, State DOTs would evaluate whether they have made progress toward achieving the target and report on that progress in their biennial performance report in accordance with sections 490.107(b)(2)(ii)(B) and 490.107(b)(3)(ii)(B).
In sections 490.105(e)(9)(v) and (e)(9)(vi), FHWA proposes that the State DOT's requirement for establishing target(s) for on-road mobile source emission measure would be by the EPA's nonattainment and maintenance areas designations published in the
Although both traffic congestion and on-road mobile source emission measures are proposed to carry out the CMAQ Program, there are some differences in how the targets for the measures would be implemented. As discussed in section 490.105(e)(8), the targets for the traffic congestion measure would apply to the NHS roadway network in urbanized areas with a population over 1 million that also contain areas designated as nonattainment or maintenance for any of the criteria pollutants applicable under the CMAQ Program where as the targets for on-road mobile source emission measure would apply to all nonattainment or maintenance areas for any of the criteria pollutants applicable under the CMAQ Program as discussed in section 490.105(e)(9). The FHWA also proposes that a single, unified target for traffic congestion measure would be established for each applicable urbanized area in the country; whereas target(s) for the on-road mobile source emission measure would be bounded by State geographic boundaries and nonattainment or maintenance areas.
As part of the MPO-State DOT coordination in establishing State DOT and MPO targets described in the discussion of sections 490.105(e)(2) and 490.105(f)(2), FHWA proposes in section 490.105(f)(1) that MPOs establish targets with a 4-year performance period identical to the State DOT's performance periods discussed in the Section-by-Section Discussion for 490.101 and 490.105(e)(4). It is important to emphasize that established MPO targets must be considered as interim conditions/performance levels that lead toward the accomplishment of longer-term performance expectations in the MPO's Metropolitan Transportation Plan
The FHWA proposes in section 490.105(f)(1)(i) that each MPO would establish 4-year targets for all applicable measures in section 490.105(c) no later than 180 days after the relevant State DOT establishes its targets, described in the discussion of section 490.105(e)(1).
The FHWA proposes in section 490.105(f)(1)(ii) that the MPOs with any portion of the applicable roadway network in an urbanized area with a population greater than 1 million would establish both 2-year and 4-year targets for the peak hour travel time measures, as described in section 490.105(f)(4)(i). In addition, the MPOs that have any portion of the applicable roadway network in an urbanized area with a population greater than 1 million and contain areas designated as nonattainment or maintenance would establish both 2-year and 4-year targets for the traffic congestion measure, as described in section 490.105(f)(4)(ii). The FHWA is proposing this approach because, as discussed section 490.105(e)(8), 2-year and 4-year targets established for peak hour travel time and traffic congestion measures would represent the entire urbanized area, and State DOTs and MPOs would report identical targets for each of the applicable urbanized areas. In addition, for the traffic congestion measure, the requirement to have targets every 2 years is consistent with the requirement for these MPOs to report on this target every 2 years under the performance plan requirements of 23 U.S.C. 149(l).
For the on-road mobile source emissions measure, whether an MPO must establish 2-year and 4-year targets or would only be required to establish a 4-year target depends on if the MPO is in an urbanized area with a population greater than 1 million and contains areas designated as nonattainment or maintenance for any of the criteria pollutants applicable to the CMAQ program. An MPO in one of these large urbanized areas would be required to establish both 2-year and 4-year targets for the on-road mobile source emissions measure, as provided in section 490.105(f)(5)(iii). An MPO outside of these large urbanized areas would only be required to establish a 4-year target for the on-road mobile source emissions measure, as required by section 490.105(f)(1)(i); it would not be required to establish a 2-year target as provided in section 490.105(f)(1)(ii). In proposing this approach, FHWA considered that the MPOs in a larger urbanized area would be required to do biennial reporting on these targets under 23 U.S.C. 149(l).
The FHWA recognizes the burden on MPOs, regardless of size, to establish targets. In addition, MPOs are not directly subject to the requirement to evaluate the progress toward achieving NHPP and NHFP targets under 23 U.S.C. 119(e)(7) and 23 U.S.C. 167(j). As a result, FHWA proposes in section 490.105(f)(1)(iii) that MPOs would not be required to establish 2-year targets for the NHS travel time reliability measures and freight movement on Interstate System measures.
In the case of the first performance period, FHWA anticipates that the State DOTs would establish targets for the measures listed in section 490.105(c) prior to the first State DOT biennial performance report, and the MPOs would establish targets no later than 180 days thereafter. The timeline for target establishment for State DOTs is illustrated in Figures 1 and 2 in the discussion of section 490.105(e)(4). The FHWA recognizes that the previously programmed projects may have an impact on the target an MPO establishes for the first performance period. The MPOs should consider the impact of previously programmed projects on future performance outcomes when establishing their targets. As discussed in section 490.105(e)(4), FHWA recognizes that if the final rule is effective after September 30, 2017, the due date to report State DOT targets for the first performance period may need to be adjusted. If the rule is effective on or after September 30, 2017, MPOs may not have the opportunity to establish their own targets in time for State DOTs to consider those MPO targets when submitting the 1st Baseline Performance Period Report. If it becomes clear that the final rule will not be effective until after September 30, 2017, FHWA will consider adjusting the due date in the final rule or issuing implementation guidance that would provide State DOTs a 1-year period and MPOs 180 days thereafter to establish and report targets. The MPOs would be required to establish targets for all applicable measures.
Similar to the requirement for State DOTs, pursuant to 23 U.S.C. 134(h)(2)(B)(i)(II), FHWA proposes in section 490.105(f)(2) that MPOs coordinate with relevant State DOT(s) to establish consistent targets, to the maximum extent practicable. This would be done in accordance with 23 CFR 450.
The FHWA recognizes the burden on the MPOs to establish their own performance targets. Consequently, as proposed, the MPOs would have the
However, these MPO target establishment options would not be available for MPOs subject to the peak hour travel time or the traffic congestion measures because FHWA has proposed that MPOs and the State DOTs subject to these measures establish identical targets. Also those MPO target establishment options would not be available for certain MPOs
As discussed previously, FHWA is proposing that MPOs establish targets for the peak hour travel time and traffic congestion measures for applicable urbanized areas. The FHWA proposes that MPOs, with mainline highways on the Interstate System that cross any part of an urbanized area with a population more than 1 million within its metropolitan planning area boundary, would establish a target for peak-hour travel time for the Interstate System for that urbanized area. Similarly, FHWA proposes that MPOs, with mainline highways on the non-Interstate NHS that cross any part of an urbanized area with a population more than 1 million within its metropolitan planning area boundary, would establish a target for peak-hour travel time for the non-Interstate NHS for that urbanized area.
The FHWA proposes an MPO would establish targets for the traffic congestion measure when mainline highways on the NHS within that MPO's metropolitan planning area boundary cross any part of an urbanized area with a population more than 1 million, and that portion of the metropolitan planning area boundary intersecting the urbanized area also includes a nonattainment or maintenance area for any one of the criteria pollutants, as specified in section 490.703. If an MPO's metropolitan planning area boundary overlaps with an urbanized area where a traffic congestion target is required but that MPO is not required to establish the traffic congestion target, then the MPO should coordinate with relevant State DOT(s) and MPO(s) in the target selection process for the traffic congestion measure. The FHWA is proposing in section 490.105(f)(4) that MPOs would be subject to the same requirements as State DOTs for the establishment of a single peak hour travel time target and a single traffic congestion target. This would require MPOs to establish both 2-year and 4-year targets that would be identical to the targets reported by other State DOTs and MPOs that share in roadway network for the applicable urbanized area. The proposed language is similar to the proposal for State DOT targets for these measures in section 490.105(e)(8). It is possible that an MPO could be required to establish more than 1 peak hour travel time or traffic congestion target if the boundary of the respective metropolitan planning area includes applicable roadways that are in multiple, separate applicable urbanized areas. Based on the data available
In section 490.105(f)(4)(iv), FHWA proposes the same requirements be applied to MPOs for the traffic congestion target as required for State DOTs in sections 490.105(e)(8)(vi)(A) and (e)(8)(vi)(B), which would require only 4-year targets to be established for the first performance period. This will provide additional time needed for MPOs to become more proficient in the management of traffic congestion and for travel time data coverage to be more complete within the NPMRDS. Please see discussion for section 490.105(e)(8)(vi) for more details.
The FHWA proposes in section 490.105(f)(5) MPO target establishment requirements for the proposed on-road mobile source emission measure, identified in section 490.807. The proposed language is similar to the proposal for State DOT targets for these measures in 490.105(e)(9). In section 490.105(f)(5)(i), FHWA proposes that MPOs would establish targets for each applicable criteria pollutant (and precursor (PM
As discussed in section 490.105(e)(9), the MPOs would adhere to the Federal fiscal year based performance periods for the on-road mobile source emissions targets. In paragraph (ii) of this section, FHWA proposes that the MPOs would establish targets as discussed in section 490.105(e)(9)(iii).
In section 490.105(f)(5)(iii), FHWA proposes that if any part of the nonattainment or maintenance area within a metropolitan planning area for any one of the applicable criteria pollutants is located within the boundary of an urbanized area with a population more than 1 million in population, then that MPO would establish both 2-year and 4-year targets for its metropolitan planning area.
In section 490.105(f)(5)(iv), FHWA proposes that a nonattainment or maintenance area within a metropolitan planning area for any one of the applicable criteria pollutants is not located within the boundary of an urbanized area with a population more than 1 million in population, then that MPO would not be required to establish a 2-year target and would only establish both 4-year targets for its metropolitan planning area as required in section 490.105(f)(3).
In section 490.105(f)(5)(v) and (f)(5)(vi), FHWA proposes the same requirements be applied to MPOs for the on-road mobile source emission target as required for State DOTs in sections 490.105(e)(9)(v) and (e)(9)(vi). In section 490.105(f)(5)(vii), FHWA proposes language for the MPOs that is similar to
As discussed in section 490.105(e)(9), both traffic congestion and on-road mobile source emission measures are proposed to carry out the CMAQ Program, but there are some differences in how the targets for the measures are to be implemented. Please refer to the discussion for section 490.105(e)(9) for a summary of differences.
As stated in the section 490.105(e)(6) discussion, State DOTs may adjust their established 4-year targets when they submit their State Biennial Performance Report just after the midpoint of the performance period (
As with State DOTs, FHWA recognizes that MPOs would need to consider many factors in establishing targets, such as uncertainties in funding, changing priorities, and external factors outside the control of the MPO. Thus, FHWA proposes in section 490.105(f)(8) that MPOs may adjust their established 4-year target in a manner that is consistent with the process MPOs and State DOTs agreed upon. The FHWA recognizes that for many MPOs the establishment of targets, especially for the first performance period, would be new and challenging and that there may be a need to revisit targets during the 4-year performance period. The FHWA requires State DOTs and MPOs to coordinate with each other throughout the performance period with respect to any target adjustments so their targets are consistent to the maximum extent practicable.
In section 490.105(f), FHWA proposes that the method by which MPOs would report their established baseline condition/performance, targets, and progress toward achieving targets would be as specified in section 490.107(c). The FHWA further proposes in 490.105(f)(8) that the State would be able to provide MPO targets to FHWA on request after targets are established or adjusted by MPOs within the State. The FHWA believes that, through the coordination between a State DOT and relevant MPOs, the reporting on MPO progress can be shared between these two entities. However, FHWA expects to be able to request from a State DOT the MPO targets and reports on progress, as needed, to better understand performance expectations and outcomes in urbanized areas across the country. The State DOT and MPO would document the target establishment reporting process. The FHWA encourages State DOTs to work with multiple MPOs to mutually agree on a process for reporting that would provide a sufficient level of consistency to understand performance in urbanized areas collectively across the State.
Proposed reporting requirements for measures identified in section 490.207(a) are discussed in section 490.213 of the first performance management NPRM; and performance target reporting requirements specific to pavement condition measures in sections 490.307(a)(1) through (c)(4) and bridge condition measures in sections 490.407(c)(1) and (c)(2) are included in the second performance management NPRM. The discussions specific to those measures will not be repeated in this NPRM. Please see the docket for proposed Subpart A in its entirety for additional information.
Pursuant to 23 U.S.C. 150(e), State DOTs are required to submit reports on performance targets and progress in achieving established targets to FHWA not later than October 1, 2016, and every 2 years thereafter. The FHWA evaluated whether there were any existing reports that could be used to meet these 23 U.S.C. 150(e) reporting requirements. For the non-HSIP related measures, FHWA determined that none of the existing reporting requirements met the statutorily required timing. In addition, none of the existing reports currently provide the consistency needed to implement performance management nationally. For these reasons, FHWA proposes a new biennial report to meet the statutory requirements.
The FHWA proposes in section 490.107 for State DOT performance reporting to be used:
• In the determination of significant progress toward achieving NHPP and NHFP targets;
• to provide some of the information needed for FHWA to report to Congress on the performance-based planning process evaluation of each State DOT as required by 23 U.S.C. 135(h);
• to understand performance needs, expectations, and progress at a State, regional, and national level; and
• to provide for transparency by communicating the content of the report to the public on an externally facing Web site in a downloadable format.
In section 490.107, FHWA proposes the minimum requirements that State DOTs and MPOs would follow to report targets for all measures identified in section 490.105(c), which include the proposed measures in both this performance management NPRM and the second performance management NPRM. In section 490.107(a), FHWA proposes that all performance targets described in section 490.105 would be subject to biennial performance reporting in this section. However, reporting on performance targets for carrying out the HSIP would be in accordance with section 490.213. In the first performance measure rulemaking, published as a final rule on March 15, 2016, FHWA requires a 1 calendar year period as the basis for measurement, target establishment, and reporting. As discussed in section 490.101 of that Rule, a 1-year period is required to align the safety measures with the requirements for the common measures reported as a requirement of 23 U.S.C. 402. The FHWA also proposes that State DOTs use an electronic template to deliver the report proposed in section 490.107(a)(3). The FHWA intends to provide additional guidance regarding the template which will include fields to capture all of the information that
The FHWA anticipates the final rule for the pavement and bridge condition performance measures (proposed in the second performance management NPRM) to be effective no later than October 1, 2016, and anticipates that the final rule for this proposal to be effective no later than October 1, 2017. However, 23 U.S.C. 150(e) requires State DOTs to submit reports on performance targets and progress in achieving established targets to FHWA not later than October 1, 2016. To meet the statutory deadlines for the first State DOT performance report due in 2016, FHWA proposes the minimum reporting requirements that would be followed by State DOTs in section 490.107(a)(4). The FHWA proposes that State DOTs would submit an Initial State Performance Report to FHWA by October 1, 2016. In that report, the State DOTs shall include: (1) The condition/performance of the NHS in the State derived only from the available data in HPMS and NBI; (2) the effectiveness of the investment strategy document in the State asset management plan for the NHS; (3) progress toward targets the State DOT would be required to establish, which may only be a description of how State DOTs would coordinate with relevant MPOs and other agencies in target selection for the targets to be reported in the first State Biennial Performance Report in 2018; and (4) the ways in which the State is addressing congestion at freight bottlenecks.
Pursuant to 23 U.S.C. 150(d)(1), FHWA proposes in section 490.107(a)(5) that State DOTs would establish targets within 1 year of the effective date of applicable rule and the State DOTs would report the initial targets to FHWA. In this section, FHWA proposes that State DOTs submit their 2-year and 4-year targets for the first performance period to FHWA either within 30 days of target establishment by amending the Initial State Performance Report or on the due date of the first Baseline Performance Report, whichever comes first. The related NPRMs are being published on individual schedules. This creates the possibility that State DOTs will be required to establish targets for some performance measures, such as those published in the second performance management NPRM, well before the first Baseline Performance Report is due in October 2018. This proposal ensures timely reporting of targets, and allows FHWA to begin to develop a national story around targets sooner.
For consistent State DOT and FHWA reporting, FHWA proposes a 4-year performance period in section 490.105(e)(4). The FHWA recognizes the need for uniform data collection timing in order to ensure consistency in reporting and repeatable target establishment and progress evaluation processes. Thus, in subsequent sections, FHWA proposes the timing of data collection based on the specified performance periods, described in section 490.105(e)(4). The FHWA proposes that data collection requirements for the established measures support the reporting requirements in this section and be in accordance with the respective Data Requirements section for each measure (see section 490.103). To ensure consistency in reporting, FHWA proposes that the reported baseline condition/performance be derived from the latest data collected through the beginning date of a performance period, the reported actual 2-year condition/performance be derived from the latest data collected through the midpoint of a performance period, and the reported actual 4-year condition/performance be derived from the latest data collected through the end date of a performance period. This is illustrated in Figures 1 and 2 in the discussion for section 490.105(e)(4).
The FHWA proposes in section 490.107(b) that State DOTs submit to FHWA three types of Biennial Performance Reports: Baseline Performance Period Report, Mid Performance Period Progress Report and Full Performance Period Progress Report. The FHWA proposes to make a distinction between the three reports to emphasize the differences in content while aligning the reporting process to the proposed target establishment, progress evaluation, and other performance reporting requirements. Figures 3-5 illustrate the proposed reporting timelines for the three types of Biennial Performance Reports. The proposed requirements identify three distinct biennial performance reports (baseline, mid, and full) and State DOTs will be expected to provide information for at least one of these reports every 2 years. Because these reports would be required for consecutive 4-year performance periods, the information provided in the Full Performance Period Report would be provided at the same time and may include some of the same information as the Baseline Performance Period Report for the next performance period. As discussed previously, FHWA is proposing to provide for an electronic template that State DOTs would use to capture the information required in each of the three reports discussed in section 490.107(b). It is envisioned that this electronic template would provide the State DOT all of the relevant fields for the information that would be due at the corresponding 2-year point. This approach would allow State DOTs to provide all of the required baseline and progress reporting information at one time. The proposed regulations identify three distinct reports to clarify the purpose and timing of information that would be required to be reported every 2 years.
The FHWA proposes the requirement for the Baseline Performance Period Report in section 490.107(b)(1), where the State DOTs would be required to submit a Baseline Performance Period Report no later than October 1st of the first year of a performance period. The FHWA is proposing that the first performance period would begin on January 1, 2018, for the measures identified in section 490.105(c)(1) through (c)(7) and would begin on October 1, 2017, for emission measure identified in section 490.105(c)(8). Although the performance periods may be different, the reporting for all the measures in 490.105(c) would follow the same schedule. State DOTs would submit their Initial State Performance Report no later than October 1, 2018. Subsequent Baseline Performance Period Reports would be due no later than October 1st every 4 years thereafter.
The required contents for the Baseline Performance Period Report are discussed in section 490.107(b)(1)(ii). The FHWA is proposing that the Baseline Performance Period Report would be the official source of the non-
Although FHWA would not approve the State DOT submitted targets, a discussion of the basis for each established target would be included in the Baseline Performance Period Report. The FHWA believes that this discussion is needed to explain the State DOT's basis for the selection of a target. The FHWA intends to publish the State DOT established targets on a publicly available Web site along with the State DOT's discussion of the basis for each target selection. Although other MAP-21 required plans and reports may discuss and use targets, FHWA is proposing that only the targets reported in the Baseline Performance Period Report and the HSIP report would be used by FHWA in carrying out the requirements of 23 CFR 490, as they are the targets established by the State DOT to meet the requirements of 23 U.S.C. 150(d).
The FHWA proposes in section 490.107(b)(1)(ii)(B) that the State DOTs report baseline condition/performance associated with each target reported to represent the latest condition/performance data collected through the beginning date of a performance period. Because the first performance period for the measures in section 490.105(c)(1) through (c)(7) is proposed to begin on January 1, 2018, the baseline condition/performance for this performance period would be the most recent condition/performance that represents actual condition/performance through December 31, 2017. As the first performance period for the on-road mobile source emissions measure in section 490.105(c)(8) is proposed to begin on October 1, 2017, State DOTs would establish baseline performance of a 4-year cumulative emissions reduction resulting from CMAQ projects from fiscal year 2014 through fiscal year 2017 (ending September 30, 2017) in the CMAQ Public Access System, as described in section 490.809. The CMAQ Public Access System contains 20 years of past data. Since all past data in the CMAQ Public Access System may not have the necessary values for the proposed measure, FHWA believes that State DOTs should revisit the data for CMAQ projects from fiscal year 2014 through fiscal year 2017 to improve baseline performance establishment which would ultimately help the State DOTs in their target establishment. Should a State DOT elect to establish additional targets, as described in sections 490.105(e)(3) and 490.105(e)(9)(iv), the State DOT would report baseline condition/performance that represent the applicable areas in addition to the statewide baseline condition/performance. As an example, for the Percent of the Interstate System providing for Reliable Travel Times measure (in section 490.507(a)(1)), would be a percentage of directional mainline highways on the Interstate System providing for Reliable Travel Times (sections 490.503(a)(1) and 490.513(b)) expressed in one tenth of a percent. Thus, FHWA proposes that a baseline condition/performance for this measure would be a percentage of directional mainline highways on the Interstate System providing for Reliable Travel Times expressed in one tenth of a percent. As a hypothetical example, a baseline condition/performance would be 37.7 percent for the proposed measure Percent of the Interstate System providing for Reliable Travel Times.
The FHWA proposes in section 490.107(b)(1)(ii)(C) that State DOTs would be required to also include a discussion in the Baseline Performance Period Report, of how the established 2-year and 4-year targets support longer term performance expectations in other performance-related plans, such as the State asset management plan and the long-range statewide transportation plan.
The FHWA proposes in section 490.107(b)(1)(ii)(D) that State DOTs would be required to report the geographic boundaries and Decennial Census population data used to determine target scope and establish any additional targets for urbanized and non-urbanized areas. Similarly, in section 490.107(b)(1)(ii)(E), FHWA proposes that State DOTs would be required to report the NHS network limits used for target establishment. The State DOT would report both the urbanized area boundaries and NHS limits used for target establishment by identifying the corresponding data inventory year of the HPMS that includes this information. Additionally, State DOTs would be required to report the latest Decennial population data for all urbanized areas in accordance with HPMS Field Manual. The FHWA would use this information in determining measure applicability and making its progress determinations in future years. It is the State's responsibility to ensure that the data entered into HPMS reflects the information that is used for target establishment.
The FHWA proposes in section 490.107(b)(1)(ii)(F) that, in each Baseline Performance Period Report, State DOTs would include discussions on the ways in which State DOTs are addressing congestion at freight bottlenecks, including those identified in the National Freight Strategic Plan. This content is required as part of the report under 23 U.S.C. 150(e)(4). To meet this requirement for State DOTs to address congestion at freight bottlenecks within the State, FHWA proposes that State DOTs would describe their activities to improve freight bottlenecks. For the purpose of this report only, freight bottlenecks would be defined as the segments of the Interstate System not meeting thresholds for freight reliability and congestion (section 490.613) and any other locations the State wishes to identify as bottlenecks based on its own freight plans or related documents if applicable. Further, the State DOT should reference its activities in other freight planning and programs that focus on improving freight bottlenecks, including: Comprehensive freight improvement efforts of Statewide Freight Planning or MPO freight plans; the Statewide Transportation Improvement Program (STIP) and TIP; regional or corridor level efforts; other related planning efforts; and operational and capital activities targeted to improve freight movement on the Interstate. The FHWA understands the multifaceted and multimodal nature of a freight bottleneck and that many State DOTs will likely define bottlenecks beyond the definition for this Part. The FHWA believes that due to the diversity in characteristics of bottlenecks and a lack of a universal definition or approach to measurement, this reporting on freight bottlenecks should be focused at a minimum on the performance measures, as proposed in section 490.607 and how those measures and the State DOT's associated targets might be impacted by other freight efforts currently underway, such as planning or programming. The FHWA encourages State DOTs to consider multimodal freight performance in transportation planning and programming efforts taking place beyond this rule. Upon development of the National Strategic Freight Plan, a State DOT shall specifically include its activities for addressing freight bottlenecks as part of that Plan in this report. The FHWA is seeking comment on this approach.
The FHWA proposes in section 490.107(b)(1)(ii)(G) that State DOTs, where applicable, would be required to describe the boundaries of EPA's designation of nonattainment or maintenance areas under the NAAQS in 40 CFR part 81 at the time when the State DOT Baseline Performance Period Report is due to FHWA. Please refer to the discussion in section 490.103(c) for more information.
As discussed in section 490.107(c)(3), MPOs serving a TMA with a population over 1 million representing nonattainment and maintenance areas for O
The FHWA proposes the requirement for the Mid Performance Period Progress Report in section 490.107(b)(2). In section 490.107(b)(2)(i), FHWA proposes that State DOTs would be required to submit a Mid Performance Period Progress Report no later than October 1st of the third year of a performance period. The FHWA is proposing that the first performance period would begin on January 1, 2018, for the measures identified in section 490.105(c)(1) through (c)(7) and would begin on October 1, 2017, for the emission measure identified in section 490.105(c)(8). Although the performance periods may be different, the reporting for all the measures in section 490.105(c) would follow the same schedule. State DOTs would submit their first Mid Performance Period Progress Report no later than October 1, 2020, and subsequent Mid Performance Period Progress Reports would be due no later than October 1st every 4 years thereafter.
In section 490.107(b)(2)(ii), FHWA proposes the required contents for the Mid Performance Period Progress Report. In section 490.107(b)(2)(ii)(A), FHWA proposes that State DOTs would be required to report 2-year condition/performance in each Mid Performance Period Progress Report. As exhibited in Figure 4, FHWA proposes that the 2-year condition/performance would be reported to represent the actual condition/performance derived from the latest measured condition/performance through the midpoint of a performance period. Considering the first performance period is proposed to begin on January 1, 2018, for the measures identified in section 490.105(c)(1) through (c)(7), 2-year condition/performance for this performance period would be the most recent conditions/performance that represents actual conditions/performance through December 31, 2019, (illustrated in Figure 4). As defined in section 490.101, a target is a numeric value that represents a quantifiable level of condition/performance in an expression defined by a measure. The FHWA proposes that a target would be a single numeric value representing the intended or anticipated condition/performance level at a specific point in time. For example, the proposed measure, Percent of the Interstate System providing for Reliable Travel Times measure (in section 490.507(a)(1)), would be a percentage of directional mainline highways on the Interstate System providing for Reliable Travel Times (sections 490.503(a)(1) and 490.513(b)) expressed in one tenth of a percent. Thus, FHWA proposes that a target for this measure would be a percentage of directional mainline highways on the Interstate System providing for Reliable Travel Times expressed in one tenth of a percent. As a hypothetical example, a 2-year target for that measure would be 39.5 percent. The 2-year condition/performance would be 39.2 percent. For the on-road mobile emissions measure identified in section 490.105(c)(8), 2-year condition/performance for this performance period would be the estimated cumulative emissions reduction resulting from CMAQ projects from fiscal year 2018 through fiscal year 2019 in the CMAQ Public Access System, as described in section 490.809.
The FHWA proposes in section 490.107(b)(2)(ii)(B) that State DOTs would also include a discussion of progress made toward the achievement of 2-year targets established for the current performance period. In this discussion, State DOTs would present a comparison of 2-year condition/performance with the 2-year targets that were established for the performance period. For example, in the first Mid Performance Period Progress Report in 2020, a State would compare the actual condition/performance through 2019 with the 2-year targets established for the first performance period and discuss why targets were or were not achieved. This discussion could describe accomplishments achieved, planned activities, circumstances that led to actual conditions/performance, or any other information that State DOT feel would adequately explain progress. Although this explanation would not be used to determine significant progress, as described in section 490.109, this information would be made available to the public to provide an opportunity for the State DOT to discuss actual outcomes achieved. As an example, for the Percent of the Interstate System providing for Reliable Travel Times measure (in section 490.507(a)(1)), a hypothetical 2-year target for this measure is 39.5 percent (in section 490.105(e)). If 2-year condition/performance for this measure is 39.2 percent as discussed above, the State DOT would discuss why this target was not achieved in its Mid Performance Period Progress Report.
The FHWA proposes in sections 490.107(b)(2)(ii)(C) and (D) that, in each Mid Performance Period Progress Report, State DOTs would include discussions on the effectiveness of the investment strategy documented in the State asset management plan for the NHS and the ways in which State DOTs are addressing congestion at freight bottlenecks, including those identified in the National Freight Strategic Plan, as described in section 490.107(b)(1)(ii)(F). This content is required as part of the report under 23 U.S.C. 150(e)(2) and (4). The FHWA recognizes that the Mid Performance Period Progress Report for the first performance period may be impacted by the timing of the implementation of the new NHS asset management plan requirement and the development of a final National Freight Strategic Plan. The FHWA intends to issue further guidance if the timing of these two plans would impact a State DOT's ability to comply with the requirements proposed in sections 490.107(b)(2)(ii)(C) and (D).
As discussed in section 490.105(e)(6), FHWA recognizes the challenges that State DOTs may face in target establishment and proposes to allow State DOTs to adjust their 4-year targets. The FHWA is proposing in section 490.107(b)(2)(ii)(E) that State DOTs would report any adjustments to their 4-year targets in the Mid Performance Period Progress Report. The FHWA proposes that this target adjustment allowance would be limited to this specific report and not allowed prior to, or following, the submittal of the Mid Performance Period Progress Report. For example, if a State DOT elects to adjust a 4-year target established in its first Baseline Performance Period Report in 2018, the State DOT would only be able to adjust the 4-year target in its Mid Performance Period Progress Report in 2020. In addition to reporting the adjusted 4-year target, the State DOT would be required to include a discussion on the basis for the adjusted 4-year target(s) for the performance period and a discussion on how the adjusted targets support expectations documented in longer range plans, such as the State asset management plan and the long-range statewide transportation plan. The FHWA intends to publish the State DOT established targets on a publicly available Web site with the initial target basis discussion. Any targets adjusted at the mid-point will also be reflected on the site.
The FAST Act introduced 23 U.S.C. 167(j), which requires FHWA to determine if a State has met or made significant progress toward meeting the performance targets related to freight movement. This was not part of MAP-21. To meet the requirements of the FAST Act, FHWA has incorporated language throughout this NPRM requiring the targets established for the measures in section 490.105(c)(6) to be included in the significant progress process. The FHWA has called these the NHFP targets. Section
In section 490.107(b)(2)(ii)(F), FHWA proposes that the State DOTs would discuss the progress they have made toward the achievement of the 2-year targets reported in the current Baseline Performance Period Report that would had been established for the NHPP measures specified in sections 490.105(c)(1) through (c)(5) and the NHFP measures in section 490.105(c)(6). Additionally, State DOTs would provide information to discuss how the actual 2-year condition/performance levels compare to targets. Although this discussion would not be used to determine significant progress for the applicable measures, this information would be made available to the public to provide an opportunity for the State DOT to discuss actual outcomes related to the NHPP and NHFP. For example, the State DOT may use this discussion to explain how it effectively and efficiently delivered a program designed to achieve 2-year targets, how this may have resulted in actual condition/performance improvements for the NHPP and NHFP, and how the State DOT would deliver a program to make significant progress for 4-year targets for the NHPP and NHFP.
In section 490.107(b)(2)(ii)(G), FHWA is proposing that a State DOT would report any factors that it could not have foreseen and were outside of its control that impacted its ability to make significant progress for the 2-year targets for the NHPP or NHFP. The FHWA would use this discussion when considering extenuating circumstances discussed in section 490.109(e)(4).
In section 490.107(b)(2)(ii)(H), FHWA proposes that if FHWA determines that a State DOT has not made significant progress toward the achievement of any NHPP or NHFP targets in a biennial FHWA determination, then the State DOT would include a description of the actions it will undertake to achieve those targets as required, respectively, under 23 U.S.C. 119(e)(7) or 167(j).
For example, for the NHPP or the NHFP, if FHWA determines that a State DOT has not made significant progress (as provided in section 490.109(e)(2)) for either the 2-year or 4-year significant progress determination, then the State DOT would include a description of the actions it would undertake to achieve its conditions/performance with respect to all related measures (section 490.109(f)) in its next Biennial Progress Report. If FHWA determines that the State DOT has achieved the target or made significant progress, then the State DOT does not need to include such description in the next Biennial Progress Report.
For the NHPP targets, the FAST Act amended the language in MAP-21, and changed the determination period from being based on looking back over “two consecutive determinations” (a 4-year period) to a single biennial FHWA determination which looks back over a 2-year period. This is a change from the language presented in the second NPRM, but it is required to be consistent with the amended statute.
As discussed in section 490.107(c)(3), MPOs serving a TMA with a population over 1 million representing nonattainment and maintenance areas for O
The FHWA proposes the requirement for the Full Performance Period Progress Report in section 490.107(b)(3). In section 490.107(b)(3)(i), FHWA proposes that State DOTs be required to submit a Full Performance Period Progress Report no later than October 1st of the first year following the completion of a performance period. The FHWA is proposing that the first performance period would begin on January 1, 2018, for the measures identified in section 490.105(c)(1) through (c)(7) and would begin on October 1, 2017, for emission measure identified in section 490.105(c)(8). Although the performance periods may be different, the reporting for all the measures in section 490.105(c) would follow the same schedule. State DOTs would submit their first Full Performance Period Progress Report no later than October 1, 2022, and subsequent Full Performance Period Progress Reports would be due no later than October 1st every 4 years thereafter.
In section 490.107(b)(3)(ii), FHWA proposes the required contents for Full Performance Period Progress Report.
In section 490.107(b)(3)(ii)(A), FHWA proposes that State DOTs would be required to report 4-year condition/
As an example, for the Percent of the Interstate System providing for Reliable Travel Times measure (in section 490.507(a)(1)), an hypothetical 4-year target for this measure is 38.5 percent (in section 490.105(e)). If 4-year condition/performance for this measure is 37.7 percent as discussed above, the State DOT would discuss why this target was not achieved in their Full Performance Period Progress Report.
The FHWA proposes in section 490.107(b)(3)(ii)(B) that the State DOTs would also include a discussion of progress made toward the achievement of 4-year targets established for the relevant performance period. In this discussion, State DOTs would present a comparison of 4-year condition/performance with the 4-year targets that were established for the performance period. For example, in the first Full Performance Period Progress Report in 2022, a State DOT would compare the actual condition/performance through the end of the performance period with the 4-year targets established for the first performance period and discuss why targets were or were not achieved. This discussion could describe accomplishments achieved, planned activities, circumstances that led to actual conditions/performance or any other information that State DOT would feel would adequately explain progress. Although this explanation would not be used in the determination of significant progress, this information would be made available to the public to provide an opportunity for the State DOT to discuss actual outcomes achieved.
As discussed in sections 490.107(b)(2)(ii)(C) and (D) for the Mid Performance Period Progress Report, FHWA also proposes in sections 490.107(b)(3)(ii)(C) and (D) that in each Full Performance Period Progress Report, State DOTs would include discussions on the effectiveness of the investment strategy documented in their State asset management plans for the NHS and the ways in which State DOTs are addressing congestion at freight bottlenecks, including those identified in the National Freight Strategic Plan, as described in section 490.107(b)(1)(ii)(F). Please refer to the discussion of sections 490.107(b)(1)(ii)(F), 490.107(b)(2)(ii)(C) and (ii)(D) for more information.
In section 490.107(b)(3)(ii)(E), FHWA proposes that the State DOTs would discuss the progress they have made toward the achievement of the 4-year targets reported in the current Baseline Performance Period Report, or adjusted in the current Mid Performance Period Progress Report, that would have been established for the NHPP measures specified in sections 490.105(c)(1) through (c)(5) and the NHFP measures specified in section 490.105(c)(6). Additionally, State DOTs would provide information to discuss how the actual 4-year condition/performance levels compare with the applicable NHPP or NHFP targets. Although this discussion would not be used in the determination of significant progress for the applicable measures, this information would be made available to the public to provide an opportunity for the State DOT to discuss actual outcomes related to the NHPP and NHFP. For example, the State DOT may use this discussion to explain how it effectively and efficiently delivered a program designed to achieve targets and how this may have resulted in actual condition/performance improvements for the NHPP and NHFP.
In section 490.107(b)(3)(ii)(F), FHWA is proposing that a State DOT would report any factors that it could not have foreseen and were outside of its control that impacted its ability to make significant progress for the NHPP or NHFP 4-year targets. This discussion would be used by FHWA to consider the application of the proposed consideration of extenuating circumstances discussed in section 490.109(e)(4).
In section 490.107(b)(3)(ii)(G), FHWA proposes that if FHWA determines that a State DOT has not made significant progress toward the achievement of any NHPP or NHFP targets, then the State DOT would include a description of the actions it would undertake to achieve conditions/performances with respect to all related NHPP or NHFP measures within the measure group, as described in section 490.109(f).
For example, for the NHPP or NHFP, if FHWA determines that a State DOT has not made significant progress at either the 2-year or 4-year significant progress determination, then the State DOT would include a description of the actions it would undertake to achieve its targets with respect to all related measures in the next Biennial Progress Report. If FHWA determines that the State DOT has achieved or made significant progress, then the State DOT does not need to include this description in the next Biennial Progress Report.
As discussed in section 490.107(c)(3), MPOs serving a TMA with a population over one million representing nonattainment and maintenance areas for O
The FHWA proposes, in section 490.107(c), that MPOs document the manner in which they report their established targets. The MPOs would report their established targets to the relevant State DOTs in a manner that is agreed upon by both parties and documented. The FHWA proposes in section 490.105(e)(5), that MPOs would report targets to the State DOT in a manner that would allow the State DOT to provide FHWA, upon request, all of the targets established by relevant MPOs. In section 490.107(c)(2), FHWA also proposes that MPOs would report baseline condition/performance, and progress toward the achievement of their targets, in the system performance report in the metropolitan transportation plan, in accordance with 23 CFR 450. In sections 490.105(e)(3) and 490.105(d)(3), FHWA discusses how an urbanized area boundary or NHS limit changes during a performance period may lead to changes in the measures reported for an area/network and could impact how an established target relates to actual measured performance. The FHWA anticipates that changes in the MPA boundary could also impact how an established target relates to actual measured performance. Thus, FHWA
As required in 23 U.S.C. 149(l), each MPO serving a TMA with a population over 1 million representing nonattainment and maintenance areas must develop a performance plan, updated biennially, to report baseline levels and the progress toward achievement of the targets for the CMAQ traffic congestion and on-road mobile source emissions measures. The FHWA proposes that the CMAQ performance plan is not required when the MPO does not serve a TMA with a population over 1 million; the MPO is attainment for O
To encourage close coordination of the State DOT and MPOs in implementing the performance requirements and to streamline the reporting requirements, FHWA proposes in section 490.107(c)(3) that the MPOs meet the reporting requirements of the CMAQ performance plan in 23 U.S.C. 149(l) if the MPO's CMAQ performance plan is submitted as part of the State Biennial Performance Report as required under section 490.107(b). The CMAQ performance plan must be clearly documented in a separate section, as an attachment, of the State Biennial Performance Report. The FHWA is soliciting comments on other ways that will help further streamline the reporting requirements. Some options may include:
1. The MPOs could submit their CMAQ performance plans to FHWA separately from the State Biennial Performance Report as discussed in section 490.107(b). In this case, the State DOTs and the MPOs should coordinate to ensure that the MPOs' data are reflected in the State report in a consistent manner.
2. The MPOs could submit their performance information to the State DOTs to be included in the State Biennial Performance Report. In this case, the State DOTs would be responsible to ensure the CMAQ performance plan requirements are met.
The FHWA requests comments on other possible options that provide a streamlined approach to meet the performance requirements as discussed above.
The FHWA proposes that, similar to the State DOT Biennial Performance Reports, an MPO would have three distinct performance reports (Baseline Performance Period, Mid Performance Period Progress, and Full Performance Period Progress). These distinct reports would contain different content, but would align with target establishment and other State DOT performance reporting requirements.
As part of the CMAQ performance plan submitted with the State DOT's Baseline Performance Period Report, the MPO would include baseline condition/performance for each applicable measure. This could result in several different baseline condition/performances: One for each urbanized area's traffic congestion measure and up to five
The report would also include the 2-year and 4-year targets for these measures for the performance period. The establishment of targets is required in section 490.105(f). An MPO would use the same geographic area for both reporting its baseline condition/performance and establishing targets. For the traffic congestion measure, as described in section 490.105(f)(5), 2-year and 4-year targets would be identical to the targets reported by the relevant State DOT(s) under section 490.107(b)(1)(ii)(A). As required by 23 U.S.C. 149(l)(1)(C), the report would describe projects identified for CMAQ funding and how such projects would contribute to achieving the performance targets for the traffic congestion and on-road mobile source emissions measures.
The FHWA proposes that the CMAQ performance plan submitted with the State DOT's Mid Performance Period Progress Report would include the actual 2-year condition/performance derived from the latest measured condition/performance through the midpoint of the performance period for an MPO-reported traffic congestion target and the estimated cumulative emissions reduction resulting from CMAQ projects in the CMAQ Public Access System for each MPO-reported on-road mobile source emissions target. For the traffic congestion measure, the actual 2-year condition/performance would be identical to the 2-year condition/performance reported by the relevant State DOT(s) under section 490.107(b)(2)(ii)(A). For the on-road mobile source emissions measure, an MPO should use the same process the State DOT uses for determining the actual condition/performance, which is described in relation to section 490.107(b)(2)(ii). As required by 23 U.S.C. 149(l)(2), MPOs would assess the progress of the projects identified in the CMAQ performance plan submitted with the Baseline Performance Period Report toward achieving the 2-year targets for traffic congestion and on-road mobile source emissions measures. When doing this assessment, the MPO would compare the actual 2-year condition/performance with the 2-year target and document any reasons for differences between these two values.
If an MPO adjusts its 4-year target, the MPO would report that adjusted target, as provided in section 490.105(f)(7) and (f)(8). In addition, an MPO would update its description of projects identified for CMAQ funding and how those updates would contribute to achieving the performance targets for these measures. If an MPO has not adjusted its targets or does not have any changes to its description of projects, it may comply with this proposed requirement by making a statement to that effect.
The FHWA proposes the CMAQ performance plan submitted with the State DOT's Full Performance Period Progress Report would include the actual 4-year condition/performance derived from the latest measured condition/performance through the end of the performance period for each MPO-reported traffic congestion and estimated cumulative emissions reductions resulting from CMAQ projects in the CMAQ Public Access System for each MPO reported on-road
The FHWA has proposed that MPOs submit three distinct CMAQ performance plans with the State DOT's biennial performance reports (Baseline Performance Period, Mid Performance Period Progress, and Full Performance Period Progress). Because these plans would be required for consecutive 4-year performance periods, the information provided in the CMAQ performance plan submitted with the State DOT's Full Performance Period Report would be provided at the same time and may include some of the same information as the CMAQ performance plan submitted with the State DOT's Baseline Performance Period Report for the next performance period. As FHWA expects that State DOTs would provide all of the required baseline and progress reporting information at one time, and the MPO CMAQ performance plan would be submitted in a similar fashion. The proposed regulations identify three distinct plans to clarify the purpose and timing of information that would be required to be reported every 2 years. The FHWA intends to issue guidance to assist MPOs in developing and submitting these biennial plans.
The FHWA also seeks comments on other issues or problems State DOTs and MPOs might anticipate in meeting the reporting requirements of 23 U.S.C. 149(l) and 150(e) for the performance measures related to the CMAQ program and ideas for resolving any anticipated issues or problems.
Significant progress determinations for measures identified in section 490.207(a) are discussed in section 490.211 of the first performance measure rulemaking, published as a final rule March 15, 2016; and significant progress determination specific to pavement condition measures in sections 490.307(a)(1) through (c)(4) and bridge condition measures in sections 490.407(c)(1) and (c)(2) are included in the second performance measure NPRM. The discussions specific to these measures will not be repeated in this NPRM. Please see the docket for Subpart A in its entirety for additional information.
In section 490.109, FHWA proposes the method by which FHWA would determine if a State DOT has achieved or is making significant progress toward its performance targets in the NHPP, as required by 23 U.S.C. 119(e)(7), and NHFP, as required 23 U.S.C. 167(j). This determination would involve the measures identified in section 490.105(c)(1) through (c)(5), which include the proposed measures in both this performance management NPRM and the second performance management NPRM, and section 490.105(c)(6). Although this determination could directly impact State DOTs, MPOs could also be indirectly impacted as a result of the link between metropolitan and statewide planning and programming decisionmaking. This rulemaking discusses the approach that would be taken by FHWA to assess State DOT performance progress, but does not include a discussion on the method that may be used by FHWA to assess the performance progress of MPOs. Interested persons should refer to the updates to the Statewide and Metropolitan Planning regulations (RIN 2125-AF52) for discussion on the review of MPO performance progress.
The FHWA recognizes that there may be factors outside of a State DOT's control that could impact its ability to achieve a target. The FHWA considered these factors in its evaluation of different approaches to implement this provision. A number of factors were raised as part of the performance management stakeholder outreach sessions regarding target establishment and progress assessment, including: The impact of funding availability on performance outcomes, the reliability of the current state-of-practice to predict outcomes resulting from investments at a system level, the impact of uncertain events or events outside the control of a State DOT on performance outcomes, the need to consider multiple performance priorities in making investment trade-off decisions, and the challenges with balancing local and national objectives.
The FHWA recognizes that the State DOTs and MPOs have to consider multiple performance priorities in making investment trade-off decisions and that there are challenges with balancing local and national objectives. During outreach, stakeholders
• The desire to foster balanced and sound decisions rather than focusing on achieving one target at the expense of another;
• the desire to assess progress using quantitative and qualitative input; and
• the desire to avoid unachievable targets.
Thus, FHWA plans to implement an approach that balances the uncertainty facing State DOTs in predicting future performance with the need to provide for a fair and consistent process to determine compliance. The approach being proposed by FHWA is based on the following principles:
• Focus the Federal-aid highway program on the MAP-21 national goals in 23 U.S.C. 150(b); and
• recognize that State DOTs need to consider fiscal constraints in their target establishment.
Because targets would be established for an entire system, FHWA acknowledges that State DOTs may make small incremental changes within that system that would not necessarily appear in a quantitative assessment. In some instances, even a modest increase in improvement when evaluating on a system-wide basis, would constitute significant progress. Accordingly, FHWA proposes that for each NHPP target (targets for the measures identified in section 490.105(c)(1) through (c)(5)) and each NHFP (targets for the measures identified in section 490.105(c)(6)), progress toward the achievement of the target would be considered “significant” when either of the following occur: The actual condition/performance level is equal to or better than the State DOT established target, or the actual condition/
The FHWA believes that State DOTs, through a transparent and public process, would want to establish or adjust targets that strive to improve the overall performance of the NHS and freight movement. For this reason, FHWA did not want to propose an approach to determine significant progress that would be difficult to meet, as it could discourage the establishment of “reach” targets due to the perceived uncertainties that would need to be assumed by State DOTs. The FHWA feels that the progress assessment approach proposed in this NPRM, which considers improvement from baseline conditions to be significant, would not discourage State DOTs from establishing targets to improve the overall condition/performance of the Interstate and non-Interstate System NHS, and freight movement.
The FHWA is proposing a three-step process to determine if a State DOT has made significant progress toward the achievement of its NHPP and NHFP targets. The FHWA would use this process to make a significant progress determination for the NHPP and NHFP each time the State DOT submits its Mid Performance Period Progress Report and its Full Performance Period Progress Report. This process is summarized below and discussed in more detail for each of the proposed regulations.
• Step 1:
• Step 2:
• Step 3:
○ Data contained within the HPMS for targets established for pavement condition measures, as specified in sections 490.105(c)(1) and (c)(2);
○ Data contained in the NBI for targets established for bridge condition measures, as specified in section 490.105(c)(3);
○ Data contained within the HPMS for targets established for system performance measures, as specified in sections 490.105(c)(4) and (c)(5);
○ Data contained within the HPMS for targets established for Freight performance measures, as specified in sections 490.105(c)(6);
○ Data to define the urbanized area boundary and NHS limits as documented in the State DOT Baseline Performance Period Report; and
○ Population data, as defined by the most recent U.S. Decennial Census that was available when targets were first reported by the State DOT in their Baseline Performance Period Report.
The FHWA would use these biennial determinations to assess if the State DOT is in compliance with the NHPP
For the NHPP, the requirement for State DOTs to take the additional reporting actions would be based on each FHWA biennial determination. This is a change from the second NPRM, which proposed that the requirement for a State DOT to take the additional reporting actions would be based on two consecutive FHWA biennial determinations. As discussed in previous sections, the enactment of FAST Act introduced the significant progress determination requirements for the NHFP and removed the requirement that two consecutive reports (4 year period) be used in determining if a State DOT would be required to take additional reporting actions when the State DOT has made significant progress toward its NHPP targets. Thus, in this NPRM, the language has been changed to reflect the statutory language in FAST Act. The FHWA proposes, in this NPRM, that FHWA would determine whether or not a State DOT has achieved or make significant progress toward its NHPP and NHFP targets every biennial reporting period, and the determination on whether or not a State DOT would take additional reporting actions based on each of FHWA biennial determination.
In section 490.109(a), FHWA proposes that it would determine whether a State DOT has achieved or has made significant progress toward achieving each of the State DOT's targets for each of the NHPP and NHFP measures separately.
The FHWA proposes in section 490.109(b) that FHWA would determine whether a State DOT has or has not made significant progress for NHPP and NHFP targets at the midpoint and the end of each performance period.
In section 490.109(c), FHWA proposes that FHWA would determine significant progress toward the achievement of a State DOT's NHPP and NHFP targets after the State DOT submittal of the Mid Performance Period Progress Report and after the State DOT submittal of the Full Performance Period Progress Report. This process, which is described in the discussion of section 490.107(b), would follow the proposed schedule illustrated in Figures 4 and 5. Following this proposed frequency, the FHWA would
The FAST Act introduced 23 U.S.C. 167(j), which says “If the Administrator determines that a State has not met or made significant progress toward meeting the performance targets related to freight movement of the State established under section 150(d) by the date that is 2 years after the date of the establishment of the performance targets, the State shall include in the next report submitted under section 150(e) a description of the actions the State will undertake to achieve the targets, including . . .” The FHWA interprets the 2-year period referenced in 23 U.S.C. 167(j) as 2 years after the start of the performance period, which is consistent with 150(e) reporting requirements and the reporting regulations of this NPRM. This 2 year period is the period of time the State DOT has to establish targets, collect data, and provide information to FHWA. This interpretation allows FHWA to determine if a State DOT has made significant progress on its 2-year targets following the submittal of its Mid Performance Period Progress Report, and on its 4-year targets following the submittal of its Full Performance Period Progress Report.
The FHWA would notify all State DOTs within a reasonable time of the final determination and would advise on any subsequent need to address progress achievement in their next biennial reports (see 450.109(f)). The data reported to FHWA by the States would be available to the public and would be used to communicate a national performance story. The FHWA is developing a public Web site to share performance related information. This information would provide for greater transparency for FHWA programs.
The FHWA also expects that during a performance period, State DOTs would routinely monitor leading indicators, such as program delivery status, to assess if they are on track to make significant progress toward achievement of their NHPP and NHFP targets. If a State DOT anticipates it may not make significant progress, it is encouraged to work with FHWA and seek technical assistance during the performance period to identify the actions that can be taken to improve progress toward making significant progress. The FHWA also seeks comment on whether it should require State DOTs to more frequently (
The FHWA desires to use national datasets in a consistent manner as a basis for making its NHPP and NHFP significant progress determinations. Thus, in section 490.109(d), FHWA proposes to use specific data sources that could be accessed by State DOTs and others if they chose to replicate FHWA's determinations. The data in these sources, specifically the HPMS, would be provided by State DOTs as proposed in Subparts E-F. To ensure a repeatable process, in section 490.109(d), FHWA is proposing to establish a specific date (August 15) to extract data from the HPMS for the measures proposed in this NPRM, as the HPMS is often updated. This “extraction” date is considered the earliest time data can be available in a national data source. This proposed “extraction” date considers the time State DOTs typically need to submit the data to HPMS, to process raw data, and to address missing or incorrect data that may be identified as a result of quality assessments conducted by the State DOT and/or FHWA. The proposed “extraction” date is necessary for FHWA to make significant progress determinations in a timely manner. The FHWA is proposing to extract metric data from the HPMS on August 15 to determine the actual performance of Interstate System and non-Interstate NHS for the Reliability and Peak Hour Travel Time measures, and Freight measures, as specified in sections 490.105(c)(4), (c)(5), and (c)(6). This date is needed to provide FHWA with sufficient time to make a determination of significant progress for NHPP and NHFP targets.
In section 490.109(e), FHWA proposes a process for the significant progress determination for each individual NHPP and NHFP target. In paragraph (e)(1), FHWA proposes that FHWA would assess how the target established by the State DOT compares to the actual condition/performance using the data/information sources described in section 490.109(d). This process is generally outlined in Step 3 of the 3-step process described earlier. The FHWA proposes, in section 490.109(e)(2), that FHWA would determine that a State DOT has made significant progress for each 2-year or 4-year target if either: (1) The actual condition/performance level is better than the baseline condition/performance reported in the State DOT Baseline Performance Period Report; or (2) the actual condition/performance level is equal to or better than the established target.
For illustrative purposes, 2-year and 4-year evaluations where improving targets were established for the first performance period are shown in Figure 6.
The FHWA recognizes that State DOTs have to consider their fiscal situation in target establishment and acknowledges that, in some cases, anticipated condition/performance could be projected to decline from (or sustain) the baseline condition/performance due to lack of funding, changing priorities, etc. In these cases, State DOTs should document why they project a decline in condition in their Biennial Performance Reports as discussed in paragraph 490.107(b)(1)(ii)(A). The FHWA proposes that significant progress could still be made in cases where the established target indicates a decline from (or sustain) the baseline condition/performance. For the decline/sustain condition/performance scenario, FHWA proposes that significant progress is made for a target when actual condition/performance level is equal to or exceeds the target. For illustrative purposes, 2-year and 4-year evaluations where declining targets were established for the first performance period are shown in Figure 7.
As discussed in section 490.105(e)(7), FHWA recognizes the data limitation issues associated with the non-Interstate NHS travel time reliability measure (in section 490.507(a)(2)) prior to the start of the first performance period. Considering this limitation, FHWA proposes in section 490.105(e)(7) that for the first performance period, the State DOTs would not be required to report their 2-year targets and their baseline condition for the non-Interstate NHS travel time reliability measure at the beginning of the first performance period. Consequently, FHWA proposes in section 490.109(e)(3) that for the first performance period only, progress toward the achievement of 2-year targets for non-Interstate NHS travel time reliability measure would not be subject to FHWA determination under section 490.109(e)(2).
The FHWA proposes to accomplish this by categorizing the 2-year targets for the non-Interstate NHS travel time reliability measure as “progress not determined,” which would exclude these targets from the FHWA determination under section 490.109(e)(2). The FHWA expects that some State DOTs would adjust their established 4-year targets at the midpoint of the first performance period because they may have had limited baseline data available to them when they first establish the 4-year target. For the first performance period, FHWA would determine significant progress toward the achievement of a State DOT's non-Interstate NHS travel time reliability measure targets based on HPMS data extracted on August15 of the year in which the Full Performance Period Progress Report is due. The FHWA recognizes that some State DOTs would be able to establish and report baseline condition and 2-year targets for the proposed non-Interstate NHS travel time reliability measure in their first Baseline Performance Period Report. However, FHWA proposes that the process established in this section apply to all State DOTs in order to ensure uniformity in the progress determination process.
In section 490.109(e)(4), FHWA proposes that if a State DOT does not provide sufficient data and/or information for FHWA to make a significant progress determination for NHPP or NHFP target(s), then that State DOT would be deemed to not have made significant progress for those individual target(s).
In section 490.109(e)(5), if a State DOT encounters extenuating circumstances beyond its control, the State DOT would document the explanation of the extenuating circumstances in the biennial performance report. This explanation would address factors that the State DOT could not have foreseen and were outside of its control when it established targets at the beginning of the performance period. If the explanation is accepted by FHWA, then the associated NHPP or NHFP target(s) would be classified as “progress not determined” and would not be subject to the requirement under section 490.109(f). If the explanation is not accepted by FHWA, then the State DOT would be deemed to not have made significant progress for the target. Proposed extenuating circumstances are listed in 490.109(e)(5). The list includes:
• Natural or man-made disasters causing delay in NHPP or NHFP project delivery, extenuating delay in data collection, and/or damage/loss of data system;
• sudden discontinuation of Federal Government furnished data due to natural and man-made disasters or lack of funding; and/or
• new law and/or regulation directing State DOTs to change metric and/or measure calculation.
In section 490.109(f), pursuant to 23 U.S.C. 119(e)(7) and 23 U.S.C. 167(j), FHWA has proposed that if that if
• Interstate System pavement condition—both proposed measures Percentage of pavements of the Interstate System in Good condition in section 490.307(a)(1) and Percentage of pavements of the Interstate System in Poor condition in section 490.307(a)(2);
• Non-Interstate NHS pavement condition—both proposed measures Percentage of pavements of the non-Interstate NHS in Poor condition in section 490.307(a)(3) and Percentage of pavements of the non-Interstate NHS in Good condition in section 490.307(a)(4);
• NHS bridge condition—both measures Percentage of NHS bridges in Good condition in section 490.407(c)(1) and Percentage of NHS bridges in Poor condition in section in 490.407(c)(2);
• NHS travel time reliability—both measures Percent of the Interstate System providing for Reliable Travel Times in section 490.507(a)(1) and Percent of the non-Interstate NHS providing for Reliable Travel Times in section 490.507(a)(2); and
• Peak Hour Travel Time for an Urbanized Area—both measures Percent of the Interstate System where peak hour travel times meet expectations in section 490.507(b)(1) and Percent of the non-Interstate NHS where peak hour travel times meet expectations in section 490.507(b)(2). Please note the grouping for these measures is for each urbanized area separately.
• Freight movement on the Interstate System—both measures Percent of the Interstate System Mileage providing for Reliable Truck Travel Times in section 490.607(a), and Percent of the Interstate System Mileage Uncongested in section 490.607(b).
As a general example of this proposed approach, when a State DOT has not made significant progress for any one of the targets for NHS travel time reliability measures (Interstate or non-Interstate NHS), then that State DOT would, at a minimum, include in its next Biennial Performance Report a description of the actions the State DOT will undertake to improve conditions for NHS travel time reliability measures (Interstate or non-Interstate NHS). As for the peak hour travel time measures, if significant progress is not made for either urbanized area specific target (Interstate or non-Interstate NHS), as described in section 490.105(e)(8), for an urbanized area, then the State DOT would document the actions it will take to improve both the Interstate and non-Interstate NHS peak hour travel times such that both targets for the peak hour travel time measures will be achieved for that urbanized area.
States must provide description of the actions they will undertake in the next Biennial Performance Report. The FHWA strongly encourages States to add a description of their planned actions to their most recent Biennial Report within 6 months of the FHWA significant progress determination to ensure actions to achieve targets are taken in a timely manner, and to improve progress toward making significant progress for the applicable targets.
Tables 10 and 11 illustrate this proposed determination method for both the NHPP and NHFP measures. Table 10 includes the significant progress determination results in 2021 for the midpoint of the 1st performance period and the significant progress determination in 2023 for the end of the 1st performance period.
In Table 10 above, the statewide target for the measure Percent of the Interstate System providing for Reliable Travel Times did not make significant progress for the 2-year target in FHWA's biennial determination in 2021. In this example, the State DOT would include, at a minimum, in its next Biennial Performance Report (
Also in Table 10, for the hypothetical “Urbanized Area A,” the urbanized area target for the measure Percent of the non-Interstate NHS where peak hour travel times meet expectations did not make significant progress for the 4-year target in FHWA's biennial determination in 2023. In this example, the State DOT would include in its next Biennial Performance Report (
The FHWA believes that any one of the targets would impact other targets in the same measure group and that the State DOT's descriptions of the actions for all targets in a same measure group would be more logical and sensible in managing performance of relevant network rather than isolated description on a subset of the network. So, FHWA proposes that a State DOT would provide a description of the actions the State DOT will undertake to achieve all targets in the same measure group.
As indicated in the previous discussion in section 490.109, FHWA would make the significant progress determination each time the State DOT submits its Mid Performance Period Progress Report and its Full Performance Period Progress Report (every 2 years). In section 490.109(f)(2), FHWA proposes the consequences for not making significant progress for the NHFP measures in 490.105(c)(6). Pursuant to 23 U.S.C. 167(j), if a State DOT has not made significant progress toward the achievement of NHFP targets in a single FHWA biennial determination, then the State DOT must take the required actions in section 490.109(f)(2).
When a State DOT does not make significant progress toward the achievement of NHFP targets, it must include a description of the actions the State DOT will undertake to achieve the targets in its next Biennial Performance Report. This discussion must include:
• A description of the actions the State DOT will undertake to achieve targets including an identification of significant freight system trends, needs and issues within the State;
• a description of the freight policies and strategies that will guide the freight-related transportation investments of the State;
• an inventory of freight bottlenecks with the State and a description of the ways in which the State DOT is allocating national highway freight program funds to improve those bottlenecks; and
• a description of the actions the State DOT will undertake to meet the performance targets of the State.
For the purpose of the requirements in section 490.109(f)(2), the State DOT may reference the Statewide Freight Plan elements that identify freight system trends, needs and issues, as well as the freight policies and strategies in the Plan to guide investment. Under Section 150(e), State DOTs are already responsible for reporting on ways in which the State DOT is addressing freight bottlenecks, which are defined as those segments of the Interstates not meeting the threshold levels for congestion and average speed, as well as any other bottlenecks the State DOT wishes to include and anything that is identified in the National Freight Strategic Plan. The State DOT will provide an inventory of those segments as defined for section 150(e) and any other locations the State DOT wishes to reference as a bottleneck, as well as any bottleneck referenced in the National Freight Strategic Plan. Additionally, the State DOT will describe how funding is or will be allocated to improve freight fluidity through bottlenecks, as well as other actions to meet performance targets of the Interstates in the State.
In section 490.109(f)(3), FHWA proposes that State DOTs who fail to make significant progress for either the NHPP or NHFP should amend their Biennial Performance Reports within 6 months of FHWA's determination to include the actions they will take to achieve their targets. State DOTs are required to include description of the actions the State DOT will undertake to achieve targets in its next Biennial Performance Reports to meet the requirement in 23 U.S.C. 119(e)(7), as described in paragraph (f) of this section. State DOTs are encouraged to amend their most recent Biennial Performance Reports to include this information. As discussed in sections 490.107(b)(2)(ii)(F) and 490.107(b)(3)(ii)(E), all State DOTs are required to discuss the progress they have made toward the achievement of targets established for the NHPP and NHFP measures in each of their Biennial Performance Reports. The FHWA expects State DOTs would routinely monitor leading indicators, such as program delivery status and measured data, to assess if they are on track to make significant progress for their NHPP and NHFP targets and expects State DOTs to be aware of their progress prior to the time of each Biennial Performance Report. As described in the discussion of section 490.109(c), if a State DOT anticipates it may not make significant progress, it is encouraged to work with FHWA and seek technical assistance during the performance period to identify the actions that can be taken in a timely manner to improve progress toward making significant progress for the targets reported in subsequent Biennial Performance Reports. Thus, in section 490.109(f)(3), FHWA proposes that the State DOT should, within 6 months of the significant progress determination, amend its Biennial Performance Report to document the information specified in this section to ensure actions are being taken to achieve targets.
In the second performance measure NPRM, FHWA had proposed to incorporate the proposed HPMS Field Manual to codify the data requirements for measures and to be consistent with HPMS reporting requirements. In this NPRM, FHWA proposes to extend that incorporation to subparts E though G. This would codify the data requirements for these measures and ensure consistency with HPMS reporting requirements. The proposed HPMS Field Manual includes detailed information on technical procedures to be used as reference by those collecting and reporting data for the proposed measures. The proposed HPMS Field Manual is included in the docket.
In this section, FHWA describes the proposed provisions in Subpart E, which would establish performance measures to assess the performance of the NHS. The discussions of the proposed requirements are organized as follows:
• Section 490.501 discusses the purpose of the subpart;
• Section 490.503 describes the applicability of the subpart;
• Section 490.505 presents the definitions;
• Section 490.507 discusses the performance measures;
• Section 490.509 describes the data requirements;
• Section 490.511 identifies how to calculate performance metrics; and,
• Section 490.513 presents how to calculate performance measures.
The following provides a general discussion of the relationship between data requirements, metrics, and measures. This relationship exists in this Subpart as well as Subparts F—H.
• Data Requirements—Outlines the data necessary to determine the required set of metrics that would be used to calculate the relevant measures. The type of data to be collected, the methods of data collection, and the extent and frequency of collection are described below and in the appropriate sections.
• Metrics—Describes the values that would be calculated from the data collected to support measure development and how to report the individual metrics.
• Measures—Provides the method to calculate the measures using reported metrics. State DOTs would use the calculated measures to report baseline condition or performance, establish targets, and report on progress.
The FHWA is required, under 23 U.S.C. 150(c), to establish performance measures for State DOTs to use to assess the performance of the Interstate System and of the non-Interstate NHS. In this Subpart, FHWA proposes to establish two measures (1) a travel time reliability measure and (2) a peak hour travel time measure.
The FHWA is proposing to establish a travel time reliability measure to apply to the entire NHS, including Interstate System and non-Interstate NHS elements. This measure would compare the longest travel time or slowest speed that occurs during a specified time frame to a reference travel time or speed for a transportation facility. A reliability measure is an indication of the extra time travelers must add to their trips in order to have a high degree of certainty that they will arrive at their destination on time. The FHWA has defined travel time reliability as the variability of travel times. Reliability, in the eyes of transportation system users, reflects how consistent a travel time is on portions of the NHS they are traveling on. The larger the variability of travel times is from day-to-day or hour-to-hour, the more the user has to plan for unexpectedly long travel times when planning a trip. For instance, to make sure a traveler arrives at the airport in time for a flight, the traveler may allot extra travel time to ensure that he/she arrives in time in case of traffic incident, bad weather, or road construction along the way.
In more mathematical terms, reliability looks at the longer (all travelers) or longest (freight) travel times faced by users on portions of the NHS and compares these times to what is typically experienced by the system user (normal travel time). The larger the difference in these travel times, the worse the reliability is. In order to improve reliability, State DOTs and MPOs can implement operational and other strategies that are specifically designed make the system more reliable and efficient.
The reliability measure proposed in this NPRM would be reported as a Percent of the Interstate System providing reliable travel times and as the Percent of the Non-Interstate NHS providing reliable travel times. What that really means is that the number of miles on the Interstate or Non-Interstate NHS that performed in a reliable manner will be those miles where the travel time during any time period of the “daylight” hours (6 a.m. to 8 p.m.), 7 days a week, did not surpass the normal travel time by more 50 percent. The time periods during “daylight” hours include: 6 a.m. to 10 a.m. weekdays, 10 a.m. to 4 p.m. weekdays, 4 p.m. to 8 p.m. weekdays, and weekend days 6 a.m. to 8 p.m. If the longer travel times exceed the normal travel time by 50 percent or more in any of these time periods, then that section of road is considered unreliable. The FHWA experience and analysis led to the proposed threshold of 1.5, which reflects 50 percent longer travel times. The FHWA seeks comments on whether the 1.5 threshold is appropriate.
The calculations (or metrics) used to report this measure report the travel time reliability for every road segment on the NHS, so it will be readily apparent to State DOTs, MPOs, and the general public where the NHS road segments are that have a reliability problem.
The FHWA also notes two important refinements that strengthen travel time reliability measures: (1) Some operating agencies currently exclude the top 20 percent of longest travel times throughout the year when developing reliability-related measures because these travel times typically are due to extreme events that are beyond an agency's control and should not be considered in the assessment of overall system performance; and (2) the reference travel time used in a reliability measure often reflects travel time associated with typical or average travel speeds rather than the time associated with free flow travel speeds.
By establishing targets for, and reporting on this measure, State DOTs and MPOs can better identify and manage portions of the NHS where users experience unreliable travel. Note that FHWA is proposing a phase-in for the establishment of targets for the non-Interstate NHS reliability measure which is outlined in more detail under the discussion for section 490.105(e)(7).
The FHWA is proposing to establish a peak hour travel time measure to apply to the NHS, including Interstate System and non-Interstate NHS, within urbanized areas with a population over 1 million. By establishing targets for, and reporting on this measure, State DOTs and MPOs can better identify and manage portions of the NHS in major urbanized areas regardless of roadway ownership. As proposed, FHWA expects State DOTs and MPOs to use this measure to report one outcome for each of the applicable urbanized areas, even in cases where the boundary of the urbanized area intersects multiple States and metropolitan planning areas.
The FHWA is proposing to define
The FHWA is proposing to define
The FHWA is proposing to define
The FHWA is proposing to define
The FHWA is proposing to define
A
Please note that Table 11 is a simple illustration of obtaining 50th and 80th percentile values in a hypothetical dataset with 20 travel time entries. Within Table 11, the 50th percentile is calculated by multiplying the total number of travel time entries (20) by 0.5 resulting in “10.” So the tenth entry in the table would be the 50th percentile travel time (23 seconds). The same approach would be used with the 80th percentile calculation: 20 travel time entries × 0.8 = 16 so the 16th entry is the 80th percentile travel time (27 seconds). Please see section 490.511 for the specifics on the proposed metrics for Travel Time Reliability and Peak Hour Travel Time measures.
The FHWA is proposing in section 490.507 the establishment of four measures to be used to assess the
Travel Time Reliability:
• Percent of the Interstate System providing for Reliable travel times
• Percent of the non-Interstate NHS providing for Reliable travel times
Peak Hour Travel Time:
• Percent of the Interstate System in large urbanized areas over 1 million in population where peak hour travel times meet expectations
• Percent of the non-Interstate NHS in large urbanized areas over 1 million in population where peak hour travel times meet expectations.
State DOTs and MPOs would need to establish targets for each of these measures in accordance with section 490.105. These measures would be calculated using the metrics proposed in section 490.511 following the methods proposed in section 490.513. The data to support the measures are proposed in section 490.509. The proposed travel time reliability measures are designed to be used by State DOTs and MPOs to better understand the scope of reliability problems on their highway systems and to aid in identifying and implementing strategies to improve system performance. These measures are intended to quantify the variability in travel times experienced by users of the highway system during hours of the day when the predominant travel occurs on the system. In general, the variability captured by the proposed measures would be a comparison of some of the longer travel times experienced by users compared to the amount of time users typically expect their travel to take. This comparison is an indication of how reliable the highway system is, in terms of how close actual travel times are to what is expected by users.
Based on research the FHWA has been doing for the past several years, it believes that measuring the reliability of travel times is a key to operating the system more efficiently and reliably.
The proposed peak hour travel time measures are designed to be used by State DOTs and MPOs in urbanized areas over 1 million in population to better understand the scope of undesirable congestion problems in these large urbanized areas and to identify and implement strategies to improve system performance in these areas. The measures are designed to compare the longest average time of travel experienced by users during peak hours of the day to the travel time desired for the system. The FHWA is proposing in section 490.511(c)(1) that the State DOT, in coordination with MPOs, establish a desired time of travel for sections of their highway system that would be consistent with its intended use and design. The proposed measure would represent the percentage of the applicable highway network where actual travel times experienced during peak hours meets the expectations of the State DOT and MPOs. The FHWA is proposing that peak hour travel times that meet expectations would be those conditions where actual travel times are less than 50 percent greater than what is desired for the highway.
The FHWA heard concerns from many stakeholders regarding the effectiveness of the establishment of measures that would utilize an absolute speed or travel time as a reference to assess NHS performance. Many felt that some portions of the new expanded NHS highway network may be functioning as intended even when traffic is not flowing freely. Considering this, FHWA is proposing an approach where State DOTs, in coordination with MPOs, would establish Desired Peak Period Travel Times (as times that are desired for the reporting segment) to be used as the basis for the peak hour measures. The Desired Peak Hour Period Travel Time would reflect the policies and management approach for the urbanized areas. In addition, as discussed in section 490.105(e)(8), FHWA is proposing that the peak hour travel time measures would only be applicable to NHS highways in urbanized areas where populations are greater than 1 million. For these measures, one single target would be established and reported for each applicable urbanized area, where collectively all State DOTs and MPOs in these areas would need to agree on the single target even where the urbanized area intersects with multiple jurisdictional boundaries. In total, based on the 2010 U.S. Census, 42 targets would be established nationwide using this measure—one for each urbanized area where populations are greater than 1 million. This approach is being proposed so that State DOTs and MPOs can work collectively to address highway performance problems that cross geographic boundaries and impact the ability to improve system performance throughout the urbanized area.
The FHWA is proposing for State DOTs and MPOs to use a travel time data set that would meet the requirements discussed in section 490.103 of this rulemaking to calculate the metrics defined in section 490.511. State DOTs and MPOs would use the same travel time data set to assess the performance of the directional mainline highways of the NHS.
The FHWA is proposing State DOTs, in coordination with MPOs, establish and submit reporting segments as discussed in section 490.103 of this rulemaking. These reporting segments would be used as the basis for calculating and reporting metrics to the FHWA and for State DOTs and MPOs to calculate the measures proposed in this subpart to assess Interstate System and non-Interstate NHS performance. Reporting segments, as defined in 490.101, include one or more travel time segments and must be contiguous so that they cover the full extent of the mainline highways of the NHS in the State. The section 490.103 discussion included in this rulemaking provides more information on the proposal for State DOTs to define and submit reporting segments.
The FHWA is proposing in this section that State DOTs would use the posted speed limits of roadways to estimate travel times for calculating the Reliability metrics when the data is missing or represented as a time of “0” or null in the Travel Time Data Set. The proposed use of the posted speed data is discussed in section 490.511. The FHWA is not proposing that posted
The areas that would be applicable to the Peak Hour Travel Time measure would be identified when the State DOT Baseline Performance Period Report is due to FHWA, based on the urbanized area boundaries at that time. These areas would continue to be applicable to the measure (or conversely “not applicable”) for the duration of the performance period regardless of population changes that may occur during the performance period. The FHWA is proposing that the applicability of the area be determined using the most recent U.S. Decennial Census reports on area populations. At the time of this rulemaking, the Peak Hour Travel Time measure would be applicable to 42 urbanized areas in the United States.
The FHWA is proposing that two metrics need to be calculated to develop the Travel Time Reliability and Peak Hour Travel Time measures proposed in this rulemaking. They are the LOTTR metric and the Peak Hour Travel Time Ratio (PHTTR) metric. State DOTs would be required to calculate these metrics for all applicable roadway segments for the applicable time periods and report them to FHWA annually. The proposed approach to calculate and report these metrics is discussed in this section.
As proposed in section 490.511(b), the LOTTR metric would be calculated annually by the State DOT for all reporting segments on the NHS in the State and used by FHWA, State DOTs, and MPOs to assess the performance of the system. The source of data would be the Travel Time Data Set. The FHWA is proposing that 5 minute travel time bins that do not have data reported, or are reported as null, or “0” in the Travel Time Data Set would be replaced with a calculation of the travel time needed to fully traverse the travel time segment while traveling at the posted speed limit. This will ensure that a complete set of travel times for the time periods throughout the day needed to calculate the LOTTR metric are utilized. The FHWA believes that, in order to calculate an accurate assessment of reliability, travel times throughout the day are necessary to capture the variability of travel times on the system. The FHWA is proposing that in cases where travel times are not recorded, typically due to a lack of probe sources, it is assumed that vehicles are travelling at the posted speed limit. The FHWA believes that this assumption is valid since a lack of vehicles present during a 5 minute interval on a roadway segment generally indicates uncongested conditions. The FHWA believes that as technologies improve and the percentage of vehicles containing equipment capable of communicating with vehicle probes increases, the potential for missing data will decrease over time. Considering the possibility for travel times to be missing during different time intervals of the day and the need for a complete data set to accurately calculate the reliability metric, FHWA encourages comments from the public on this proposed approach and/or alternative approaches that could be used reliably as part of a national performance program.
The FHWA is proposing that the LOTTR metric is based on the variability of travel times over a full year during following time periods: Weekdays 6:00 a.m. to 10:00 a.m.; 10:00 a.m. to 4:00 p.m.; 4:00 to 8:00 p.m.; and weekend days 6:00 a.m. to 8:00 p.m. The FHWA selected these time periods to cover peak hours and other times of day the system may be used the most. It is FHWA's desire to have the Travel Time Reliability metric reflect the level of consistency in travel times during hours of the day when the majority of highway use occurs. In addition, by using these smaller time periods, State DOTs and MPOs may better understand reliability issues during varying travel periods throughout the week (
The FHWA reviewed other options for the denominator in the LOTTR metric and determined that the 50th percentile, more so than either the 20th percentile or average travel time, more accurately reflected the expected time. Use of the 50th percentile, along with the 80th percentile, travel time, shows the variability in travel times that operational strategies can positively affect in helping to improve travel time reliability.
In general, the proposed calculation is made by ranking, from the shortest travel time to the longest, all the travel time values in each reporting segment for each time period (weekdays 6 a.m. to 10 a.m.; 10 a.m. to 4 p.m.; and 4 p.m. to 8 p.m. and weekends 6 a.m.to 8 p.m.) every day from January 1st through December 31st and identifying the 50th and 80th percentile travel times in this series for each time period. An example is contained in Table 11. The FHWA is proposing that the LOTTR metric would be calculated by developing a ratio that compares the 80th percentile travel time to the normal (50th percentile) travel time as shown in the following equation.
The resulting LOTTR metrics (one for each time period) would be rounded to the nearest hundredth decimal place and calculated for every NHS reporting segment within the State. The LOTTR values for each of the four time periods would be reported for the relevant reporting segment. The FHWA believes that the comparison of the 80th and 50th percentiles of the travel times occurring during the time periods identified, the most typical travel times, will reflect the reliability of the system as perceived by most highway users. The FHWA encourages comments from the public on the use of time periods to develop the LOTTR metric, as well as the number and length of the time periods proposed.
In section 490.511(c), FHWA is proposing that the PHTTR metric would be calculated by State DOTs for all NHS mileage within urbanized areas with a population over 1 million using average peak hour travel times derived from the Travel Time Data Set. The proposed metric is a comparison of the longest average hourly travel time, referred to in this rulemaking as the “peak hour travel time,” to the travel time desired by the State DOT and MPO for the reporting segment. The FHWA is not proposing to address missing data for this metric as:
• The metric is focused on travel occurring during only peak hours of the day when it may not be correct to assume free flowing conditions when data are missing; and
• the metric is computed using hourly average travel times that can be determined even if there are missing 5 minute travel time bins within the one hour time period.
The FHWA also proposes that, for this metric, any 5 minute bin travel times that represent travel speeds below 2 mph or above 100 mph be excluded from the metric calculation to remove outliers that may negatively affect the metric. The FHWA encourages comments on these approaches and invites suggestions on alternatives that could be considered that may be more effective.
In this rulemaking, FHWA is proposing that the peak period of travel will occur between 6:00 a.m. and 9:00 a.m. or between 4:00 p.m. and 7:00 p.m. on non-holiday weekdays. The six 1-hour time blocks within these periods are referred to as the “peak period” in this rulemaking. The FHWA proposes a 2-step process of determining the peak hour of travel time for calculating the PHTTR metric for a reporting segment. As the first step, the annual average travel time for each of the six hourly blocks in the peak period (6:00 a.m. to 7:00 a.m.; 7:00 a.m. to 8:00 a.m.; 8:00 a.m. to 9:00 a.m.; 4:00 p.m. to 5:00 p.m.; 5:00 p.m. to 6:00 p.m.; and 6:00 p.m. to 7:00 p.m.) would be calculated separately for a reporting segment. For calculating those six annual averages, measured travel times on non-holiday weekdays over a full calendar year would be used. As the second step, the highest numeric value, or longest time, of the annual average travel time among the hours in the peak period would be selected as the peak hour travel time for calculating the PHTTR metric for the reporting segment and that hour would be referred to as the “peak hour” for metric and measure development purposes. For example, if annual average peak hour travel times across a reporting segment were as follows: 6:00 a.m. to 7:00 a.m.: 125 seconds; 7:00 a.m. to 8:00 a.m.: 196 seconds; 8:00 a.m. to 9:00 a.m.: 120 seconds; 4:00 p.m. to 5:00 p.m.: 105 seconds; 5:00 p.m. to 6:00 p.m.: 105 seconds; 6:00 p.m. to 7:00 p.m.: 108 seconds, then the 7:00 a.m. to 8:00 a.m. period with an average annual hourly travel time of 196 seconds would be selected as the peak hour and used to calculate the PHTTR.
This proposed process is illustrated in the equation below:
The FHWA is proposing that State DOTs, in coordination with MPOs, establish Desired Peak Period Travel Times for each reporting segment, based on their operational policies for NHS roadways. The FHWA recommends that these Desired Peak Period Travel Times also be developed in consultation with operating agencies. For each reporting segment, State DOTs would need to report a single “Desired Peak Period Travel Time” for the morning hours in the peak period and a single “Desired Peak Period Travel Time” for the afternoon hours in the peak period when reporting segments are submitted to FHWA as proposed in section 490.103(f). As proposed, State DOTs would only be allowed to modify the Desired Peak Period Travel Time if the reporting segment lengths change during a performance period. The FHWA anticipates that State DOTs will work with MPOs, in consultation with applicable operating agencies, to develop polices (
The FHWA is proposing that the PHTTR ratio is a comparison of the Peak Hour Travel Time to the Desired Peak Period Travel Time for each reporting segment and calculated as illustrated in the following equation:
In section 490.511(d), FHWA is proposing for State DOTs to report annually the LOTTR and PHTTR metrics for each applicable reporting segment on the NHS. State DOTs would report these metrics in HPMS no later than June 15th of the following year (
• NPMRDS TMC codes (or related reporting segments made up of multiple Travel Time Segments) or standard HPMS location referencing;
• LOTTR metrics for each of the four time periods, to the nearest hundredth;
• 80th percentile, travel times for each of the four time periods to the nearest second;
• 50th percentile, travel times for each of the four time periods to the nearest second;
• PHTTR metric, to the nearest hundredth;
• Peak Hour Travel Time, to the nearest second; and
• the Hour (6 a.m., 7 a.m., 8 a.m., 4 p.m., 5 p.m., or 6 p.m.)
The FHWA intends to issue additional guidance on how State DOTs could report these data to HPMS. The FHWA recognizes the burden associated with the efforts needed to conflate (or relate) travel time reporting segments (NPMRDS data locations) to locations on a defined roadway network (State GIS-based locations). For this reason, FHWA is not proposing a requirement for State DOTs to conflate the travel time reporting segments to the HPMS roadway network. The FHWA intends to conduct this conflation.
The FHWA is proposing section 490.513 to establish a method that can be used by State DOTs, MPOs, and FHWA to calculate the performance measures proposed in section 490.507. These system performance measures are based on the performance metrics proposed in section 490.511 Calculation of System Performance Metric(s). The FHWA expects that State DOTs and MPOs will use the methods proposed in this section to assess and report on the performance of the system. The FHWA proposes to use this calculation method to report on performance at a national level and to carry out its evaluation of the progress made by State DOTs to achieve their NHPP targets.
The proposed calculation method would be used to determine the percentage of the system, by length, operating at a specified level of performance. The general format for this calculation is illustrated in the equation below:
The FHWA is proposing the level that represents reliable travel to highway users is a LOTTR of 1.50. This LOTTR level represents an operating level where 80 percent of the travel times observed on a roadway segment is less than 50 percent more than what is observed normally (defined as the 50th percentile travel time for this rulemaking). The LOTTR is a ratio, so a 1.0 would mean that the 80th and 50th percentile travel times were the same. A 1.50 or above LOTTR means that the 80th percentile travel time is 50 percent longer than the 50th percentile travel time and represents less than acceptable travel time reliability. In general, this operating level of reliability represents conditions where the amount of time to travel on an NHS highway is up to 50 percent longer than what users would have expected. The FHWA also considered a threshold of 2.0, or twice the normal travel time, but determined that these travel times would be longer than most system users would consider reliable. The FHWA ultimately chose the 1.5 threshold understanding that there will be some variability in travel time that may be beyond the ability of operating agencies to affect. While any LOTTR above 1.00 would indicate some variability in travel time, it is the variability that is 50 percent more than the normal time that is being addressed with this measure and that has the ability to be addressed through operational and other strategy implementation. The FHWA encourages comments from the public on the proposed LOTTR threshold level of 1.50 and if it is at the appropriate level to indicate unreliable performance.
The FHWA is proposing that a PHTTR threshold level of 1.50 represents peak hour travel times that meet expectations of State DOTs, MPOs, and local operating agencies. This PHTTR level represents a condition where observed (or estimated) travel times in large urbanized areas are no more than 50 percent higher than what would be desired for the roadway, as identified by the State DOT and MPO. The PHTTR is a ratio where 1.0 would mean that that the actual peak hour travel time would equal to the Desired Peak Period Travel Time. So a PHTTR of 1.5 represents an actual peak hour travel time that is 50 percent higher than the Desired Peak Period Travel Time. The FHWA feels that a PHTTR level of 1.50 or higher indicates a roadway is no longer meeting its intended purpose, as desired by local needs, to move traffic through the system. The FHWA encourages comments from the public on the proposed PHTTR threshold level of 1.50 and if it is at the appropriate level to
Both of these measures use the same threshold—1.50. The FHWA believes that highway users and operating agencies begin to consider the system to not meet expectations when trips take 50 percent longer than what they would normally expect. For example, highway users would become frustrated with the system when a trip that is expected to take 30 minutes ends up taking 45 minutes or longer.
For the reliability measure, FHWA evaluated the impact of different threshold values ranging from 1.2 to 2.0 on reliability of the Interstate System in five States that varied in size and population. This evaluation showed minimal sensitivity to changes in reliability when the reliability threshold was above 1.6 and a sharp drop off in reliability when the threshold was below 1.3. The FHWA's proposed threshold value of 1.50 resulted in reliability levels that appeared to be reasonable as a level that could be used to manage performance.
A summary of the criteria described previously for the proposed performance measures, including the measure, the metric, and transportation network or geographic area the measure would apply to, is provided in Table 12 below:
In this sub-section, FHWA describes the proposed requirements in Subpart F, which would establish performance measures to assess freight movement on the Interstate System. The discussions of the proposed requirements are organized as follows:
• Section 490.601 discusses the purpose of the subpart;
• Section 490.603 describes the applicability of the subpart;
• Section 490.605 presents the definitions;
• Section 490.607 discusses the performance measures;
• Section 490.609 describes the data requirements;
• Section 490.611 identifies how to calculate performance metrics; and,
• Section 490.613 presents how to calculate performance measures.
The FHWA is required, under 23 U.S.C. 150(c), to establish performance measures for State DOTs to use to assess the performance of freight movement on the Interstate System. The FHWA proposes to establish in this subpart a travel time reliability measure and a congestion measure for State DOTs and MPOs to use to assess freight movement on the Interstate System.
As required by 23 U.S.C. 150(c)(6), FHWA proposes that the freight performance measures will apply to freight movement on the Interstate System.
The FHWA proposes to define
Slow or unreliable truck travel times are a cause of diminished productivity for drivers and equipment; they reduce the efficiency of operations, increase the cost of goods, increase fuel costs, and reduce drivers' available hours for service. Considering these potential impacts and the input received from public and private sector freight stakeholders, FHWA is proposing measures in this subpart that would focus on both the speed of truck travel and the time reliability for truck travel. The FHWA identifies these measures as complimentary in illustrating congestion and performance of the Interstate System. The FHWA believes that State DOTs and MPOs, by using both of these measures, can assess and evaluate areas where freight-movement problems are occurring on the Interstate System by looking at the entire Interstate System within their boundaries, as well as specific isolated areas where delays typically occur. The
The first proposed measure (Percent of the Interstate System providing for Reliable Truck Travel Times) is based on the concept of using a metric that is an index to assess the “extra budgeted time” needed to assure an on-time arrival. This concept, used by many transportation operating agencies today to assess and manage system operations, considers the variability in operating travel times as an indicator of trip time planning needs. In general, highways that are operating with higher travel time variability would require extra time to be budgeted to assure an on-time arrival of trips. This metric can be used as a management tool to identify the strategies that, when implemented effectively, would minimize the need for travelers to have to budget “extra time” into their trip planning.
The efficient use of resources to move goods across the country is particularly critical for freight operations on the Interstate System. For this reason, the reliability measure proposed in this subpart is designed to support freight trip planning needs where a high level of certainty is needed to assure on time arrivals for trips occurring at all hours throughout the year. Shippers, carriers, and receivers desire on-time or just-in-time delivery of goods and plan their trips by building in enough time to be on time. To do this, they consider the longest travel times of a route by looking at the distribution of travel times, which equates to the 95th percentile or higher. They typically budget their trip time at the 95th percentile travel time level. This assures their customers that aside from an extreme traffic event, they will be on time. However, the freight industry will consider the reliability ratio of the worst travel times to normal travel times in route planning and desire for there to be a low ratio meaning that there is little difference between the normal travel time and the worst travel times. They will reroute or consider other shipping options for routes with extreme congestion or high reliability rations. To be consistent with the industry measures of reliability, FHWA proposes to use the 95th percentile travel time in comparison to the 50th percentile travel time as the normal travel time. As a threshold, FHWA proposes that the reliability ratio be below 1.5. This means that the trips take no more than 50 percent longer than normal. The FHWA believes that the freight industry would not find trips that are longer than 50 percent above normal reliable. The FHWA seeks comments on this assumption.
The FHWA selected this ratio based on information it has received from stakeholders as well as its own research. As discussed with relation to section 490.513 (the performance of the NHS measures), FHWA believes that shippers and suppliers begin to consider the system to not meet expectations when trips take 50 percent longer than what they would normally expect.
The truck travel time reliability measure proposed in this subpart differs from the travel time reliability measure proposed in Subpart E (for performance of the Interstate and non-Interstate NHS) of this rulemaking in that the truck travel time reliability is focused on the variability in travel times experienced by trucks during all hours of the day and throughout the year. In contrast, the travel time reliability measure proposed in Subpart E is focused on the variability in travel times experienced by all vehicles that typically occur due to non-recurring events during the times of the day when the highway facility is in predominant use. The second proposed measure (Percent of the Interstate System Mileage Uncongested) uses average truck speeds to determine the percentage of Interstate System mileage that is considered uncongested. This measure is being proposed to assess where delays are occurring on the Interstate System so that strategies to address these locations can be implemented to improve the efficiency of freight movement. This measure differs from the reliability measure in that it is focused on shortening travel times where the reliability measure is focused on improving the consistency of travel times.
The congestion measure proposed in this subpart differs from the traffic congestion measure proposed in Subpart G (Annual Hours of Excessive Delay per Capita) of this rulemaking in that the speed threshold to identify the presence of congestion for freight movement is higher than the threshold used to define traffic congestion. In addition, the freight congestion measure broadly applies to all Interstate System roadways across the country where the traffic congestion measure is focused only on NHS roadways in the largest urbanized areas in the country. Both sets of measures are based on speed. The freight measures use speed to identify congested segments, while the traffic congestion measure uses speed to calculate the additional travel time caused by “excessive” delay.
The criteria used to establish the two proposed measures in this subpart are derived from research and testing of data by FHWA using the FPM. The FHWA produced two reports illustrating the use of Travel Time Reliability and Average Truck Speed measures to validate the proposed thresholds.
The FHWA is proposing that State DOTs use a travel time data set that would meet the requirements discussed in section 490.103 of this rulemaking to calculate the metrics defined in section 490.611. State DOTs and MPOs would use the same travel time data set to assess freight movement on the Interstate System.
The FHWA is proposing that State DOTs establish and submit reporting segments as discussed in section 490.103 of this rulemaking. These reporting segments would be used as the basis for calculating and reporting metrics to FHWA, and for their use and MPO use to calculate measures proposed in this subpart to assess freight movement. Reporting segments, as defined in section 490.101, include one or more travel time segments and must be contiguous so that they cover the full extent of the mainline highways of the Interstate System in the State. The section 490.103 discussion included in this rulemaking provides more information on the proposal for State DOTs to define and submit reporting segments.
The FHWA is proposing in this section that in cases where the travel time required to calculate a metric is missing or represented as a time of “0” or null in the Travel Time Data Set, State DOTs would be required to use an observed travel time that represents all traffic on the roadway during the same 5 minute interval (referred to as “all vehicles” in the NPMRDS) provided this travel time is representative of travel speeds less than the posted speed. In all other cases, FHWA is proposing that State DOTs use a travel time that would have occurred while traveling at the posted speed limit to replace missing travel times or those that are represented as a time of “0” or null in the Travel Time Data Set. The proposed use of the “all traffic” and posted speed
In section 490.611, FHWA proposes the methodologies for calculating Truck Travel Time Reliability and Average Truck Speed metrics. The FHWA is proposing the same method to calculate the truck travel time reliability metric as discussed for the LOTTR metric discussed in Subpart E of this rulemaking with the exception of the days/times and the travel time percentile used in the calculation. As discussed previously in Subpart E, this method would require State DOTs to assemble and organize a complete year of travel time data for each reporting segment to calculate the metric. The FHWA is proposing in section 490.611(b), that the assembled data would include, for each reporting segment, average truck travel times, to the nearest second, for 5 minute periods of the day, or 5-minute bins. The information in those 5-minute bins would be collected throughout the day, for every hour of every day from January 1st through December 31st of the same year. In cases where the 5-minute bins for travel time segments are:
• Missing from the dataset or include truck travel times reported as “0” or null; and
• do not include all traffic travel times representative of speeds less than the posted speed limit; then
• a truck travel time would be used that represents travel at the posted speed limit (TTT@PSL)
In section 490.611(b), to calculate the Truck Travel Time Reliability the FHWA is proposing that State DOTs would determine from the assembled data set described above the 95th percentile travel time and the 50th percentile travel time. The basis for the 95th percentile travel time is that it represents more certainty of on-time arrival for freight stakeholders. The 50th percentile was chosen, as previously described, based on an analysis of reliability measurement and how it compares to using the 20th percentile or average. The FHWA analyzed travel times for several regions in the Nation with different population characteristics and found that the 50th percentile provided the most accurate picture of reliability.
The metric would be determined by dividing the 95th percentile travel time by the 50th percentile travel time for each reporting segment. The FHWA believes that the 95th percentile travel time will represent the longest trip, excluding extreme outliers, that likely occurred on the reporting segment throughout the year and the 50th percentile travel time will typically represent the normal time experienced during the year. Therefore, the proposed metric will be an indication of the variability considering nearly all travel times that had occurred throughout the year. The FHWA is proposing this approach so that the Truck Travel Time Reliability metric would be an indicator of the planning time needed to assure a high level of confidence in on-time arrival of freight movements that could occur all hours of the day throughout the year. The FHWA is seeking comment specifically on the appropriateness of the proposed percentiles used in this metric calculation to assess reliability of truck travel times on the Interstate System.
In section 490.611(c), to calculate the Average Truck Speed metric for each reporting segment, truck travel speeds would be derived from the data in the travel time data set. Within that data set, for any 5-minute bins that are missing from the dataset, are missing data, or where data is reported as “0” or null, those bins would be replaced with the “all traffic” travel time value where the travel time correlates with speeds that are less than posted speed limit. In all other cases, it would be replaced with a travel time (TTT@PSL) that would represent the time to traverse the travel time segment at the posted speed limit.
Because the data set provides average travel times by Travel Time Segment and in 5-minute bins (or 5-minute periods), Average Truck Speed for a reporting segment would need to be calculated for the entire calendar year. Average truck travel time would be calculated by dividing the Travel Time Segment length by the truck travel time for each reporting segment for each 5-minute bin throughout the calendar year. Then, the result of this calculation for each of the 5-minute bins would be added together. This sum would be divided by the total number of 5-minute bins in a calendar year. This calculation would be done for each of the reporting segments.
In section 490.611(d), FHWA is proposing for State DOTs to report, on an annual frequency, the Truck Travel Time Reliability and Average Truck Speed metrics for each reporting segment on the Interstate System. State DOTs would report the annual outcomes to the HPMS by June 15th of the following year (
• Reference NPMRDS TMC codes (or related reporting segments made up of multiple TMC codes) or standard HPMS location referencing;
• Truck Travel Time Reliability metric, to the nearest hundredth;
• 95th percentile travel time to the nearest second;
• 50th percentile travel time to the nearest second; and
• Average Truck Speed metric, to the nearest hundredth mile per hour.
The FHWA intends to issue additional guidance on how State DOTs could report these data to HPMS. The FHWA recognizes the level of effort needed to conflate travel time reporting segments to align them with a referenced highway network for the system performance and freight measures. For this reason, FHWA is not proposing a requirement for State DOTs to conflate the travel time reporting segments to the HPMS roadway network. The FHWA intends to conduct this conflation, if needed, if State DOTs choose to report the metrics by Travel Time Segment codes.
In sections 490.613(a) and (b), FHWA proposes the method to calculate the measures to assess freight movement on the Interstate System proposed in section 490.607. This method would be used by State DOTs and MPOs to assess freight performance when reporting and establishing targets. The FHWA would also use this to report on freight performance at a national level. The two measures would be calculated using the
The proposed calculation method would be used to determine the percentage of the system, by length, operating at a specified level of performance for each of the two measures. The general format for this calculation is illustrated in the equation below:
The specific criteria proposed to calculate each of the measures following the format discussed above is proposed as follows:
• Truck Travel Time Reliability metric threshold < 1.50
• Average Truck Speed
The truck travel time reliability threshold of 1.50 is proposed to be the level at which truck travel times become unreliable. This level represents a condition where travel time could be no more than 50 percent longer than what would be expected during normal travel time conditions. Reliability levels greater than 1.50 are considered in this rulemaking to be unreliable due to the impact of the additional time that freight operators would need to consider and provide for during trip planning to assure on-time arrival. Reliability levels greater than 1.50 generally mean a trip could take twice as long as it would at the 50th percentile or normal travel time. This would not occur on every trip, but on the worst days. The FHWA also considered a threshold of 2.0, or twice the normal travel time, but determined that these travel times would be longer than most users would consider reliable. The FHWA ultimately chose the 1.5 threshold understanding that there will be some variability in travel time that may be beyond the ability of operating agencies to affect.
The average truck speed of 50.00 mph is proposed to be the level at which delay would exist on Interstate System highways when speeds are below this value as posted speed limits on Interstate System highways are typically 55 mph or greater. The FHWA is considering any travel speeds occurring below 50.00 mph to be representative of “congested” conditions for freight flow. The FHWA is seeking comment on the appropriateness of this speed threshold to indicate congested conditions.
In this section, FHWA describes the proposed changes to Subpart G, which would establish a performance measure for assessing traffic congestion. The discussions of the proposed requirements are organized as follows:
• Section 490.701 discusses the purpose of the subpart;
• Section 490.703 describes the applicability of the subpart;
• Section 490.705 presents the definitions;
• Section 490.707 discusses the performance measure;
• Section 490.709 describes the data requirements;
• Section 490.711 identifies how to calculate performance metric; and,
• Section 490.713 presents how to calculate performance measure.
The FHWA is required, under 23 U.S.C. 150(c), to establish performance measures for State DOTs to use to assess traffic congestion for the purpose of carrying out the CMAQ program. The FHWA proposes to establish in this subpart an excessive delay measure for State DOTs and MPOs to use to assess traffic congestion.
The FHWA proposes that the measure apply only to those portions of the NHS in urbanized areas with a population over 1 million that contain areas designated as nonattainment or maintenance areas for the O
The FHWA felt that the CMAQ Traffic Congestion measure should apply to nonattainment/maintenance areas and should relate to how the CMAQ program currently operates. Given the burden of developing multiple measures, FHWA chose to limit this measure to urbanized areas over 1 million in population, as agencies in these areas typically have more capability and experience in developing this type of measure than agencies outside of these areas. In addition, MPOs in these areas are expected to be the same MPOs that are required to report on this measure as part of the CMAQ performance plan requirements in 23 U.S.C. 149(l).
Many traffic congestion reduction projects that seek CMAQ funding use a form of a delay measure to show the benefits of traffic reduction (as well as emission reductions). This, in part, led FHWA to focus on a delay measure for the CMAQ Traffic Congestion measure, so that existing and future projects would use similar measures for analysis as the proposed national measure.
By establishing where and when the worst delay occurs on the NHS facilities in large urbanized areas where air quality is a concern, State DOTs and MPOs can better plan investments that address excessive delays and emissions reduction.
The FHWA proposes to define “Excessive Delay” as the traffic speed that causes delays that would be perceived by users as being excessive (
In section 490.707, FHWA proposes the measure of Annual Hours of Excessive Delay Per Capita, which would be used by State DOTs, MPOs, and FHWA to assess traffic congestion performance of large urbanized areas that contain nonattainment or maintenance areas for any of the criteria pollutants under the CMAQ program. The FHWA is proposing that this measure be used to establish a single target and report on traffic congestion performance for each applicable urbanized area, including those that intersect with multiple State and metropolitan planning area boundaries. This measure is being proposed because it addresses the impact of transportation projects funded under the CMAQ
In order to capture the total delay over a full year, FHWA is proposing in this subpart to use vehicle counts as a method to expand the sampling of highway average travel times to all traffic using the system. The FHWA elected to propose the use of vehicle counts as this is the most accurate and widely available information on nationwide use of the system. Including vehicle counts in the measure helps ensure the measure reflects, as closely as possible from available data, the actual amount of vehicles delayed. If FHWA proposed a measure that did not include vehicle counts, the same length of delay on a high volume road would count the same as the same length of delay on a low volume road.
As discussed in the Performance Measure Analysis section of this rulemaking, DOT considered alternatives to a highway based traffic congestion measure that would reflect the delays experienced by all travelers using all modes of surface transportation but, for the reasons discussed in this rulemaking, elected to propose only a highway based measure as a first step. After careful consideration, FHWA determined that it would be too burdensome at this time to propose requirements for State DOTs and MPOs to gather and process the data necessary to calculate measures that would be representative of travelers using all surface transportation modes. Although technologies are improving and information on system use is more available, FHWA believes that the current state of practice is not yet mature enough to propose requirements to measure, in a reliable and consistent manner, more than highway delay. Considering the current state, FHWA is proposing a measurement approach that would focus on excessive delay experienced by motor vehicles on the highway system. The FHWA is proposing that this measure is expressed as a ratio of the total excessive highway delay experienced by all traffic to the population of the applicable area. This will provide a more meaningful measure as delay is related to a typical person's experience in traveling in the urbanized area. The FHWA recognizes that other options for making the Annual Vehicle Hours of Excessive Delay understandable to the public besides dividing by urban area population may exist. The FHWA encourages comments on using “per capita” or other options.
The FHWA and DOT would like to move to a measure in the future that could be used to assess traffic congestion in a manner that reflects the experience of all travelers using the various modes of surface transportation that are available in an urbanized area. For the purpose of this rulemaking, FHWA considers any expansion of the proposed approach to be a “future” measure of traffic congestion where such a measure could additionally capture the congestion as experienced by travelers that are using other modes such as: Transit, commuter railways, walkways, and bikeways. The DOT is taking steps now to work with State DOTs, MPOs, and other surface transportation stakeholders to study and advance the technologies that could be used to move the current state of practice to capture the necessary data to support a “future” measure.
The FHWA encourages public comment on the following issues related to the measure approach and methods that can be used to realize a “future” measure of traffic congestion.
• Are there existing methods that can be used reliably to weigh the highway delay metric by “total vehicle occupants” rather than “total number of vehicles”? Are there technologies or methods that could be advanced in the next 3-5 years to capture vehicle occupancy data?
• Which surface modes of transportation, other than highways, have readily available data that could be used to support a measure to assess traffic congestion? To what extent is this information available in the urbanized areas applicable to the measure proposed in this subpart?
• What would be the appropriate surface transportation network to use to measure traffic congestion in the future? Is data available off the NHS that can be used to assess traffic congestion that can be made available to all State DOTs and MPOs?
The FHWA is proposing for State DOTs and MPOs to use a travel time data set that would meet the requirements discussed in section 490.103 of this rulemaking to calculate the metrics defined in section 490.711. State DOTs and MPOs would use the same travel time data set to assess traffic congestion for all applicable directional mainline highways on the NHS.
In section 490.709(b), FHWA is proposing for State DOTs to establish and submit reporting segments, in coordination with MPOs on the segments within metropolitan planning areas, as discussed in section 490.103 of this rulemaking. These reporting segments would be used as the basis for calculating and reporting metrics to FHWA and for calculating measures proposed in this subpart to assess traffic congestion. Reporting segments, as defined in 490.101, include one or more travel time segments, and would be contiguous so they cover the full extent of the mainline highways of the NHS in the State. The section 490.103 discussion included in this rulemaking provides more information on the proposal for State DOTs to define and submit reporting segments.
To calculate the measure, State DOTs also would need to provide estimates of hourly traffic volume that can be applied to some or all portions of the NHS in areas applicable to this measure. Traffic volumes would be needed to estimate the accumulated delay experienced by all users of the highway system. The FHWA is proposing in section 490.709(c) that State DOTs could use one of the two methods proposed in section 490.709(c)(1) to count or estimate hourly traffic volumes for each reporting segment. Examples of standard approaches to estimate hourly traffic include using AADT with k-factors or traffic profiles. The hourly traffic volumes do not have to be submitted to FHWA, but State DOTs would need to report to FHWA the method they used to estimate traffic volumes. State DOTs would need to report the method they use to FHWA no later than 60 days prior to the submittal of the first Baseline Performance Period Report. The FHWA recognizes State DOTs subsequently may change the method they used to estimate traffic volumes. Thus, FHWA proposes in section 490.709(c)(4) that if a State DOT elects to change the submitted methodology, then the State DOT would submit the changed methodology no later than 60 days prior to the submittal of next State Biennial Performance Report required in section 490.107(b).
The population of the applicable area is needed to calculate the proposed traffic congestion measure. The FHWA is proposing in section 490.709(d) that the most recently available U.S. Decennial Census population data available at the time when the State DOT Baseline Performance Period
Similarly, urbanized areas that contain nonattainment or maintenance areas would be based on the designation status at the time the State DOT Baseline Performance Period Report is due to FHWA, and that designation status would be used for the entire performance period.
The geographic areas that would be applicable to this measure would be identified in the State DOT Baseline Performance Period Report submitted to FHWA. These areas would continue to be applicable to the measure (or conversely remain “not applicable”) for the duration of the performance period regardless of changes to designation, urbanized areas, or populations that may occur during the performance period. The FHWA is proposing that the applicability of the area be determined using the most recent U.S. Decennial Census reports on area populations; the urbanized areas approved by FHWA and submitted in HPMS at the start of a performance period; and the EPA nonattainment or maintenance designations for the O
The FHWA is proposing in this section for State DOTs to calculate the Total Excessive Delay for each reporting segment and report these metrics to FHWA annually.
Section 490.711(b) contains the specific data that is required to calculate the metric and is described in more detail in the discussion of section 490.709(b). The use of the data is explained in the proposed calculation methodology.
The FHWA is proposing in section 490.711(c) through (e) the method to calculate the Total Excessive Delay as discussed below.
• 35 mph for Interstates, freeways, or expressways, and
• 15 mph for all other NHS roadways.
The FHWA defines congestion on the agency Traffic Congestion Reliability reporting Web site
The Excessive Delay Threshold Travel Time would be determined by the State DOT for each travel time segment to represent the time that it could take for a vehicle to traverse the reporting segment before excessive delay would occur. This time threshold would be determined by dividing the travel time segment length by the excessive delay threshold speed corresponding to the roadway functional level (35 mph or 15 mph) and converting the quotient to a time unit of seconds. For example, if a travel time segment on an Interstate is
The RSD, as calculated above, would result in a positive or negative amount
The FHWA is proposing for State DOTs to use estimated hourly traffic volumes to expand the travel times, determined by probing a sample of highway users, to represent the total excessive delay experienced by roadway users. An example of this proposed method is provided in Figure 9 below:
In this example, 178 highway probes were recorded (from mobile phones, vehicles, or portable navigation devices) during a 5-minute period of time which, on average, took 82 seconds to traverse a 0.50 mile long roadway segment located on a freeway. These highway users were experiencing excessive delay as the threshold time for this roadway segment is 51 seconds. For this example, the additional time experienced by each highway user as a result of being excessively delayed is estimated to be 0.009 hours. This delay per highway user is expanded to represent all traffic by multiplying the delay per user, 0.009 hours, by the estimated traffic volume during the 5 minute interval, 433.3 vehicles. The product of 3.900 vehicle-hours is the Total Excessive Delay for the 5 minute interval. The final metric for this example would then carry out this same process for every 5 minute interval through a full calendar year and for each travel time segment within the reporting segment.
The FHWA recognizes that the proposed method would apply a delay per highway user to total vehicles to identify the total excessive delay of vehicles. The FHWA elected to use this approach as it is believed that traffic volume data are the most accurate and complete data available on the use of the highways. As previously discussed,
The FHWA is proposing section 490.711(f) that would require State DOTs to report annually on the Total Excessive Delay (as measured in vehicle-hours) metric for each applicable reporting segment on the NHS. State DOTs would report the annual outcomes to the HPMS by June 15th of the following year (
• NPMRDS TMC codes or standard HPMS location referencing; and
• Total Excessive Delay metric, to the nearest one hundredth hours.
The FHWA intends to issue additional guidance on how State DOTs could report these data to HPMS. As discussed previously with respect to proposed sections 490.511 and 490.611, FHWA recognizes the level of effort to conflate travel time reporting segments to align with a referenced highway network. For this reason, FHWA is not proposing a requirement for State DOTs to conflate the travel time reporting segments to the HPMS roadway network. The FHWA intends to conduct this conflation, if needed, if State DOTs choose to report the metric by Travel Time Segment reference codes.
The FHWA is proposing the method to be used by State DOTs and MPOs to calculate the traffic congestion measure, Annual Hours of Excessive Delay Per Capita, proposed in section 490.707. The FHWA, State DOTs, and MPOs would all use this method to assess performance, establish targets, and/or report on performance. The measure would be calculated by summing the Total Excessive Delay, calculated as proposed in section 490.711, of all reporting segments in the applicable area and then dividing this total by the population for the applicable area. As discussed in section 490.703, this measure is calculated for each urbanized area with a population over 1 million that contain nonattainment or maintenance areas for any of the criteria pollutants covered under the CMAQ program. A single measure would be determined for urbanized areas that intersect with multiple State and metropolitan planning area boundaries and for each applicable area within a State boundary. For example, in the State of Maryland, based on the 2010 U.S. Decennial Census and areas designated nonattainment or maintenance at the time of this rulemaking for O
In this section, FHWA describes the proposed changes to Subpart H, which would establish a performance measure for assessing on-road mobile source emissions. The discussion of the proposed requirements is as follows:
• Section 490.801 discusses the purpose of the subpart;
• Section 490.803 describes the applicability of the subpart;
• Section 490.805 presents the definitions;
• Section 490.807 discusses the performance measure;
• Section 490.809 describes the data requirements;
• Section 490.811 identifies how to calculate performance metric;
• Section 490.813 presents how to calculate performance measure.
The FHWA is required, under 23 U.S.C. 150(c), to establish performance measures for State DOTs to assess on-road mobile source emissions for the purpose of carrying out the CMAQ program. The FHWA proposes to establish in this subpart a measure for State DOTs and MPOs to use to assess the reduction of the criteria pollutants and applicable precursors under the CMAQ program through the programming of projects.
In section 490.803(a), FHWA proposes that the on-road mobile source emissions performance measure would be applicable to State DOTs and MPOs that received funding from the CMAQ program that contain areas designated as nonattainment or maintenance for the O
Similar to the traffic congestion measure, for this measure MPOs serving urbanized areas over 1 million in population with nonattainment and maintenance areas have additional performance reporting requirements (See 23 U.S.C. 149(l)). Because of the special emphasis for these areas, FHWA proposes that these areas would be subject to the full set of performance requirements. The FHWA anticipates that MPOs serving in these areas over 1 million in population with nonattainment or maintenance areas could calculate and use the proposed performance measure to assess on-road mobile source emissions in their applicable planning area as these organizations have more experience and capability to manage their air quality program through the transportation conformity process and the implementation of the CMAQ program, including estimating emissions reductions and reporting to the CMAQ Public Access System.
In section 490.803(b), FHWA proposes that State DOTs and MPOs that do not contain any O
The FHWA proposes definitions associated with the on-road mobile source emissions performance measures that are used in the proposed regulation. It includes definitions for Donut Areas, Isolated Rural Nonattainment and Maintenance Areas, and On-Road Mobile Source.
The FHWA proposes to utilize the same definition for donut area and isolated rural nonattainment and maintenance areas, as found in the transportation conformity rule at 40 CFR 93.101. The FHWA proposes to define on-road mobile sources as emissions from vehicles that you would typically expect to find on our roadways, such as cars, trucks, and buses.
In section 490.807, FHWA proposes the measure of “Total Emissions Reduction” to assess on-road mobile source emissions. The measure will be the 2-year and 4-year cumulative reported emissions reduction resulting from CMAQ projects, by applicable criteria pollutants (O
The FHWA proposes to use the CMAQ Public Access System
State DOTs report estimated emissions reductions of CMAQ projects for the first year that a project is obligated and only the first time a project is entered into the system, not each time the project receives CMAQ funds, to avoid double counting of benefits. The quantitative emissions reduction estimates are reported for each CMAQ-funded project in kilograms (kg) per day for applicable criteria pollutants (and their precursors) for which the area is nonattainment or maintenance. These five pollutants or precursors include CO, PM
For the purpose of establishing targets in section 490.105, FHWA proposes the annual reports shall include for each project, the applicable nonattainment or maintenance area and MPO for which the project is located, and quantified emissions reductions for all applicable criteria pollutants (and their precursors) for which the area is nonattainment or maintenance. For those projects that do not include a quantified emissions reduction (
In 490.809(b), FHWA is proposing a period of approximately 120 days for FHWA to review and approve the data for publication in the CMAQ Public Access System. Considering this time allowance, FHWA is proposing that specific dates be established for when FHWA approves the State DOT's annual reports and when data are available for extraction from the CMAQ Public Access System for the purpose of implementing the on-road mobile source emissions measure. These dates are necessary in order to report the measures and establish targets in a timely manner. The FHWA is proposing the following dates:
• March 1—The FHWA is proposing that State DOTs enter their project information for a given fiscal year by March 1st of the following fiscal year; and
• July 1—The FHWA is proposing that it will make available the data necessary to calculate the on-road mobile source emissions measure will be in the CMAQ Public Access System by July 1st for project obligations in the prior fiscal year.
In 490.809(c), FHWA is proposing to identify nonattainment or maintenance areas based on the most recent effective designations made by the EPA when the State DOT Baseline Performance Period Report is due to FHWA. The areas designated at this time will remain as the areas applicable to this subpart for the duration of the performance period. For example, for a performance period that begins on October 1, 2017, and ends on September 30, 2021, FHWA would consider the designated areas as of October 1, 2018, to be those subject to this subpart even if the effective nonattainment and maintenance area designations change during the performance period after this date.
The FHWA proposes in section 490.811 the method that would be used by State DOTs and MPOs to calculate the annual emission reductions for projects reported to the CMAQ Public Access System in a Federal fiscal year. The metric would be calculated for each CMAQ-funded project and for each applicable criteria pollutant and precursor. The proposed method would convert the emissions reductions reported in the CMAQ Public Access System from units of kg per day to short tons per year: One kg per day is equal to 0.4026 short tons per year. The emissions reductions would then be summed for all projects within the applicable reporting area, by criteria pollutant or precursor, for a Federal fiscal year. The annual emissions reductions (in tons/year) would be used to calculate the performance measure proposed in section 490.813.
The FHWA proposes in section 490.813 that State DOTs and MPOs should calculate on-road mobile source emissions reductions by summing the annual tons of emissions reduced by CMAQ projects, using the 2 and 4 years of available data from the Public Access System as proposed in section 490.809 by criteria pollutant or precursor. For example, for the first proposed performance period that would begin on October 1, 2017, and end on September 30, 2021. So the 2-year total emissions reductions by criteria pollutant or applicable precursor for the performance period would reflect project data from Federal fiscal years from 2018 through 2019, and the 4-year total emissions reductions by criteria pollutant or applicable precursor for the performance period would reflect project data from Federal fiscal years from 2018 through 2021.
All comments received before the close of business on the comment closing date indicated above will be considered and available for examination in the docket at the above address. Comments received after the comment closing date will be filed in the docket and considered to the extent practicable. In addition to late comments, FHWA will also continue to file relevant information in the docket as it becomes available after the comment period closing date, and interested persons should continue to examine the docket for new material. A final rule may be published at any time after close of the comment period and after FHWA has had the opportunity to review the comments submitted.
The FHWA has determined that this proposed rule constitutes a significant regulatory action within the meaning of Executive Order 12866 and is significant within the meaning of DOT regulatory policies and procedures. This action complies with Executive Orders 12866 and 13563 to improve regulation. This action is considered significant because of widespread public interest in the transformation of the Federal-aid highway program to be performance-based, although it is not economically significant within the meaning of Executive Order 12866. The FHWA is presenting a Regulatory Impact Analysis (regulatory analysis or RIA) in support of this NPRM on National Performance Measures to Assess Performance of the National Highway System, Freight Movement on the Interstate System, and Congestion Mitigation and Air Quality Improvement Program. The regulatory analysis estimates the economic impact, in terms of costs and benefits, on Federal, State, and local governments, as well as private entities regulated under this action, as required by Executive Order 12866 and Executive Order 13563. The economic impacts are measured on an incremental basis, relative to current practices.
This section of the NPRM identifies the estimated costs and benefits resulting from the proposed rule in order to inform policy makers and the public of the relative value of the current proposal. The complete RIA may be accessed from the rulemaking's docket (FHWA-2013-0054).
The cornerstone of MAP-21's highway program transformation is the transition to a performance-based program. In accordance with the law, State DOTs would invest resources in projects to achieve performance targets that make progress toward national goal areas. The MAP-21 establishes national performance goals for system reliability, freight movement and economic vitality, and environmental sustainability. The FHWA must promulgate a rule to establish performance measures to assess performance of the Interstate System and non-Interstate NHS; assess freight movement on the Interstate System, and to carry out the CMAQ program and assess traffic congestion and on-road mobile source emissions. As required by MAP-21, this NPRM identifies the following performance measures for which State DOTs and MPOs must collect and report data, establish targets for performance, and make progress toward achievement of targets:
1. Percent of the Interstate System providing for Reliable Travel Times;
2. Percent of the non-Interstate NHS providing for Reliable Travel Times;
3. Percent of the Interstate System where peak hour travel times meet expectations;
4. Percent of the non-Interstate NHS where peak hour travel times meet expectations;
5. Percent of the Interstate System Mileage providing for Reliable Truck Travel Times;
6. Percent of the Interstate System Mileage Uncongested;
7. Annual Hours of Excessive Delay Per Capita; and
8. Cumulative emissions reduction resulting from CMAQ projects by criteria pollutant for which the area is in nonattainment or maintenance.
To estimate costs for the proposed rule, FHWA assessed the level of effort, expressed in labor hours and the labor categories, and capital needed to comply with each component of the proposed rule. Level of effort by labor category is monetized with loaded wage rates to estimate total costs.
Because there is some uncertainty regarding the availability of NPMRDS data for use by State DOTs and MPOs, FHWA estimated the cost of the proposed rule according to two scenarios. Under Scenario 1, FHWA assumes that it will provide State DOTs and MPOs with the required data from NPMRDS. Table 13 displays the total cost of the proposed rule for the 11-year
Under Scenario 2, which represents “worst case” conditions, State DOTs would choose to independently acquire the necessary data. Table 14 displays the total cost of the proposed rule for the 11-year study period (2016-2026). Total costs over 11 years are estimated to be $224.5 million undiscounted, $158.9 million discounted at 7 percent, and $192.1 million discounted at 3 percent.
The costs in Tables 14 and 15 assume a portion of MPOs will establish their own targets and a portion will adopt State DOT targets. For the performance measures that apply to all State DOTs and MPOs (
Currently, State DOTs differ from State to State in the way they evaluate the performance of the NHS, congestion, on-road mobile source emissions, and freight movement. These differences hinder accurate analysis at the national level. The proposed rulemaking would not only establish uniform performance measures, but also would establish processes that (1) State DOTs and MPOs use to report measures and establish performance targets and (2) FHWA uses to assess progress that State DOTs have made toward achieving targets.
Upon implementation, FHWA expects that the proposed rule would result in some significant benefits that are not easily monetized, but nonetheless deserve mention in this analysis. Specifically, the proposed rule would allow for more informed decisionmaking on congestion-, freight-, and air-quality-related project, program, and policy choices. The proposed rule also would yield greater accountability because the MAP-21-mandated reporting would increase visibility and transparency. In addition,
The expected benefits discussed above (
For the break-even analyses associated with enhancing the performance of the Interstate System and non-Interstate NHS, the costs associated with the following proposed rule sections are summed together to estimate the total cost of provisions aimed at reducing congestion:
• Section 490.103. Sixty percent of the cost
• Section 490.105. Approximately 63 percent of the cost
• Section 490.107. Approximately 63 percent of the cost
• Section 490.107. Approximately 63 percent of the cost
• Section 490.107. Approximately 63 percent of the cost
• Section 490.107. Half the cost
• Section 490.107. Sixty percent of the cost
• Section 490.109. Cost of assessing significant progress for NHPP measures;
• Section 490.511. Cost of calculating system performance metrics;
• Section 490.513. Cost of calculating system performance measures;
• Section 490.711. Cost of calculating congestion metric; and
• Section 490.713. Cost of calculating congestion measure.
Table 15 presents the results from the break-even analysis associated with enhancing performance of the Interstate System and non-Interstate NHS under Scenario 1 (
The results represent the passenger car travel time (in hours) that would need to be saved in order to justify the costs. The analysis shows that the proposed rule would need to result in approximately 354,000 hours of passenger car travel time saved per year, or 3.9 million hours over 11 years. To provide context, private commuters in 498 urban areas across the United States experience 5.5 billion hours of travel delay per year. As a result, the reduction represents a less than 0.01 percent decrease in the amount of travel delay per year for major U.S. urban areas.
Table 16 presents the results from the break-even analysis associated with enhancing performance of the Interstate System and non-Interstate NHS under Scenario 2 (
Table 187 presents the results from the break-even analysis associated with the Freight Movement on the Interstate System measures under Scenario 1 (
• Section 490.103. Forty percent of the cost
• Section 490.105. Twenty-five percent of the cost
• Section 490.107. Twenty-five percent of the cost
• Section 490.107. Twenty-five percent of the cost
• Section 490.107. Twenty-five percent of the cost
• Section 490.107. Forty percent of the cost
• Section 490.109. Cost of assessing significant progress for NHFP measures;
• Section 490.611. Cost of calculating freight movement metrics; and
• Section 490.613. Cost of calculating freight movement measures.
The results represent the amount of truck travel time (in hours) which would need to be saved in order to justify the costs associated with the Freight Movement on the Interstate System measures. The analysis shows that the proposed rule would need to result in approximately 168,000 hours of freight travel time saved per year, or 1.8 million hours over 11 years. This reduction represents a less than 0.1 percent decrease in the amount of freight travel delay per year for major U.S. urban areas.
Table 198 presents the results from the break-even analysis associated with the Freight Movement on the Interstate System measures under Scenario 2 (
Table 19 presents the results from the break-even analysis to estimate the reduction in pollutant tons
• Section 490.105. Approximately 13 percent of the cost
• Section 490.107. Approximately 13 percent of the cost
• Section 490.107. Approximately 13 percent of the cost
• Section 490.107. Approximately 13 percent of the cost
• Section 490.107. Half the cost
• Section 490.811. Cost of calculating emissions metric; and
• Section 490.813. Cost of calculating emissions measure.
The costs associated with the Emissions performance measure are identical under Scenario 1 and Scenario 2 because State DOTs would not need data from NPMRDS. Therefore, FHWA presents one set of results.
With the undiscounted cost of the on-road mobile source emissions requirements, the analysis estimates the savings in emission tons from automobiles that the proposed rule would need to save in order for the proposed rule to be cost-beneficial. The break-even analysis estimates that a total of 49,000 emission tons would need to be reduced throughout the 10-year study period, or approximately 4,000 tons annually. On a pollutant-specific basis, this is approximately equivalent to 410 tons of VOCs, 275 tons of NO
In compliance with the Regulatory Flexibility Act (Pub. L. 96-354, 5 U.S.C. 601-612), FHWA has evaluated the effects of this action on small entities and has determined that the action would not have a significant economic impact on a substantial number of small entities. The proposed amendment addresses the obligation of Federal funds to State DOTs for Federal-aid highway projects. The proposed rule affects two types of entities: State governments and MPOs. State governments do not meet the definition of a small entity under 5 U.S.C. 601, which have a population of less than 50,000.
The MPOs are considered governmental jurisdictions, and to qualify as a small entity they would need to serve less than 50,000 people. The MPOs serve urbanized areas with populations of 50,000 or more. As discussed in the RIA, the proposed rule is expected to impose costs on MPOs that serve populations exceeding 200,000. Therefore, the MPOs that incur economic impacts under this proposed rule do not meet the definition of a small entity.
I hereby certify that this regulatory action would not have a significant impact on a substantial number of small entities.
The FHWA has determined that this NPRM does not impose unfunded mandates as defined by the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4, March 22, 1995, 109 Stat. 48). This rule does not include a Federal mandate that may result in expenditures of $143.1 million or more in any one year (when adjusted for inflation) in 2012 dollars for either State, local, and tribal governments in the aggregate, or by the private sector. The FHWA will publish a final analysis, including its response to public comments, when it publishes a final rule. Additionally, the definition of “Federal mandate” in the Unfunded Mandates Reform Act excludes financial assistance of the type in which State, local, or tribal governments have authority to adjust their participation in the program in accordance with changes made in the program by the Federal Government. The Federal-aid highway program permits this type of flexibility.
The FHWA has analyzed this NPRM in accordance with the principles and criteria contained in Executive Order 13132. The FHWA has determined that this action does not have sufficient federalism implications to warrant the preparation of a federalism assessment. The FHWA has also determined that this action does not preempt any State law or State regulation or affect the States' ability to discharge traditional State governmental functions.
The regulations implementing Executive Order 12372 regarding intergovernmental consultation on Federal programs and activities apply to this program. Local entities should refer to the Catalog of Federal Domestic Assistance Program Number 20.205, Highway Planning and Construction, for further information.
Under the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501,
This proposed rule provides definitions and outlines processes for performance elements of this NPRM. Some burdens in this proposed rule would be realized in other reporting areas as described below. The PRA activities that are already covered by existing OMB Clearances have reference numbers for those clearances as follows:
HPMS information collection, OMB No. 2125-0028 with an expiration of May 2015 and CMAQ Program OMB 2125-0614 with an expiration date of (INSERT DATE) -. Any increase in PRA burdens caused by MAP-21 in these areas will be addressed in PRA approval requests associated with those rulemakings.
This rulemaking requires the submittal of performance reports. The DOT has analyzed this proposed rule under the PRA and has determined the following:
The FHWA invites interested persons to submit comments on any aspect of the information collection. Comments submitted on the information collection proposed in this NPRM will be summarized or included, or both, in the request for OMB approval of this information collection.
The FHWA has analyzed this action for the purpose of the National Environmental Policy Act of 1969, as amended (42 U.S.C. 4321
The FHWA has analyzed this proposed rule under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights. The FHWA does not anticipate that this proposed action would affect a taking of private property or otherwise have taking implications under Executive Order 12630.
This action meets applicable standards in §§ 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.
We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. The FHWA certifies that this action would not cause an environmental risk to health or safety that might disproportionately affect children.
The FHWA has analyzed this action under Executive Order 13175, dated November 6, 2000, and believes that the proposed action would not have substantial direct effects on one or more Indian tribes; would not impose substantial direct compliance costs on Indian tribal governments; and would not preempt tribal laws. The proposed rulemaking addresses obligations of Federal funds to State DOTs for Federal-aid highway projects and would not impose any direct compliance requirements on Indian tribal governments. Therefore, a tribal summary impact statement is not required.
The FHWA has analyzed this action under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. The FHWA has determined that this is not a significant energy action under that order and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. Therefore, a Statement of Energy Effects is not required.
The E.O. 12898 requires that each Federal agency make achieving environmental justice part of its mission by identifying and addressing, as appropriate, disproportionately high and adverse human health or environmental effects of its programs, policies, and activities on minorities and low-income populations. The FHWA has determined that this proposed rule does not raise any environmental justice issues.
The FHWA continues to assess the privacy impacts of this proposed rule as required by section 522(a)(5) of the FY 2005 Omnibus Appropriations Act,
The FHWA is proposing the use of the new NPMRDS as the data source to calculate the metrics for the seven travel time/speed based measures to ensure consistency and coverage at a national level. This private sector data set provides average travel times derived from vehicle/passenger probe data traveling on the NHS. The FHWA recognizes that probe data is an evolving field and we will continue to evaluate the privacy risks associated with its use.
An RIN is assigned to each regulatory action listed in the Unified Agenda of Federal Regulations. The Regulatory Information Service Center publishes the Unified Agenda in April and October of each year. The RIN number contained in the heading of this document can be used to cross-reference this action with the Unified Agenda.
Bridges, Highway safety, Highways and roads, Incorporation by reference, Reporting and recordkeeping requirements.
In consideration of the foregoing, FHWA proposes to amend 23 CFR part 490 as follows:
23 U.S.C. 134, 135, 148(i), and 150; 49 CFR 1.85.
Unless otherwise specified, the following definitions apply to the entire part 490:
(a)
(1) 490.309 for the condition of pavements on the Interstate System;
(2) 490.309 for the condition of pavements on the non-Interstate NHS;
(3) 490.409 for the condition of bridges on the NHS;
(4) 490.509 for the performance of the Interstate System;
(5) 490.509 for the performance of the non-Interstate NHS;
(6) 490.609 for the freight movement on the Interstate System;
(7) 490.709 for traffic congestion; and
(8) 490.809 for on-road mobile source emissions.
(b)
(c)
(d)
(e)
(1) State DOTs and MPOs shall use the same equivalent data source(s) for a calendar year; and
(2) The State DOT shall request FHWA approve the use of equivalent data source(s) no later than October 1st prior to the beginning of the calendar year in which the data source would be used to calculate metrics and FHWA would need to approve the use of that data source prior to a State DOT and MPO(s)'s implementation and use of that data source; and
(3) The State DOT shall make the equivalent data source(s) available to FHWA, on request; and
(4) The State DOT shall maintain and use a documented data quality plan to routinely check the quality and accuracy of data contained within the equivalent data source(s); and
(5) The equivalent data source(s) shall:
(i) Be used by both the State DOT and all MPOs within the State for all applicable travel time segments;
(ii) In combination with or in place of NPMRDS data, include:
(A) Contiguous segments that cover the full NHS, as defined in 23 U.S.C. 103, within the State and MPO boundary;
(B) Average travel times for at least the same number of 5 minute intervals and the same locations that would be available in the NPMRDS;
(iii) Be populated with actual measured vehicle travel times and shall not be populated with travel times derived from imputed (historic travel times or other estimates) methods;
(iv) Include, for each segment at 5 minute intervals throughout a full day (24 hours) for each day of the year, the average travel time, recorded to the nearest second, representative of at least one of the following:
(A) All traffic on each segment of the NHS;
(B) Freight vehicle traffic on each segment of the Interstate System;
(v) Include, for each segment, a recording of the time and date of each 5 minute travel time record;
(vi) Include the location (route, direction, State), length and begin and end points of each segment; and
(vii) Be available within 60 days of measurement.
(f) State DOTs, in coordination with MPOs, shall define a single set of reporting segments of the Interstate System and non-Interstate NHS for the purpose of calculating the measures specified in § 490.507, § 490.607, and § 490.707 in accordance with the following:
(1) Reporting segments shall be comprised of one or more contiguous Travel Time Segments of same travel direction;
(2) Reporting segments shall not exceed
(3) All reporting segments collectively shall be contiguous and cover the full extent of the directional mainline highways of the Interstate System and non-Interstate NHS required for reporting the measure.
(g) State DOTs shall submit their defined reporting segments to FHWA no later than November 1st prior to the beginning of a calendar year. If a State DOT is using an approved equivalent travel time data source during the performance period, the State DOT shall resubmit a new set of defined reporting segments that corresponds to the equivalent travel time data source. The State DOT shall submit the following to FHWA in HPMS:
(1) The Travel Time segment/s that make up each reporting segment; and
(2) The route and length (to the nearest thousandth of a mile) of each reporting segment; and
(3) The Desired Peak Period Travel Times (both morning and evening) that will be used to calculate the Peak Hour Travel Time measures identified in § 490.507(b) for each reporting segment that is fully included within urbanized areas with populations over one million.
(4) Documentation of the State DOT and applicable MPOs coordination and agreement on the travel time data set, the defined reporting segments, and the desired travel times submitted.
(5) If the defined reporting segments contain segments using equivalent data set, in part or in whole, all reporting
(a)
(b)
(c)
(1) 490.307(a)(1) and 490.307(a)(2) for the condition of pavements on the Interstate System;
(2) 490.307(a)(3) and 490.307(a)(4) for the condition of pavements on the National Highway System (NHS) (excluding the Interstate);
(3) 490.407(c)(1) and 490.407(c)(2) for the condition of bridges on the NHS;
(4) 490.507(a)(1) and 490.507(a)(2) for the NHS travel time reliability;
(5) 490.507(b)(1) and 490.507(b)(2) for the peak hour travel time;
(6) 490.607(a) and 490.607(b) for the freight movement on the Interstate System;
(7) 490.707 for traffic congestion; and
(8) 490.807 for on-road mobile source emissions.
(d)
(1) State DOTs and MPOs shall establish Statewide and metropolitan planning area wide targets, respectively, that represent the condition/performance of the transportation network or geographic area that are applicable to the measures, as specified in 23 CFR sections—
(i) 490.303 for the condition of pavements on the Interstate System measures specified in § 490.307(a)(1) and § 490.307(a)(2);
(ii) 490.303 for the condition of pavements on the National Highway System (NHS) (excluding the Interstate) measures specified in § 490.307(a)(3) and § 490.307(a)(4);
(iii) 490.403 for the condition of bridges on the NHS measures specified in § 490.407(c)(1) and § 490.407(c)(2);
(iv) 490.503(a)(1) for NHS travel time reliability measures specified in § 490.507(a)(1) and § 490.507(a)(2);
(v) 490.603 for the freight movement on the Interstate System measures specified in § 490.607(a) and § 490.607(b); and
(vi) 490.803 for the on-road mobile source emissions measure identified in § 490.807.
(2) State DOTs and MPOs shall establish a single urbanized area target that represents the performance of the transportation network in each area applicable to the measures, as specified in 23 CFR sections—
(i) 490.503(a)(2) for the peak hour travel time measures identified in § 490.507(b)(1) and § 490.507(b)(2); and
(ii) 490.703 for the traffic congestion measure identified in § 490.707.
(3) For the purpose of target establishment in this section, reporting targets and progress evaluation in § 490.107 and significant progress determination in § 490.109, State DOTs shall declare and describe the NHS limits and urbanized area boundaries within the State boundary in the Baseline Performance Period Report required by § 490.107(b)(1). Any changes in NHS limits or urbanized area boundaries during a performance period would not be accounted for until the following performance period.
(e) State DOTs shall establish targets for each of the performance measures identified in paragraph (c) of this section for respective target scope identified in paragraph (d) of this section as follows:
(1)
(2)
(3)
(i) A State DOT shall declare and describe in the Baseline Performance Period Report required by § 490.107(b)(1) the boundaries used to establish each additional target. Any changes in boundaries during a performance period would not be accounted for until the following performance period.
(ii) State DOTs may select any number and combination of urbanized area boundaries and may also select a non-urbanized area boundary for the establishment of additional targets.
(iii) The boundaries used by the State DOT for additional targets shall be contained within the geographic boundary of the State.
(iv) State DOTs shall evaluate separately the progress of each additional target and report that progress as required under § 490.107(b)(2)(ii)(B) and § 490.107(b)(3)(ii)(B).
(v) Additional targets for urbanized areas and the non-urbanized area are not applicable to the peak hour travel time measures, traffic congestion measures, and on-road mobile source emissions measures in paragraphs (c)(5), (c)(7), and (c)(8) of this section, respectively.
(4)
(i) The performance period will begin on:
(A) January 1st of the year in which the Baseline Performance Period Report is due to FHWA and will extend for a duration of 4 years for the measures in paragraphs (c)(1) through (c)(7) of this section; and
(B) October 1st of the year prior to which the Baseline Performance Report is due to FHWA and will extend for a duration of 4 years for the measure in paragraph (c)(8) of this section.
(ii) The midpoint of a performance period will occur 2 years after the beginning of a performance period described in paragraph (e)(4)(i) of this section.
(iii) Except as provided in paragraphs (e)(7) and (e)(8)(vi) of this section, State DOTs shall establish 2-year targets that reflect the anticipated condition/performance level at the midpoint of each performance period for the measures in paragraphs (c)(1) through (c)(7) of this section, and the anticipated cumulative emissions reduction to be reported for the first 2 years of a performance period by applicable criteria pollutant and precursor for the
(iv) State DOTs shall establish 4-year targets that reflect the anticipated condition/performance level at the end of each performance period for the measures in paragraphs (c)(1) through (c)(7) of this section, and the anticipated cumulative emissions reduction to be reported for the entire performance period by applicable criteria pollutant and precursor for the measure in paragraph (c)(8) of this section.
(5)
(6)
(7)
(i) State DOTs shall establish their 4-year targets, required under paragraph (4)(iv), and report these targets in their Baseline Performance Period Report, required under § § 490.107(b)(1);
(ii) State DOTs shall not report 2-year targets, described in paragraph (e)(4)(iii) of this section, and baseline condition/performance in their Baseline Performance Period Report; and
(iii) State DOTs shall use the 2-year condition/performance in their Mid Performance Period Progress Report, described in § 490.107(b)(2)(ii)(A) as the baseline condition/performance. State DOTs may also adjust their 4-year targets, as appropriate.
(iv) State DOTs shall annually report metrics for all mainline highways on the NHS throughout the performance period, as required in § 490.511(d).
(8)
(i) State DOTs, with mainline highways on the Interstate System that cross any part of an urbanized area with a population more than 1 million within its geographic State boundary, shall establish target for the measure specified in § 490.507(b)(1) for the urbanized area. State DOTs, with mainline highways on the non-Interstate NHS that cross any part of an urbanized area with a population more than 1 million within its geographic State boundary, shall establish target for the measure specified in § 490.507(b)(2) for the urbanized area.
(ii) If any part of the urbanized area for either of the peak hour travel time measures, provided for in paragraph (i) of this section, contains any part of a nonattainment or maintenance area for any one of the criteria pollutants, as specified in § 490.703, then that State DOT shall establish targets for the measure specified in § 490.707.
(iii) If required to establish a target for a peak-hour travel time measure, as described in paragraph (e)(8)(i) of this section and/or a target for a traffic congestion measure, as described in paragraph (e)(8)(ii), State DOTs shall comply with the following:
(A) For each urbanized area, only one 2-year target and one 4-year target for the entire urbanized area shall be established regardless of roadway ownership.
(B) For each urbanized area, all State DOTs and MPOs that contain, within their respective boundaries, any portion of the NHS network in that urbanized area shall agree on one 2-year and one 4-year target for that urbanized area. The targets reported, in accordance with § 490.105(e)(5) and § 490.105(f)(7), by the State DOTs and MPOs for that urbanized area shall be identical.
(C) State DOTs shall meet all reporting requirements in § 490.107 for the entire performance period even if there is a change of population, NHS designation, or nonattainment/maintenance area designation during that performance period.
(D) The 1 million population threshold, in paragraph (e)(8)(i) of this section, shall be determined based on the most recent U.S. Decennial Census available at the time when the State DOT Baseline Performance Period Report is due to FHWA.
(E) NHS designations, in paragraphs (e)(8)(i) and (ii) of this section, shall be determined from the State DOT Baseline Performance Period Report required in § 490.107(b)(1)(ii)(E).
(F) The designation of nonattainment or maintenance areas, in paragraph of (ii) of this section, shall be determined based on the effective date of U.S. Environmental Protection Agency's designation under the NAAQS in 40 CFR part 81 at the time when the State DOT Baseline Performance Period Report is due to FHWA.
(iv) If a State DOT does not meet the criteria specified in paragraph (e)(8)(i) of this section for both peak-hour travel time measures at the time when the State DOT Baseline Performance Period Report is due to FHWA, then that State DOT is not required to establish targets for traffic congestion measure for that performance period.
(v) If a State DOT does not meet the criteria specified in paragraph (ii) at the time when the State DOT Baseline Performance Period Report is due to FHWA, then that State DOT is not required to establish targets for the traffic congestion measure for that performance period.
(vi) The following requirements apply only to the first performance period and the traffic congestion measure in § 490.707:
(A) State DOTs shall establish their 4-year targets, required under paragraph § 490.105(e)(4)(iv), and report these targets in their Baseline Performance Period Report, required under § 490.107(b)(1);
(B) State DOTs shall not report 2-year targets, described in § 490.105(e)(4)(ii) of this section, and baseline condition/performance in their Baseline Performance Period Report; and
(C) State DOTs shall use the 2-year condition/performance in their Mid Performance Period Progress Report, described in § 490.107(b)(2)(ii)(A) as the baseline condition/performance. The established baseline condition/performance shall be collectively developed and agreed upon with relevant MPOs.
(D) State DOTs may, as appropriate, adjust their 4-year target(s) in their Mid Performance Period Progress Report, described in § 490.107(b)(2)(ii)(A). Adjusted 4-year target(s) shall be developed and collectively agreed upon with relevant MPO(s), as described in paragraph (e)(6) of this section.
(E) State DOTs shall annually report metrics for all mainline highways on the NHS for all applicable urbanized area(s) throughout the performance period, as required in § 490.711(f).
(9)
(i) The State DOTs shall establish statewide targets for the on-road mobile source emissions measure for all nonattainment and maintenance areas for all applicable criteria pollutants and precursors specified in § 490.803.
(ii) For all nonattainment and maintenance areas within the State geographic boundary, the State DOT shall establish separate statewide targets for each of the applicable criteria pollutants and precursors.
(iii) The established targets, as specified in paragraph (e)(4) of this section, shall reflect the anticipated cumulative emissions reduction to be reported in the CMAQ Public Access System required in § 490.809(a).
(iv) In addition to the statewide targets in paragraph (e)(9)(i) of this section, State DOTs may, as appropriate, establish additional targets for any number and combination of nonattainment and maintenance areas by applicable criteria pollutant within the geographic boundary of the State. If a State DOT establishes additional targets for nonattainment and maintenance areas, it shall report the targets in the Baseline Performance Period Report required by § 490.107(b)(1). State DOTs shall evaluate separately the progress of each of these additional targets and report that progress as required under § 490.107(b)(2)(ii)(B) and § 490.107(b)(3)(ii)(B).
(v) The designation of nonattainment or maintenance areas shall be determined based on the effective date of U.S. Environmental Protection Agency's designation under the NAAQS in 40 CFR part 81 at the time when the State DOT Baseline Performance Period Report is due to FHWA.
(vi) The State DOT shall meet all reporting requirements in § 490.107 for the entire performance period even if there is a change of nonattainment or maintenance area designation status during that performance period.
(vii) If a State geographic boundary does not contain any part of nonattainment or maintenance areas for applicable criteria pollutants and precursors at the time when the State DOT Baseline Performance Period Report is due to FHWA, then that State DOT is not required to establish targets for on-road mobile source emissions measures for that performance period.
(f) The MPOs shall establish targets for each of the performance measures identified in paragraph (c) of this section for the respective target scope identified in paragraph (d) of this section as follows:
(1)
(i) The MPOs shall establish 4-year targets, described in paragraph (e)(4)(iv) of this section, for all applicable measures, described in paragraphs (c) and (d) of this section.
(ii) Except as provided in paragraph (f)(4)(vi) of this section, the MPOs shall establish 2-year targets, described in paragraph (e)(4)(iii) of this section for the peak hour travel time, traffic congestion and on-road source emissions measures, described in paragraphs (c) and (d) of this section as their applicability criteria described in paragraphs (f)(4)(i), (f)(4)(ii), and (f)(5)(iii) of this section, respectively.
(iii) If an MPO does not meet the criteria described in paragraphs (f)(4)(i), (f)(4)(ii), or (f)(5)(iii) of this section, the MPO is not required to establish 2-year target(s) for the corresponding measure(s).
(2)
(3)
(i) Agreeing to plan and program projects so that they contribute toward the accomplishment of the relevant State DOT target for that performance measure; or
(ii) Committing to a quantifiable target for that performance measure for their metropolitan planning area.
(4)
(i) MPOs shall establish targets for the measure specified in § 490.507(b)(1) when mainline highways on the Interstate System within their metropolitan planning area boundary cross any part of an urbanized area with a population more than 1 million. MPOs shall establish targets for the measure specified in § 490.507(b)(2) when mainline highways on the non-Interstate NHS within their metropolitan planning area boundary cross any part of an urbanized area with a population more than 1 million.
(ii) MPOs shall establish targets for the measure specified in § 490.707 when mainline highways on the NHS within their metropolitan planning area boundary cross any part of an urbanized area with a population more than 1 million, and that portion of their metropolitan planning area boundary also contains any portion of a nonattainment or maintenance area for any one of the criteria pollutants, as specified in § 490.703. If an MPO is not required to establish a target for the measure specified in § 490.707, but any part of the urbanized area for either of the peak hour travel time measures, provided for in paragraph (i) of this section, contains any part of a nonattainment or maintenance area for any one of the criteria pollutant, as specified in § 490.703, then that MPO should coordinate with relevant State DOT(s) and MPO(s) in the target establishment process for the measure specified in § 490.707.
(iii) If required to establish a target for a peak-hour travel time measure, as described in paragraph (f)(4)(i) of this section and/or traffic congestion measure, as described in paragraph (f)(4)(ii), MPOs shall comply with the following:
(A) For each urbanized area, only one 2-year target and one 4-year target for the entire urbanized area shall be established regardless of roadway ownership.
(B) For each urbanized area, all State DOTs and MPOs that contain, within their respective boundaries, any portion of the NHS network in that urbanized area shall agree on one 2-year and one 4-year target for that urbanized area. The targets reported, in accordance with § 490.105(e)(5) and § 490.105(f)(7), by the State DOTs and MPOs for that urbanized area shall be identical.
(C) MPOs shall meet all reporting requirements in § 490.107(c) for the entire performance period even if there is a change of population, NHS designation, or nonattainment/maintenance area designation status during that performance period.
(D) The 1 million population threshold, in paragraph (f)(4)(i) of this section, shall be determined based on the most recent U.S. Decennial Census available at the time when the State DOT Baseline Performance Period Report is due to FHWA.
(E) NHS designations, in paragraphs (f)(4)(i) and (ii) of this section, shall be
(F) The designation of nonattainment or maintenance areas, in paragraph (f)(4)(ii) of this section, shall be determined based on the effective date of U.S. Environmental Protection Agency's designation under the NAAQS in 40 CFR part 81 at the time when the State DOT Baseline Performance Period Report is due to FHWA.
(iv) If an MPO does not meet the criteria specified in paragraph (f)(4)(i) of this section at the time when the State DOT Baseline Performance Period Report is due to FHWA, then that MPO is not required to establish targets for the peak hour travel time measure for that performance period.
(v) If an MPO does not meet the criteria specified in paragraph (f)(4)(ii) of this section at the time when the State DOT Baseline Performance Period Report is due to FHWA, then that MPO is not required to establish targets for the traffic congestion measure for that performance period.
(vi) The following requirements apply only to the first performance period and the traffic congestion measure in § 490.707:
(A) The MPOs shall not report 2-year targets, described in paragraph (f)(4)(iii)(A) of this section,
(B) The MPOs shall use the 2-year condition/performance in State DOT Mid Performance Period Progress Report, described in § 490.107(b)(2)(ii)(A) as baseline condition/performance. The established baseline condition/performance shall be agreed upon and made collectively with relevant State DOTs.
(C) The MPOs may, as appropriate, adjust their 4-year target(s). Adjusted 4-year target(s) shall be collectively developed and agreed upon with all relevant State DOT(s), as described in paragraph (f)(7) of this section.
(5)
(i) The MPO shall establish targets for each of the applicable criteria pollutants and precursors, specified in § 490.803, for which it is in nonattainment or maintenance, within its metropolitan planning area boundary.
(ii) The established targets, as specified in paragraph (e)(4) of this section, shall reflect the anticipated cumulative emissions reduction to be reported in the CMAQ Public Access System required in § 490.809(a).
(iii) If any part of a designated nonattainment and maintenance area within the metropolitan planning area overlaps the boundary of an urbanized area with a population more than 1 million in population, then that MPO shall establish both 2-year and 4-year targets for their metropolitan planning area.
(iv) For the nonattainment and maintenance areas within the metropolitan planning area that do not meet the criteria in paragraph (f)(5)(iii) of this section, MPOs shall establish 4-year targets for their metropolitan planning area, as described in paragraph (f)(3) of this section.
(v) The designation of nonattainment or maintenance areas shall be determined based on the effective date of U.S. Environmental Protection Agency's designation under the NAAQS in 40 CFR part 81 at the time when the State DOT Baseline Performance Period Report is due to FHWA.
(vi) The MPO shall meet all reporting requirements in § 490.107(c) for the entire performance period even if there is a change of nonattainment or maintenance area designation status or population during that performance period.
(vii) If a metropolitan planning area boundary does not contain any part of nonattainment or maintenance areas for applicable criteria pollutants and precursors at the time when the State DOT Baseline Performance Period Report is due to FHWA, then that MPO is not require to establish targets for on-road mobile source emissions measures for that performance period.
(6)
(i) Agree to plan a program of projects so that they contribute to the adjusted State DOT target for that performance measure; or
(ii) Commit to a new quantifiable target for that performance measure for its metropolitan planning area.
(7)
(8)
(a)
(1) All State DOTs and MPOs shall report in accordance with the schedule and content requirements under paragraphs (b) and (c) of this section, respectively.
(2) For the measures identified in § 490.207(a), all State DOTs and MPO shall report on performance in accordance with § 490.213.
(3) State DOTs shall report using an electronic template provided by FHWA.
(4)
(i) The condition/performance of the NHS in the State for measures where the State DOT is required to establish targets and where data is available;
(ii) The effectiveness of the investment strategy document in the State asset management plan for the National Highway System;
(iii) Progress toward targets the State DOT are to establish, which may only be a description of how State DOTs are coordinating with relevant MPOs and other agencies in target selection for the targets to be reported in the first State Biennial Performance Report in 2018; and
(iv) The ways in which the State is addressing congestion at freight bottlenecks, including those identified in the National Freight Strategic Plan, within the State.
(5) State DOTs shall report initial 2-year and 4-year targets, as described in § 490.105(e)(4), to FHWA within 30 days of target establishment by either amending the Initial State Performance Report due in October 2016, or through the Baseline Performance Report for the
(b)
(1)
(i)
(ii)
(A)
(B)
(C)
(D)
(E)
(F)
(G)
(H)
(2)
(i)
(ii)
(A)
(B)
(C)
(D)
(E)
(F)
(G)
(H)
(I)
(3)
(i)
(ii)
(A)
(B)
(C)
(D)
(E)
(F)
(G)
(H)
(c)
(1) The MPOs shall report their established targets to their respective State DOT in a manner that is documented and mutually agreed upon by both parties.
(2) The MPOs shall report baseline condition/performance and progress toward the achievement of their targets in the system performance report in the metropolitan transportation plan in accordance with Part 450 of this chapter.
(3) MPOs serving a TMA with a population over one million representing nonattainment and maintenance areas for ozone, CO, or PM NAAQS shall develop a CMAQ performance plan as required by 23 U.S.C. 149(l). The CMAQ performance plan is not required when the MPO does not serve a TMA with a population over one million; the MPO is attainment for ozone, CO, and PM NAAQS; or the MPO's nonattainment or maintenance area for ozone, CO, or PM NAAQS is outside the urbanized area boundary of the TMA with a population over one million.
(i) The CMAQ performance plan shall be submitted as a separate section attached to the State Biennial Performance Reports, as required under § 490.107(b), and be updated biennially on the same schedule as the State Biennial Performance Reports.
(ii) For traffic congestion and on-road mobile source emissions measures in Subparts G and H, the CMAQ performance plan submitted with the State DOT's Baseline Performance Period Report shall include:
(A) The 2-year and 4-year targets for the traffic congestion measure, identical to the relevant State DOT(s) reported target under paragraph (b)(1)(ii)(A) of this section, for each applicable urbanized area;
(B) The 2-year and 4-year targets for the on-road mobile source emissions measure for the performance period;
(C) Baseline condition/performance for each MPO reported traffic congestion target, identical to the relevant State DOT(s) reported baseline condition/performance under paragraph (b)(1)(ii)(B) of this section;
(D) Baseline condition/performance derived from the latest estimated cumulative emissions reductions from CMAQ projects for each MPO reported on-road mobile source emissions target; and
(E) A description of projects identified for CMAQ funding and how such projects will contribute to achieving the performance targets for these measures.
(iii) For traffic congestion and on-road mobile source emissions measures in Subparts G and H, the CMAQ performance plan submitted with the State DOT's Mid Performance Period Progress Report shall include:
(A) 2-year condition/performance for the traffic congestion measure, identical to the relevant State DOT(s) reported condition/performance under paragraph (b)(2)(ii)(A) of this section, for each applicable urbanized area;
(B) 2-year condition/performance derived from the latest estimated cumulative emissions reductions from CMAQ projects for each MPO reported on-road mobile source emissions target;
(C) An assessment of the progress of the projects identified in the CMAQ performance plan submitted with the Baseline Performance Period Report toward achieving the 2-year targets for these measures;
(D) When applicable, an adjusted 4-year target to replace an established 4-year target; and
(E) An update to the description of projects identified for CMAQ funding and how those updates will contribute to achieving the 4-year performance targets for these measures.
(iv) For traffic congestion and on-road mobile source emissions measures in Subparts G and H, the CMAQ performance plan submitted with the State DOT's Full Performance Period Progress Report shall include:
(A) 4-year condition/performance for the traffic congestion measure, identical to the relevant State DOT(s) reported condition/performance reported under paragraph (b)(3)(ii)(A) of this section, for each applicable urbanized area;
(B) 4-year condition/performance derived from the latest estimated cumulative emissions reductions from CMAQ projects for each MPO reported on-road mobile source emissions target; and
(C) An assessment of the progress of the projects identified in both paragraphs (c)(3)(ii)(C) and (c)(3)(iii)(D) of this section toward achieving the 4-year targets for these measures.
(a)
(b)
(c)
(d)
(1) The FHWA will use the following sources of information to assess NHPP condition and performance progress:
(i) Data contained within the HPMS on June 15 of the year in which the significant progress determination is made that represents conditions from the prior year for targets established for Interstate System pavement condition measures, as specified in § 490.105(c)(1);
(ii) Data contained within the HPMS on August 15 of the year in which the significant progress determination is made that represents conditions from the prior year for targets established for non-Interstate NHS pavement condition measures, as specified in § 490.105(c)(2);
(iii) The most recently available data contained within the NBI as of June 15 of the year in which the significant progress determination is made for targets established for NHS bridge condition measures, as specified in § 490.105(c)(3);
(iv) The urbanized area boundary and NHS limit data in the HPMS as documented in the Baseline Performance Period Report specified in § § 490.107(b)(1)(ii)(D) and (E);
(v) Data contained within the HPMS on August 15 of the year in which the significant progress determination is made that represents performance from the prior year for targets established for the Interstate System and non-Interstate NHS performance measures, as specified in § 490.105(c)(4) and (5); and
(vi) Population data as defined by the most recent U.S. Decennial Census for urbanized areas available at the time when the State DOT Baseline Performance Period Report is due to FHWA.
(2) The FHWA will use the data contained within the HPMS on August 15 of the year in which the significant progress determination is made that represents performance from the prior year for targets established for NHFP measures, as specified in § 490.105(c)(6), to assess NHFP targets and performance progress.
(e)
(1)
(2)
(i) The actual condition/performance level is better than the baseline condition/performance reported in the State DOT Baseline Performance Period Report; or
(ii) The actual condition/performance level is equal to or better than the established target.
(3)
(i) At the midpoint of the first performance period, FHWA will not make a determination of significant progress toward the achievement of 2-year targets for Interstate System pavement condition measures.
(ii) The FHWA will classify the assessment of progress toward the achievement of targets in paragraph (e)(3)(i) of this section as “progress not determined” so that they will be excluded from the requirement under paragraph (e)(2) of this section.
(iii) FHWA will not make a determination of significant progress toward the achievement of 2-year targets for non-Interstate NHS travel time reliability measure.
(4)
(5)
(i) The FHWA will classify the assessment of progress toward the achievement of an individual 2-year or 4-year target as “progress not determined” if the State DOT has provided an explanation of the extenuating circumstances beyond the control of the State DOT that prevented
(A) Natural or man-made disasters that caused delay in NHPP or NHFP project delivery, extenuating delay in data collection, and/or damage/loss of data system;
(B) Sudden discontinuation of Federal government furnished data due to natural and man-made disasters or lack of funding; and/or
(C) New law and/or regulation directing State DOTs to change metric and/or measure calculation.
(ii) If the State DOT's explanation, described in paragraph (e)(5)(i) of this section, is accepted by FHWA, FHWA will classify the progress toward achieving the relevant target(s) as “progress not determined,” and those targets will be excluded from the requirement in paragraph (e)(2) of this section.
(f)
(1) If FHWA determines that a State DOT has not made significant progress toward the achieving of NHPP targets, then the State DOT shall include as part of the next performance target report under section 150(e) [the Biennial Performance Report] a description of the actions the State DOT will undertake to achieve the targets related to the measure in which significant progress was not achieved as follows:
(i) If significant progress is not made for either target established for the Interstate System pavement condition measures, § 490.307(a)(1) and § 490.307(a)(2), then the State DOT shall document the actions they will take to improve Interstate Pavement conditions;
(ii) If significant progress is not made for either target established for the Non-Interstate System pavement condition measures, § 490.307(a)(3) and § 490.307(a)(4), then the State DOT shall document the actions they will take to improve Non-Interstate Pavement conditions;
(iii) If significant progress is not made for either target established for the NHS bridge condition measures, § 490.407(c)(1) and § 490.407(c)(2), then the State DOT shall document the actions they will take to improve the NHS bridge conditions;
(iv) If significant progress is not made for either target established for the NHS travel time reliability measures, § 490.507(a)(1) and § 490.407(a)(2), then the State DOT shall document the actions they will take to achieve the NHS travel time targets;
(v) If significant progress is not made for either urbanized area specific target, described in § 490.105(e)(8), established for the peak hour travel measures, § 490.507(b)(1) and § 490.407(b)(2) for an urbanized area, then the State DOT shall document the actions they will take to achieve both the Interstate and non-Interstate NHS peak hour travel time targets that urbanized area;
(2) If FHWA determines that a State DOT has not made significant progress toward achieving the NHFP targets established for either of the NHFP measures in § 490.607(a) or § 490.607(b), then the State DOT shall include as part of the next performance target report under section 150(e) [the Biennial Performance Report], a description of the action the State will undertake to achieve the targets, including—
(i) An identification of significant freight system trends, needs, and issues within the State;
(ii) A description of the freight policies and strategies that will guide the freight-related transportation investments of the State;
(iii) An inventory of freight bottlenecks within the State and a description of the ways in which the State DOT is allocating national highway freight program funds to improve those bottlenecks; and
(iv) A description of the actions the State DOT will undertake to achieve the targets established for the Freight measures in § 490.607(a) and § 490.607(b).
(3) The State DOT should, within 6 months of the significant progress determination, amend its Biennial Performance Report to document the information specified in this paragraph to ensure actions are being taken to achieve targets.
(a) Certain material is incorporated by reference into this subpart with the approval of the Director of the Federal Register under 5 U.S.C. 552(a) and 1 CFR part 51. To enforce any edition other than that specified in this section, FHWA must publish a document in the
(b) The Federal Highway Administration, 1200 New Jersey Avenue SE., Washington, DC 20590,
(1) Highway Performance Monitoring System (HPMS) Field Manual, IBR approved for Subparts A through C, and E through G.
(2) Recording and Coding Guide for the Structure Inventory and Appraisal of the Nation's Bridges, Report No. FHWA-PD-96-001, December 1995 and errata, IBR approved for Subpart D.
(c) The American Association of State Highway and Transportation Officials, 444 North Capitol Street NW., Suite 249, Washington, DC 20001, (202) 624-5800,
(1) AASHTO Standard M328-14, Standard Specification for Transportation Materials and Methods of Sampling and Testing, Standard Equipment Specification for Inertial Profiler, 2014, 34th/2014 Edition, AASHTO, 1-56051-606-4, IBR approved for Subpart C.
(2) AASHTO Standard R57-14, Standard Specification for Transportation Materials and Methods of Sampling and Testing, Standard Practice for Operating Inertial Profiling Systems, 2014, 34th/2014 Edition, AASHTO, 1-56051-606-4, IBR approved for Subpart C.
(3) AASHTO Standard R55-10 (2013), Standard Specification for Transportation Materials and Methods of Sampling and Testing, Standard Practice for Quantifying Cracks in Asphalt Pavement Surface, 2014, 34th/2014 Edition, AASHTO, 1-56051-606-4, IBR approved for Subpart C.
(4) AASHTO Standard PP67-14, Standard Specification for Transportation Materials and Methods of Sampling and Testing, Standard Practice for Quantifying Cracks in Asphalt Pavement Surfaces from Collected Images Utilizing Automated Methods, 2014, 34th/2014 Edition, AASHTO, 1-56051-606-4, IBR approved for Subpart C.
(5) AASHTO Standard PP68-14, Standard Specification for Collecting Images of Pavement Surfaces for Distress Detection, 2014, 34th/2014 Edition, AASHTO, 1-56051-606-4, IBR approved for Subpart C.
(6) AASHTO Standard R48-10 (2003), Standard Specification for Transportation Materials and Methods of Sampling and Testing, Standard Practice for Determining Rut Depth in Pavements, 2014, 34th/2014 Edition, AASHTO, 1-56051-606-4, IBR approved for Subpart C.
(7) AASHTO Standard PP69-14, Standard Specification for Transportation Materials and Methods of Sampling and Testing, Standard Practice for Determining Pavement Deformation Parameters and Cross Slope from Collected Transverse Profiles, 2013, 2014, 34th/2014 Edition, AASHTO, 1-56051-606-4, IBR approved for Subpart C.
(8) AASHTO Standard PP70-14, Standard Specification for Transportation Materials and Methods of Sampling and Testing, Standard Practice for Collection the Transverse Pavement Profile, 2014, 34th/2014 Edition, AASHTO, 1-56051-606-4, IBR approved for Subpart C.
(9) AASHTO Standard R36-13, Standard Specification for Transportation Materials and Methods of Sampling and Testing, Standard Practice for Evaluating Faulting of Concrete Pavements, 2014, 34th/2014 Edition, AASHTO, 1-56051-606-4, IBR approved for Subpart C.
(10) AASHTO Standard R43-13, Standard Specification for Transportation Materials and Methods of Sampling and Testing, Standard Practice for Quantifying Roughness of Pavement, 2014, 34th/2014 Edition, AASHTO, 1-56051-606-4, IBR approved for Subpart C.
The purpose of this subpart is to implement the requirements of 23 U.S.C. 150(c)(3)(A)(ii)(IV) and (c)(3)(A)(ii)(V) to establish performance measures for State Departments of Transportation (State DOTs) and Metropolitan Planning Organizations (MPOs) to use to assess:
(a) Performance of the Interstate System; and
(b) Performance of the non-Interstate National Highway System (NHS).
(a) The performance measures are applicable to those portions of the mainline highways on the NHS as provided below (and in more detail in § 490.507):
(1) The Reliability measures in § 490.507(a) are applicable to all directional mainline highways on the Interstate System and non-Interstate NHS.
(2) The Peak Hour Travel Time measures in § 490.507(b) are applicable to all directional mainline highways on the Interstate System and non-Interstate NHS that are within the boundary of urbanized areas with a population over one million.
All definitions in § 490.101 apply to this subpart. Unless otherwise specified in this subpart, the following definitions apply:
There are four performance measures to assess the performance of the Interstate System and the performance of the non-Interstate NHS for the purpose of carrying out the National Highway Performance Program.
(a) Two measures are used to assess Reliability. They are:
(1) Percent of the Interstate System providing for Reliable Travel Times; and
(2) Percent of the non-Interstate NHS providing for Reliable Travel Times.
(b) Two measures are used to assess Peak Hour Travel Time in urbanized areas over 1,000,000 in population. They are:
(1) Percent of the Interstate System where Peak Hour Travel Times meet expectations; and
(2) Percent of the non-Interstate NHS where Peak Hour Travel Times meet expectations.
(a) Travel time data needed to calculate the measures in § 490.507 shall come from the Travel Time Data Set, as specified in § 490.103(e).
(1) State DOTs, in coordination with MPOs, shall define reporting segments in accordance with § 490.103(f) and submit the reporting segments in accordance with § 490.103(g). Reporting segments must be contiguous so that they cover the full extent of the mainline highways of the NHS in the State.
(2) [Reserved]
(b) State DOTs shall use posted speed limit data to calculate travel times when data is not available in the Travel Time Data Set (data not reported, or reported as “0” or null) as specified in § 490.511(b)(1)(v).
(c) Populations of urbanized areas shall be as identified based on the most recent U.S. Decennial Census available at the time when the State DOT Baseline Performance Period Report is due to FHWA. State DOTs and MPOs shall use this population to identify areas that are applicable to the Peak Hour Travel Time measure as specified in § 490.503.
(a) Two performance metrics are required for the measures specified in § 490.507. These are:
(1) Level of Travel Time Reliability (LOTTR)
(2) Peak Hour Travel Time Ratio (PHTTR)
(b) The State DOT shall calculate the LOTTR metrics for each NHS reporting segment in accordance with the following:
(1) Data sets shall be created from the Travel Time Data Set to be used to calculate the LOTTR metrics. This data set shall include, for each reporting segment, a ranked list of average travel times for all traffic (“all vehicles” in NPMRDS nomenclature), to the nearest second, for 5 minute periods of a population that:
(i) Includes travel times occurring between the hours of 6:00 a.m. and 10:00 a.m. for every weekday (Monday-Friday) from January 1st through December 31st of the same year;
(ii) Includes travel times occurring between the hours of 10:00 a.m. and 4:00 p.m. for every weekday (Monday-Friday) from January 1st through December 31st of the same year;
(iii) Includes travel times occurring between the hours of 4:00 p.m. and 8:00 p.m. for every weekday (Monday-Friday) from January 1st through December 31st of the same year;
(iv) Includes travel times occurring between the hours of 6:00 a.m. and 8:00 p.m. for every weekend day (Saturday-Sunday) from January 1st through December 31st of the same year; and
(v) Any travel time for Travel Time segments contained within a reporting segment that are not reported, or reported as “0” or null shall be replaced with the calculated travel time for that segment, based on the segment length and posted speed limit (TT@PSL), rounded to the nearest second.
(2) The Normal Travel Time (50th percentile) shall be determined from each data set defined under paragraph (b)(1) of this section as the time in which 50 percent of the times in the data set are shorter in duration and 50 percent are longer in duration. The 80th percentile travel time shall be determined from the each data set defined under paragraph (b)(1) of this section as the time in which 80 percent of the times in the data set are shorter in duration and 20 percent are longer in duration. Both the Normal and 80th percentile travel times can be determined by plotting the data on a Travel Time Cumulative Probability Distribution graph or using the percentile functions available in spreadsheet and other analytical tools.
(3) Four LOTTR metrics shall be calculated for each reporting segment; one for each data set defined under paragraph (b)(1) of this section as the 80th percentile travel time divided by the 50th percentile travel time and rounded to the nearest hundredth.
(c) The State DOT shall calculate the PHTTR metric for each reporting segment that is included within an urbanized area with a population over 1,000,000 in accordance with the following:
(1) The State DOT, in coordination with the relevant MPOs, shall assign a “Desired Peak Period Travel Time,” based on their operational policies for their NHS roadways, for each reporting segment for the peak period, one each for the three morning hours and three evening hours and report these to FHWA in accordance with § 490.103(g)(3).
(2) All travel times equating to speeds less than 2 mph or greater than 100 mph shall be removed from the calculation described in paragraph (c)(3) of this section.
(3) An average annual peak hour travel time for each reporting segment shall be computed for each peak hour on non-Federal holiday weekdays that includes travel times recorded from January 1st through December 31st of a calendar year. Morning peak hours for this metric shall include 6:00 to 7:00 a.m., 7:00 to 8:00 a.m., and 8:00 to 9:00 a.m. and afternoon peak hours for this measure shall include 4:00 to 5:00 p.m., 5:00 to 6:00 p.m., and 6:00 to 7:00 p.m. The average travel time for each peak hour shall be calculated for each reporting segment to the nearest whole second as the sum of the 5-minute bin segment average travel times for all traffic (“all vehicles” in NPMRDS nomenclature) occurring in the peak hour on non-Federal holiday weekdays throughout the year divided by the total count of 5-minute intervals where travel times were reported in the peak hour.
(4) The longest average annual peak hour travel time out of the 6 calculated in paragraph (c)(2) of this section shall be used to calculate the PHTTR metric for the reporting segment.
(5) The PHTTR metric shall be calculated for each reporting segment by using the longest average annual peak hour travel time as described in paragraph (c)(3) of this section divided by either the desired morning or afternoon peak hour travel time defined in paragraph (c)(1) of this section corresponding to the hour when the longest average annual peak hour travel time occurred, and rounded to the nearest hundredth.
(d) Starting in 2018 and annually thereafter, State DOTs shall report the metrics, as defined in this section, in accordance with HPMS Field Manual by June 15th of each year for the previous year's measures. Specifically, the following metrics shall be reported for each reporting segment:
(1) All reporting segments of the NPMRDS shall be referenced by NPMRDS TMC. If a State DOT elects to use, in part or in whole, the equivalent data set, all reporting segment shall be referenced by HPMS location referencing standards:
(2) The Level of Travel Time Reliability (LOTTR) metric (to the nearest hundredths) for each of the four time periods identified in paragraphs (b)(1)(i) through (iv) of this section; the corresponding 80th percentile travel times (to the nearest second); and the corresponding normal (50th percentile) travel times (to the nearest second);
(3) Peak Hour Travel Time Ratio (PHTTR) (to the nearest hundredth); peak hour travel time (to the nearest second); and the hour (6 a.m., 7 a.m., 8 a.m., 4 p.m., 5 p.m., or 6 p.m.) where the peak travel time occurred.
(a) The performance measures in § 490.507 shall be calculated in accordance with this section and used by State DOTs and MPOs to carry out the Interstate System and non-Interstate NHS performance-related requirements of part 490, and by FHWA to make the significant progress determinations specified in § 490.109.
(b) The performance measure for Interstate System Travel Time Reliability specified in § 490.507(a)(1) shall be computed to the nearest tenth of a percent as follows:
(c) The performance measure for non-Interstate NHS Travel Time Reliability specified in § 490.507(a)(2) shall be computed to the nearest tenth of a percent as follows:
(d) The performance measure for Interstate System Peak Hour Travel Time specified in § 490.507(b)(1) shall be computed to the nearest tenth of a percent as follows:
(e) The performance measure for non-Interstate NHS Peak Hour Travel Time specified in § 490.507(b)(2) shall be computed to the nearest tenth of a percent as follows:
The purpose of this subpart is to implement the requirements of 23 U.S.C. 150(c)(6) to establish performance measures for State Departments of Transportation (State DOTs) and the Metropolitan Planning Organizations (MPOs) to use to assess the national freight movement on the Interstate System.
The performance measures to assess the national freight movement are applicable to the Interstate System.
The definitions in § 490.101 apply to this subpart.
There are two performance measures to assess freight movement on the Interstate System. They are:
(a) Percent of the Interstate System Mileage providing for Reliable Truck Travel Times; and
(b) Percent of the Interstate System Mileage Uncongested.
(a) Travel time data needed to calculate the measures in § 490.607 shall come from the Travel Time Data Set, as specified in § 490.103(e).
(b) State DOTs, in agreement with MPOs, shall define reporting segments in accordance with § 490.103(f) and submit the reporting segments in accordance with § 490.103(g). Reporting segments must be contiguous so that they cover the full extent of the directional mainline highways of the Interstate in the State.
(c) When truck travel times are not available in the Travel Time Data Set (data not reported, or reported as “0” or null) as specified in § 490.611(b)(1)(ii) for a given 5 minute interval State DOTs shall replace the missing travel time as follows:
(1) Replace the missing value with an observed travel time that represents all traffic on the roadway during the same 5 minute interval (“all vehicles” in NPMRDS nomenclature) provided this travel time is associated with travel speeds that are less than the posted speed limit; or
(2) Replace the missing value with the travel time that would have occurred while traveling at the posted speed limit.
(a) Two performance metrics are required for the measures specified in § 490.607. These are:
(1) Truck Travel Time Reliability.
(2) Average Truck Speed.
(b) The State DOT shall calculate the Truck Travel Time Reliability metric for each Interstate System reporting segment in accordance with the following:
(1) A truck travel time data set shall be created from the Travel Time Data Set to be used to calculate the Truck Travel Time Reliability metric. This data set shall include, for each reporting segment, a ranked list of average truck travel times, to the nearest second, for 5 minute periods of a 24 hour period for an entire calendar year that:
(i) Includes truck travel times occurring for all hours of every day and for every 24-hour period from January 1st through December 31st of the same year; and
(ii) Any truck travel times for Travel Time Segments contained within a reporting segment that are not reported, or reported as “0” or null shall be replaced with an observed travel time that represents all traffic on the roadway during the same 5 minute interval (“all vehicles” in NPMRDS nomenclature) provided this travel time is associated with travel speeds that are less than the posted speed limit. In all other cases the truck travel time shall be replaced with a calculated truck travel time for that segment, based on the segment length and posted speed limit (TTT@PSL), rounded to the nearest second.
(2) The Normal Truck Travel Time (50th percentile) shall be determined from the truck travel time data set defined under paragraph (b)(1) of this section as the time in which 50 percent of the times in the data set are shorter in duration and 50 percent are longer in duration. The 95th percentile truck travel time shall be determined from the truck travel time data set defined under paragraph (b)(1) of this section as the time in which 95 percent of the times in the data set are shorter in duration. Both the Normal and 95th percentile truck travel times can be determined by plotting the data on a Travel Time Cumulative Probability Distribution graph or using the percentile functions available in spreadsheet and other analytical tools.
(3) The Truck Travel Time Reliability metric shall be calculated for each Interstate System reporting segment as the 95th percentile truck travel time divided by the Normal Truck Travel Time (50th percentile truck travel time), rounded to the nearest hundredth.
(c) The State DOT shall calculate the Average Truck Speed metric for each Interstate System reporting segment, in accordance with the following:
(1) Any truck travel times for the travel time segments contained within a reporting segment that are not reported, or reported as “0” or null shall be replaced with an observed travel time that represents all traffic on the roadway during the same 5 minute interval (“all vehicles” in NPMRDS nomenclature) provided this travel time is associated with travel speeds that are less than the posted speed limit. In all other cases the truck travel time shall be with the truck travel time, to the nearest second, at posted speed limit (TTT@PSL) for that segment.
(2) The Average Truck Speed shall be calculated for each reporting segment as follows:
(d) Starting in 2018 and annually thereafter, State DOTs shall report the metrics, as defined in this section, in accordance with HPMS Field Manual by June 15th of each year for the previous year's measures. Specifically, the following metrics shall be reported for each reporting segment:
(1) All reporting segments of the NPMRDS shall be referenced by NPMRDS TMC. If a State DOT elects to use, in part or in whole, the equivalent data set, all reporting segment shall be referenced by HPMS location referencing standards:
(2) Truck Travel Time Reliability metric (to the nearest hundredth), including the 95th percentile truck travel time (to the nearest second) and normal (50th percentile) truck travel time (to the nearest second);
(3) Average Truck Speed metric (to the nearest hundredth mile per hour).
(a) The performance measures in § 490.607 shall be calculated in accordance with this section and used by State DOTs and MPOs to carry out the Freight Movement on the Interstate System related requirements of part 490, and by FHWA to report on performance of the Interstate System.
(b) The performance measure for the Percent of the Interstate System Mileage providing for Reliable Truck Travel Times specified in § 490.607(a) shall be computed to the nearest tenth of a percent as follows:
(c) The performance measure for the Percent of the Interstate System Mileage Uncongested as specified in § 490.607(b) shall be computed to the nearest tenth of a percent as follows:
The purpose of this subpart is to implement the requirements of 23 U.S.C. 150(c)(5)(A) to establish performance measures for State Departments of Transportation (State DOTs) and the Metropolitan Planning Organizations (MPOs) to use in assessing traffic congestion.
The performance measure is applicable to all of the National Highway System in urbanized areas with a population over one million that are, in all or part, designated as nonattainment or maintenance areas for ozone (O
All definitions in § 490.101 apply to this subpart. Unless otherwise specified, the following definitions apply in this subpart:
The performance measure to assess traffic congestion for the purpose of carrying out the CMAQ program, is Annual Hours of Excessive Delay Per Capita.
(a) Travel time data needed to calculate the measure in § 490.707 shall come from the Travel Time Data Set, as specified in § 490.103(e).
(b) State DOTs, in coordination with MPOs, shall define reporting segments in accordance with § 490.103(f) and submit the reporting segments in accordance with § 490.103(g). Reporting segments must be contiguous so that they cover the full extent of the directional mainline highways of the NHS in the urbanized area(s).
(c) State DOTs shall develop hourly traffic volume data for each reporting segment as follows:
(1) State DOTs shall measure or estimate hourly traffic volumes for each day of the reporting year by using either paragraph (c)(1)(i) or (ii) of this section.
(i) State DOTs may use hourly traffic volume counts collected by continuous count stations and apply them to multiple reporting segments, or
(ii) State DOTs may use Annual Average Daily Traffic (AADT) reported to the HPMS to estimate hourly traffic volumes when no hourly volume counts exist. In these cases the AADT data used should be the most recently available, but no more than two years older than the reporting period (
(2) State DOTs shall assign hourly traffic volumes to each reporting segment by hour (
(3) State DOTs shall report the methodology they use to develop hourly traffic volume estimates to FHWA no later than 60 days prior to the submittal of the first Baseline Performance Period Report.
(4) If a State DOT elects to change the methodology it reported under paragraph (c)(3) of this section, then the State DOT shall submit the changed methodology no later than 60 days prior to the submittal of next State Biennial Performance Report required in § 490.107(b).
(d) Populations of urbanized areas shall be as identified based on the most recent U.S. Decennial Census available at the time when the State DOT Baseline Performance Period Report is due to FHWA. This population shall be used for the duration of the performance period to calculate the performance measure as specified in § 490.713.
(e) Nonattainment and maintenance areas shall be identified based on the U.S. Environmental Protection Agency's designation of the area under the NAAQS at the time when the State DOT Baseline Performance Period Report is due to FHWA. These designations shall be used for the duration of the performance period.
(a) The performance metric required to calculate the measure specified in § 490.707 is Total Excessive Delay (vehicle-hours). The following paragraphs explain how to calculate this metric.
(b) State DOTs shall use the following data to calculate the Total Excessive Delay (vehicle-hours) metric:
(1) Travel times of all traffic (“all vehicles” in NPMRDS nomenclature) during each five minute interval for all applicable reporting segments in the Travel Time Data Set occurring for all hours of every day and for every 24-hour period from January 1st through December 31st of the same year;
(2) The length of each applicable reporting segment, reported as required under § 490.709(b); and
(3) Hourly volume estimation for all days and for all reporting segments where excessive delay is measured, as specified in § 490.709(c).
(c) The State DOT shall calculate the “excessive delay threshold travel time” for all applicable travel time segments as follows:
(d) State DOTs shall determine the “excessive delay” for each five minute bin of each reporting segment for every hour and every day in a calendar year as follows:
(1) The travel time segment delay (RSD) shall be calculated to the nearest whole second as follow:
(2) Excessive delay, the additional amount of time to traverse a travel time segment in a five minute bin as compared to the time needed to traverse the travel time segment when traveling at the excessive delay travel speed threshold, shall be calculated to the nearest thousandths of an hour as follows:
(e) State DOTs shall use the hourly traffic volumes as described in § 490.709(c) to calculate the Total Excessive Delay (vehicles-hours) metric for each reporting segment as follows:
(f) Starting in 2018 and annually thereafter, State DOTs shall report Total Excessive Delay (vehicle-hours) metric (to the nearest one hundredth hour) in accordance with HPMS Field Manual by June 15th of each year for the previous year's measures. The Total Excessive Delay (vehicle-hours) metric shall be reported for each reporting segment. All reporting segments of the NPMRDS shall be referenced by NPMRDS TMC. If a State DOT elects to use, in part or in whole, the equivalent data set, all reporting segment shall be referenced by HPMS location referencing standards.
(a) The performance measure in § 490.707 shall be computed in accordance with this section and shall be used by State DOTs and MPOs to carry out CMAQ Traffic Congestion performance-related requirements of part 490.
(b) The performance measure for CMAQ Traffic Congestion specified in § 490.707, Annual Hours of Excessive Delay Per Capita, shall be computed to the nearest hundredth, and by summing the “Total Excessive Delay (vehicle-hours)” metrics of all reporting segments in each of the urbanized area, specified in § 490.703, and dividing it by the population of the urbanized area to produce the measure. The equation for calculating the measure is as follows:
(c) Calculation for the measure, described in this section, and target establishment for the measure shall be phased-in under the requirements in §§ 490.105(e)(8)(vi) and 490.105(f)(4)(vi).
The purpose of this subpart is to implement the requirements of 23 U.S.C. 150(c)(5)(B) to establish performance measures for State Departments of Transportation (State DOTs) and the Metropolitan Planning Organizations (MPOs) to use in assessing on-road mobile source emissions.
(a) The on-road mobile source emissions performance measure is applicable to all projects financed with funds from the 23 U.S.C. 149 CMAQ program apportioned to State DOTs in areas designated as nonattainment or maintenance for ozone (O
(b) This performance measure does not apply to States and MPOs that do not contain any portions of nonattainment or maintenance areas for the criteria pollutants identified in paragraph (a) of this section.
All definitions in § 490.101 apply to this subpart. Unless otherwise specified in this part, the following definitions apply in this part:
The performance measure for the purpose of carrying out the CMAQ Program and for State DOTs to use to assess on-road mobile source emissions is, “Total Emissions Reduction”, which is the 2-year and 4-year cumulative reported emission reductions, for all projects funded by CMAQ funds, of each criteria pollutant and applicable precursors (PM
(a) The data needed to calculate the Total Emission Reduction measure shall come from the CMAQ Public Access System and includes:
(1) The applicable nonattainment or maintenance area;
(2) The applicable MPO; and
(3) The emissions reduction estimated for each CMAQ funded project for each of the applicable criteria pollutants and their precursors for which the area is nonattainment or maintenance.
(b) The State DOT shall:
(1) Enter project information into the CMAQ project tracking system for each CMAQ project funded in the previous fiscal year by March 1st of the following fiscal year; and
(2) Extract the data necessary to calculate the on-road mobile source emissions measures as it appears in the CMAQ Public Access System on July 1st for projects obligated in the prior fiscal year.
(c) Nonattainment and maintenance areas shall be identified based on the effective date of U.S. Environmental Protection Agency's designations under the NAAQS in 40 CFR part 81 at the time when the State DOT Baseline Performance Period Report is due to FHWA. These designations shall be used for the duration of the performance period.
(a) The metric to calculate the Total Emission Reductions measure is the conversion of Emission Reductions from kg/day to short tons per year.
(b) The Annual Tons of Emission Reductions that are predicted for each applicable project reported to the CMAQ Public Access System for each criteria pollutant or precursor for one year shall be defined as follows:
(a) The Total Emission Reductions performance measure specified in § 490.807 shall be calculated in accordance with this section and used by State DOTs and MPOs to carry out CMAQ On-Road Mobile Source Emissions performance-related requirements of part 490.
(b) The Total Emission Reductions for each of the criteria pollutant or applicable precursor for all projects reported to the CMAQ Public Access System shall be calculated to the nearest one thousandths, as follows:
Securities and Exchange Commission.
Concept release.
The Commission is publishing this concept release to seek public comment on modernizing certain business and financial disclosure requirements in Regulation S-K. These disclosure requirements serve as the foundation for the business and financial disclosure in registrants' periodic reports. This concept release is part of an initiative by the Division of Corporation Finance to review the disclosure requirements applicable to registrants to consider ways to improve the requirements for the benefit of investors and registrants.
Comments should be received on or before July 21, 2016.
Comments may be submitted by any of the following methods:
• Use the Commission's Internet comment form (
• Send an email to
• Use the Federal eRulemaking Portal (
• Send paper comments to Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.
Angie Kim, Special Counsel in the Office of Rulemaking, at (202) 551-3430, in the Division of Corporation Finance; 100 F Street NE., Washington, DC 20549.
Regulation S-K was adopted to foster uniform and integrated disclosure for registration statements under the Securities Act of 1933 (“Securities Act”), registration statements under the Securities Exchange Act of 1934 (“Exchange Act”), and other Exchange Act filings, including periodic and current reports.
We focus this release on business and financial disclosures that registrants provide in their periodic reports, which are a subset of the disclosure requirements in Regulation S-K.
This release begins with a discussion of the regulatory history of the integrated disclosure system and Regulation S-K as well as an overview of prior initiatives to review and modernize our disclosure requirements. We then present the framework for our current disclosure regime and explore potential alternative approaches. We proceed to review the business and financial disclosure requirements that apply to periodic reports. We first consider what financial and business information should be required and whether any of these requirements are appropriate to scale for smaller registrants. We then explore how registrants can most effectively present this information to improve its usefulness to investors. In this release, we consider input we have received from letters submitted in response to disclosure modernization efforts
Through this release, we are reviewing and seeking public comment on whether our business and financial disclosure requirements continue to elicit important information for investors and how registrants can most effectively present this information. We are specifically seeking comment on:
• Whether, and if so, how specific disclosures are important or useful to making investment and voting decisions and whether more, less or different information might be needed;
• whether, and if so how, we could revise our current requirements to enhance the information provided to investors while considering whether the action will promote efficiency, competition, and capital formation;
• whether, and if so how, we could revise our requirements to enhance the protection of investors;
• whether our current requirements appropriately balance the costs of disclosure with the benefits;
• whether, and if so how, we could lower the cost to registrants of providing information to investors, including considerations such as advancements in technology and communications;
• whether and if so, how we could increase the benefits to investors and facilitate investor access to disclosure by modernizing the methods used to present, aggregate and disseminate disclosure; and
• any challenges of our current disclosure requirements and those that may result from possible regulatory responses explored in this release or suggested by commenters.
This concept release is part of a comprehensive evaluation of the Commission's disclosure requirements recommended in the staff's Report on Review of Disclosure Requirements in Regulation S-K (“S-K Study”), which was mandated by Section 108 of the Jumpstart Our Business Startups Act (“JOBS Act”).
In connection with the S-K Study
Some of the comments received in connection with the S-K Study were specific to EGCs.
The staff is also working on recommendations for our consideration to propose specific revisions to update or simplify certain of our business and financial disclosure requirements, as required by the recently enacted Fixing America's Surface Transportation Act of 2015 (“FAST Act”).
Enactment of the Securities Act and the Exchange Act resulted in the creation of two separate disclosure regimes. These disclosure regimes remained distinct for approximately thirty years and often resulted in overlapping and duplicative disclosure requirements. Regulation S-K reflects the Commission's efforts to harmonize disclosure required under both the Securities Act and the Exchange Act by creating a single repository for disclosure regulation that applies to filings by registrants under both statutes.
The current integrated disclosure system resulted from a series of efforts triggered by a 1964 amendment to the Exchange Act,
As a result of amendments made by the JOBS Act and the FAST Act, Section 12(g)(1) of the Exchange Act now requires an issuer that is not a bank, bank holding company, or savings and loan holding company to register a class of equity securities if the securities are held of record by either (i) 2,000 persons, or (ii) 500 persons who are not accredited investors and the issuer has total assets exceeding $10 million. Banks, bank holding companies and savings and loan holding companies with total assets exceeding $10 million must register a class of equity securities if the securities are held of record by 2,000 or more persons. Public Law 112-106, Sec. 501, 126 Stat. 306 (2012) and Public Law 114-94, Sec. 85001, 129 Stat. 1312 (2015).
Subsequent to the publication of this article, the Commission initiated several studies that advanced efforts to integrate the Securities Act and Exchange Act disclosure regimes. These efforts included the Disclosure Policy Study led by Commissioner Francis Wheat
Following the Sommer Report, the Commission adopted the first version of Regulation S-K, which included only two disclosure requirements—a description of business and a description of properties.
Many of the disclosure requirements in Regulation S-K originated in Schedule A of the Securities Act, which lists 27 items that must be disclosed in a registration statement and prospectus.
The purpose of corporate disclosure is to provide investors with information they need to make informed investment and voting decisions. Lowering information asymmetries between managers of companies and investors may enhance capital formation and the allocative efficiency of the capital markets. In particular, disclosure of information that is important for investment and voting decisions may lead to more accurate share prices, discourage fraud, heighten monitoring of the managers of companies, and increase liquidity. Effective disclosure requirements also should increase the integrity of securities markets, build investor confidence, and support the provision of capital to the market. In addition, such requirements can facilitate the coordination of registrants around consistent disclosure standards, increasing the efficiency with which investors can process the information.
There are potential drawbacks associated with disclosure requirements. Disclosure can be costly for registrants to produce and disseminate, and disclosure of certain sensitive information can result in competitive disadvantages. There is also a possibility that high levels of immaterial disclosure can obscure important information or reduce incentives for certain market participants to trade or create markets for securities. The appropriate choice of disclosure requirements therefore involves certain tradeoffs. These tradeoffs may depend on the nature of the audience for disclosure and the characteristics of registrants.
Markets are composed of a broad spectrum of investors with different information needs. Some investors may be highly sophisticated and have access to substantial resources to process and interpret data, while others may lack sophistication or have fewer resources to process and interpret data. Investors also may differ in their reliance on disclosure or on third-party analyses of disclosure. The breadth of the audience for disclosure may inform choices about what information is important to investment and voting decisions and should therefore be disclosed. The diversity of the audience for disclosure, and how different subsets of this audience access and digest information about registrants, will also affect decisions about how best to format and disseminate disclosure.
The trade-off between the benefits and costs of disclosure requirements may vary across different types of registrants. For example, to the extent that our disclosure requirements impose fixed costs, they may impose a disproportionate burden on smaller registrants. At the same time, these registrants may have relatively simple operations and thus be able to promote an understanding of their business and financial condition with less disclosure than larger, more complex registrants. Accordingly, it may be appropriate to provide disclosure accommodations for certain types of registrants, while remaining cognizant of the potential adverse impacts that reduced disclosure may have on capital formation and the allocative efficiency of the capital markets.
The benefits associated with disclosing certain items of information may be greater in some cases than in others, such as when an item of disclosure reflects an important part of one registrant's operations but an immaterial part of another's. In this context, it may be important to consider various approaches to trigger disclosure where it is more likely to be important, rather than in all cases. It may also be useful to have disclosure requirements, or guidance in fulfilling these requirements, that are specific to certain industries or other subsets of registrants. We seek to understand if disclosure requirements can be more appropriately tailored to registrants given the likely variation across registrants in the benefits and the costs of disclosing certain types of information. We discuss specific economic considerations in more detail below.
From time to time, the Commission has assessed its disclosure requirements. Several of these studies focused on modernizing or simplifying disclosure requirements. Other initiatives focused on different aspects of the regulatory framework, such as the securities offering process or the financial reporting system, but had the effect of raising disclosure issues for further consideration or shaping current disclosure requirements. The Disclosure Effectiveness Initiative builds upon these prior studies and initiatives.
The Task Force on Disclosure Simplification (“Task Force”), comprising staff from across the Commission, was formed in 1995 to review regulations affecting capital formation with a view towards “streamlining, simplifying, and modernizing the overall regulatory scheme without compromising or diminishing important investor protections.”
The Task Force also made the following recommendations on Regulation S-K:
• Streamline Item 101's description of business disclosure by eliminating duplication of quantitative information about business segments and foreign operations provided in the financial statements;
• revise Item 102's description of property disclosure to elicit “more meaningful and material disclosure;” and
• eliminate Item 103's instruction to replace the $100,000 standard with a general materiality standard for certain environmental legal proceedings to ensure registrants will not be required to disclose non-material information.
Also in 1995, the Commission established the Advisory Committee on the Capital Formation and Regulatory Processes (“1995 Advisory Committee”) to advise on, among other things, the regulatory process and disclosure requirements for public offerings. The 1995 Advisory Committee's primary recommendation was implementing a system of “company registration.”
Noting the Task Force Report, the 1995 Advisory Committee did not focus on specific line-item disclosure requirements but suggested disclosure enhancements as part of its recommendations for a system of “company registration.” These enhancements included a management certification to the Commission for all periodic and current reports, a management's report to the audit committee to be filed as an exhibit to the Form 10-K, expansion of current reporting obligations on Form 8-K and a risk factor disclosure requirement in Form 10-K.
After receiving reports from both the Task Force and the 1995 Advisory Committee, the Commission issued a concept release on regulation of the securities offering process and also sought input on the 1995 Advisory Committee's proposed disclosure enhancements.
In 1998, the Commission adopted rules intended to improve the readability of prospectuses by promoting clear, concise and understandable disclosure (“Plain English Rules”).
In 2007, the Commission chartered the Advisory Committee on Improvements to Financial Reporting (“CIFiR Advisory Committee”) to examine the U.S. financial reporting system.
The Commission adopted rules in 2009 requiring companies to provide financial statement information in interactive data format using the eXtensible Business Reporting Language (“XBRL”) format.
The JOBS Act required the Commission to review Regulation S-K to determine how its disclosure requirements can be updated to modernize and simplify the registration process for EGCs.
The S-K Study recommended a comprehensive review of disclosure requirements in the Commission's rules and forms, including Regulations S-K and S-X, and identified specific areas for further review.
• Improving and maintaining the informativeness of disclosure;
• historical objectives of the rule and their continued or recurring relevance;
• whether the required information is available on a non-discriminatory basis from reliable sources and, if so, any costs or benefits from obtaining the information other than from the registrant;
• administrative and compliance costs of the requirements;
• any competitive or economic costs of disclosing proprietary information;
• maintenance of the Commission's ability to conduct an effective enforcement program and deter fraud; and
• importance of maintaining investor confidence in the reliability of registrant information, in order to, among other things, encourage capital formation.
Under the FAST Act,
• Emphasize a company-by-company approach that allows relevant and material information to be disseminated to investors without boilerplate language or static requirements while preserving completeness and comparability of information across registrants; and
• evaluate methods of information delivery and presentation and explore methods for discouraging repetition and the disclosure of immaterial information.
Consistent with the S-K Study's recommendations and the FAST Act mandates, and in furtherance of the Commission's prior modernization studies and initiatives, we seek to evaluate components of our disclosure framework and revisit certain of our business and financial disclosure requirements to assess whether they continue to provide investors with information that is important to making informed investment and voting decisions. We also seek to evaluate whether current disclosure requirements should be revised to include different formats to facilitate the readability and navigability of disclosure, which we discuss in Section V of the release.
The Securities Act and the Exchange Act authorize the Commission to promulgate rules for registrant disclosure as necessary or appropriate in the public interest or for the protection of investors.
A central goal of the federal securities laws is full and fair disclosure.
Schedule A of the Securities Act sets forth certain items of disclosure to be included in registration statements filed in public offerings and provides the basis for many of the disclosure requirements currently in Regulation S-K. Items in Schedule A are largely financial in nature and were intended to help investors assess a security's value. According to the House Report that preceded the Securities Act:
The items required to be disclosed . . . are items indispensable to any accurate judgment upon the value of a security . . . The type of information required to be disclosed is of a character comparable to that demanded by competent bankers from their borrowers, and has been worked out in light of these and other requirements. They are . . . adequate to bring into full glare of publicity those elements of real and unreal values which may lie behind a security.
In addition to mandating certain disclosure requirements, the Securities Act and the Exchange Act grant the Commission authority to modify and supplement these requirements as necessary or appropriate to implement the purpose of the statutes.
From time to time, Congress has introduced additional disclosure requirements through other statutory mandates. Recent mandates have focused on corporate responsibility, corporate governance and providing enhanced business and financial information to investors. The Sarbanes-Oxley Act of 2002 (“Sarbanes-Oxley Act”)
In some instances, Congress has mandated disclosure that is not necessarily financial in nature. These mandates have ranged from broad policy considerations to prescriptive directives. For example, under the National Environmental Policy Act of 1969 (“NEPA”),
Our disclosure regime includes requirements that we have adopted in response to market developments or advancements in technology. In response to the disorderly markets and damage to investors caused by the hot issue securities markets between 1967 and 1971, the Commission initiated hearings to determine the adequacy of existing disclosure requirements
Significant advancements in technology have also prompted some of our disclosure requirements. The
We are considering changes to our disclosure requirements and seeking public input on how our disclosure requirements could be improved for the benefit of investors and registrants and whether the requirements could be revised to adapt to future changes in market conditions and advancements in technology. We also are seeking input on the utility of mechanisms such as sunset provisions or temporary rules.
When adopting disclosure requirements that have departed from traditional disclosure concepts, the Commission has historically taken an incremental approach to change by first adopting modest revisions and then expanding their application after observing and evaluating the rules' effectiveness. For example, the initial adoption of simplified registration and reporting requirements for smaller businesses on Form S-18 were “in the nature of an experiment”
The Commission has, on occasion, adopted temporary rules or rules with automatic sunset provisions to better assess the effect of or necessity for a particular rule before adopting the rule on a permanent basis. For example, Securities Act Rule 415, which permits delayed and continuous offerings under certain circumstances, was initially adopted on a temporary basis for a period of nine months during which the Commission monitored the operation and impact of the new rule.
While the Commission acted to permanently adopt Rule 415, it has allowed other temporary rules to expire. The Commission adopted on a temporary basis Securities Act Rules 702 and 703. Rule 702 required the filing of a Form 701 after sales under Rule 701 exceeded a particular threshold. Rule 703 disqualified registrants from relying on the Rule 701 exemption from registration where the registrant failed to make the filing required by Rule 702.
Even in the absence of a temporary rule or sunset provision, the Commission has undertaken efforts to study the effects of new rules or amendments. The Commission uses these studies to guide future amendments or rulemaking. For example, our staff has examined the effects on capital formation through private placements after adoption of amendments to Regulation D in accordance with the JOBS Act.
Requiring affirmative Commission action to extend or make permanent certain requirements, the utility of which may change over time, could require us to more frequently consider the effectiveness of our requirements. Alternatively, the Commission could commit to studying the impact of certain rule changes on a specified schedule, without making the rules temporary or applying automatic sunset provisions. Any such review would be in addition to the periodic review currently required by the Regulatory Flexibility Act (“RFA”),
1. Should the Commission consider including automatic sunset provisions in new disclosure requirements? If so, what types of disclosure requirements should include these provisions? What factors should we consider in identifying them? What would be an appropriate length of time for any sunset provisions? Would this length of time vary with the nature of the rule in question?
2. What are the advantages and disadvantages of automatic sunset provisions? Would automatic sunset provisions result in unnecessary regulatory uncertainty for investors or registrants?
3. How would the use of automatic sunset provisions affect registrants, investors and other users of disclosure? Would registrants, investors or other users incur increased costs associated with the use of automatic sunset provisions?
4. Should we consider requiring the staff to study and report to the Commission on the impact of new disclosure requirements when adopting them, in addition to the review the Commission performs under the RFA? For what type of disclosure requirements would such an approach be appropriate? What are the advantages and disadvantages of such a study and report on a new rule?
5. Are there other ways our disclosure requirements could be revised to adapt more easily to future market changes and technological advancements?
The concept of materiality has been described as “the cornerstone” of the disclosure system established by the federal securities laws.
In creating and implementing our system of integrated disclosure, identification of material information was one of two principal objectives. In the 1982 Integrated Disclosure Adopting Release, the Commission stated:
The Commission's program to integrate the disclosure systems has focused on two principal objectives: First, a comprehensive evaluation of the disclosure policies and procedures under both Acts to identify the information which is material to security holders and investors in both the distribution process and the trading markets . . . and, second, a determination of the circumstances under which information should be disseminated to security holders, investors and the marketplace.
The Commission adopted line-item requirements in Regulation S-K and its predecessors to provide investors with specific disclosure within broad categories of material information.
For example, Item 303(a)(2) requires registrants to disclose material commitments for capital expenditures, known material trends in the registrant's capital resources, and expected material changes in the mix and relative cost of such resources.
For example, disclosure requirements specific to environmental proceedings in Item 103 enumerate thresholds for disclosure based on a percentage of current assets (10%) or a specified dollar amount ($100,000).
In addition to the information required to be disclosed, Exchange Act Rule 12b-20 requires registrants to disclose such further material information, if any, as may be necessary to make the required statements, in the light of the circumstances under which they are made, not misleading. Rule 12b-20 of the Exchange Act [17 CFR 240.12b-20].
The Court has held that information is material if there is a substantial likelihood that a reasonable investor would consider the information important in deciding how to vote or make an investment decision.
In proposing to revise Rule 12b-2 to adopt the Court's definition of “material,” the Commission noted the trend to apply the Court's definition in every type of federal securities law violation and concluded that the same test would be applied for any purpose under the Securities Act and the Exchange Act.
Article 1-02(o) of Regulation S-X retains the definition of “material” prior to
From time to time, the Commission has provided guidance to assist management in the types of assessments to make and issues to consider in determining whether information is material.
Instruction 5 to Item 103 requires disclosure of proceedings related to federal, state, or local environmental protection laws when (i) the proceeding is material to the registrant's business or financial condition; (ii) the proceeding involves primarily a claim for damages, or involves potential monetary sanctions, capital expenditures, deferred charges or charges to income and the amount involved, exclusive of interest and costs, exceeds ten percent of current assets of the registrant and its subsidiaries on a consolidated basis; or (iii) a governmental authority is a party to a proceeding involving monetary sanctions, unless the registrant believes that the proceeding will result in no monetary sanctions, or in monetary sanctions, exclusive of interests and costs, of less than $100,000. [17 CFR 229.103].
Item 404 requires disclosure of transactions with related parties where the related party had or will have a direct or indirect material interest and the amount involved exceeds $120,000 or, in the case of SRCs, where the amount involved exceeds the lesser of $120,000 or one percent of the average of the SRC's total assets at year end for the last two completed fiscal years. [17 CFR 229.404].
Two commenters stated that a principles-based approach would provide additional flexibility to registrants by allowing them to disclose material information based on all relevant facts and circumstances.
One commenter opposed a principles-based system, stating such a system could result in inconsistent application of the principles-based threshold and thus non-comparable information across companies.
In 2003, the staff prepared a study on the adoption of a principles-based accounting system.
In the S-K Study, the staff stated that any recommended revisions to Regulation S-K should emphasize a principles-based approach as an overarching component of the disclosure framework while preserving the benefits of a rules-based system, which affords consistency, completeness and comparability across registrants.
Limiting prescriptive disclosure requirements and emphasizing principles-based disclosure could improve disclosure by reducing the amount of information that may be irrelevant, outdated or immaterial. Because prescriptive disclosure requirements may result in disclosure that is not necessarily material or important to investors, greater use of principles-based disclosure requirements may allow registrants to more effectively tailor their disclosure to provide only the information about their specific business and financial condition that is important to investors. A principles-based approach also may allow registrants to readily adapt their disclosure to facts and circumstances that may change over time.
On the other hand, reducing prescriptive disclosure requirements and shifting towards more principles-based disclosure requirements may limit the comparability, consistency and completeness of disclosure. Also, in the absence of clear guidelines for determining when information is material, registrants may have difficulty applying principles-based disclosure requirements,
The Section 108 Study proposed a third alternative for developing new accounting standards, which the staff referred to as an “objectives-oriented” approach.
6. Should we revise our principles-based rules to use a consistent disclosure threshold? If so, should a materiality standard be used or should a different standard, such as an “objectives-oriented” approach or any other approach, be used? If materiality should be used, should the current definition be retained? Should we consider a different definition of materiality for disclosure purposes? If so, how should it be defined?
7. Should we limit prescriptive disclosure requirements and emphasize a principles-based approach? If so, how? How can we most effectively balance the benefits of a principles-based approach while preserving the benefits of prescriptive requirements?
8. What are the advantages and disadvantages of a principles-based approach? Would a principles-based approach increase the usefulness of disclosures? What would be the costs and benefits of such an approach for investors and registrants?
9. Do registrants find it difficult to apply principles-based requirements? Why? If they are uncertain about whether information is to be disclosed, do registrants err on the side of including or omitting the disclosure? If registrants include disclosure beyond what is required, does the additional information obfuscate the information that is important to investors? Does it instead provide useful information to investors?
10. Do registrants find quantitative thresholds helpful in preparing disclosure? Do such thresholds elicit information that is important to investors? Do they require registrants to provide some disclosure that investors do not need? To the extent our rules contain quantitative thresholds, how should we define them? Are specified dollar amounts more or less effective than amounts based on a registrant's financial condition, such as a percentage of revenues or assets?
11. Should we develop qualitative thresholds for disclosure? Should there be a combination of quantitative and qualitative thresholds?
12. Do registrants find principles-based disclosure requirements helpful in preparing disclosure? Do such requirements elicit information that is important to investors?
13. Would principles-based disclosure affect corporate compliance and governance structures? If so, how?
The Securities Act and the Exchange Act require registrants to provide information prescribed by the Commission as necessary or appropriate in the public interest or for the protection of investors.
Nearly fifty years ago, the Wheat Report recognized variation among the investor audience for disclosure and suggested that the Commission's disclosure requirements should strike a “pragmatic balance . . . between the needs of unsophisticated investors and those of the knowledgeable student of finance.”
When adopting format and content changes to Form 10-K and the annual report to security holders as part of integrated disclosure, the Commission characterized users of Form 10-K as different from users of the annual report to security holders.
In the adopting release for these changes, the Commission stated its belief that focusing primarily on these frequent users is appropriate in formulating Form 10-K disclosure requirements, but “such a focus would not be appropriate in formulating requirements for annual reports to security holders.”
One commenter suggested that current disclosure is too complicated for the everyday person to read and that it should be less duplicative and more straightforward.
We recognize the diverse composition and varied informational needs, sophistication and financial resources of investors and that some investors may obtain their analysis or advice from or through third parties who use registrant disclosures. Investors using registrant disclosure directly may include both individual investors and institutional investors, such as banks, insurance companies, mutual funds, exchange traded funds, pension funds, hedge funds and managed accounts. These investor types may also use registrant disclosure indirectly through professional data aggregators, financial advisors, proxy advisors, professional analysts, journalists, and other third parties who process and synthesize disclosures for end user investors.
Different investor types and third parties may focus on different filings or items of disclosure.
Similarly, as different investors and third parties use disclosure in different ways and seek varying degrees of information, the audience for disclosure is also an important consideration in determining what information is disclosed. Institutional investors, their financial advisors and some third parties often use, and have supported requiring complex information and interactive data.
Other investors may seek disclosure that emphasizes, within the universe of information that is disclosed, the information and analysis that management believes is most important.
14. Should registrants assume some level of investor sophistication in preparing their disclosures? If so, what level or levels of sophistication? How should investor sophistication be measured? What are the risks or other disadvantages to investors if registrants either underestimate or overestimate the level of investor sophistication and resources when preparing their disclosures? Does disclosure protect all investors if it is tailored to a subset of the investor community?
15. Should we revise our rules to require disclosure that is formatted to provide information to various types of investors in a manner that will facilitate their use of disclosure for investment and voting decisions?
16. Commenters have suggested that disclosure should be written for a more sophisticated investor than current disclosure appears to contemplate,
17. How do investors and other users of disclosure currently access and use this information? How does this vary across different subsets of the audience for the disclosure?
18. Should we use investor testing, such as focus groups or electronic surveys, to provide input on investors' use of and access to disclosure?
19. To what extent should the reliance of certain investors on market prices or third-party analyses, rather than using
20. To what extent should we consider the needs of other market participants, such as professional securities analysts and other third parties, in revising our disclosure requirements? What would be their needs?
When the Commission is engaged in rulemaking it is statutorily required to consider, in addition to the protection of investors, whether an action will promote efficiency, competition, and capital formation.
Disclosure may also have costs to registrants that could negatively affect these factors, although advances in technology and communications have the potential to reduce these costs. As disclosure costs rise, registrants' costs of capital may increase, which can reduce investment, lower the value of a company and impede economic growth. Registrants may also choose to exit the Commission's reporting system, when eligible, or remain private if the disclosure requirements are sufficiently costly.
We are sensitive to the costs of disclosure, including the administrative and compliance costs of preparing and disseminating disclosure as well as the potential costs of disclosing sensitive information to competitors. While the S-K Study did not specifically consider costs to investors, the staff identified economic principles that should be given consideration when reviewing and considering changes to our disclosure requirements, including: (1) The extent to which a given disclosure requirement entails high administrative and compliance costs; and (2) the extent to which disclosure of a company's proprietary information may have competitive or other economic costs.
To address the potential negative effects that would result from disclosing sensitive information, our rules permit registrants to request confidential treatment of proprietary information, if disclosure of such information would cause competitive harm to the registrant.
The Commission also has addressed the costs of disclosure through regulatory relief in the form of scaled disclosure requirements for certain smaller registrants. These accommodations are intended to promote capital formation and provide relief where the fixed costs of compliance may be particularly high relative to the size of the company while also considering investor protection.
Throughout this concept release, we seek comment on changes to specific disclosure requirements that could reduce costs for registrants, while still providing investors with information that is important or useful to making informed investment and voting decisions. Separately, we address the effectiveness of our scaled disclosure requirements.
21. Do current disclosure requirements appropriately consider the costs and benefits of disclosure to registrants and investors? How should the Commission evaluate benefits, such as those arising from disclosure, that cannot be easily quantified?
22. In addition to scaled disclosure and confidential treatment, are there other accommodations that we could make to reduce costs for registrants while still providing investors with the information that is important or useful to making informed investment and voting decisions?
23. Are there other benefits and costs that we should consider when evaluating disclosure effectiveness?
Disclosure about a registrant's business lays the groundwork for understanding and assessing a company, its operations and financial condition. Information about a registrant's industry, business environment and other factors affecting the business helps inform investment and voting decisions by placing other disclosure in context. Schedule A of the Securities Act requires disclosure of the general character of the business transacted or to be transacted by the registrant. Item 101 of Regulation S-K similarly requires a description of a registrant's business. Item 102 requires disclosure about a registrant's materially important physical properties. We are reviewing the disclosure required by Item 101(a)(1) and (c)
Item 101(a) of Regulation S-K requires a description of the general development of the business of the registrant during the past five years, or such shorter period as the registrant may have been engaged in business.
A requirement to provide a brief outline of the general development of the business for the preceding five years was included in the earliest forms of registration statements and annual reports.
Business developments and other disclosure called for by Item 101(a)(1) are often reflected elsewhere in the filing, such as in the financial statements or MD&A. Additionally, in 2004, the Commission expanded the number of reportable events on Form 8-K to include items that may result in disclosure that overlaps with the requirements of Item 101(a)(1), such as disclosure of entry into a material definitive agreement, including business combination agreements.
24. Does the current requirement in Item 101(a)(1) to describe the general development of a registrant's business during the past five years provide useful disclosure that is not available either elsewhere in the current filing (
25. How could we improve Item 101(a)(1)? For example, is the five-year time frame for this disclosure appropriate? Would a shorter or longer time frame be more appropriate? If so, what time frame would be appropriate and why?
26. Does this disclosure continue to be useful for registrants with a reporting history? Once a registrant has disclosed this information in a registration statement should we allow registrants to omit this disclosure from subsequent periodic reports unless material changes occur? Alternatively, should we require registrants to describe its business as currently conducted as well as any material changes that have occurred in the last five years?
27. Should we revise Item 101(a)(1) to require disclosure of a registrant's business strategy? Would investors find such a disclosure important or useful? If so, should this requirement be included in a registrant's MD&A? Should we define “business strategy”? If so, how?
28. Should we permit a summary disclosure of the general development of a registrant's business in all filings except the initial filing? For example, should we require a more detailed discussion of a registrant's business in the initial filing, and in subsequent filings only require a summary of the registrant's business along with a discussion of material changes in the business as previously disclosed in the registrant's Form 10-K? Alternatively, should we require a more detailed discussion of a registrant's business on a periodic basis, such as every three years, and a summary disclosure in other years? Should any such requirement be conditioned on timely reporting or some other consideration?
29. What types of investors or audiences are most likely to value the information required by Item 101(a)(1)?
30. What is the cost of providing the disclosure required by Item 101(a), including the administrative and compliance costs of preparing and disseminating this disclosure? How would these costs change if we made any of the changes contemplated here? Please provide quantified estimates where possible and include only those costs associated with providing disclosure under Item 101(a).
While Item 101(a) requires disclosure of the general development of the business, Item 101(c) requires a narrative description of a registrant's business and identifies thirteen specific items that must be disclosed:
(i) principal products produced and services rendered;
(ii) new products or segments;
(iii) sources and availability of raw materials;
(iv) intellectual property;
(v) seasonality of the business;
(vi) working capital practices;
(vii) dependence on certain customers;
(viii) dollar amount of backlog orders believed to be firm;
(ix) business subject to renegotiation or termination of government contracts;
(x) competitive conditions;
(xi) company-sponsored research and development activities;
(xii) compliance with environmental laws; and
(xiii) number of employees.
Consistent with Schedule A of the Securities Act, the earliest forms of registration statements and annual reports required a brief outline of the general character of the business done and intended to be done by a registrant.
In the S-K Study, the staff recommended reviewing the description of business for continuing relevance in
31. Do the disclosure requirements in Item 101(c) continue to provide useful information to investors? How could we improve Item 101(c)'s requirements?
32. How could we update Item 101(c) to better reflect changes in the way businesses operate? Are there particular categories or types of registrants for which these disclosure requirements are more or less relevant?
33. Are there additional line-item disclosure requirements about a registrant's business that would improve the quality and consistency of disclosure? Are there any categories of information that certain registrants voluntarily provide, and are not required to disclose under Item 101(c), that we should include in Item 101(c)?
34. Currently, some registrants include in their business section a general description of their industry. Should industry disclosure be a separate requirement? If so, would this requirement be more useful to investors in the business section or in MD&A?
35. Should we require additional specific disclosure relevant to particular industries, such as manufacturing or technology companies? If so, which industries and why? What are the benefits and challenges of requiring industry-specific disclosure?
36. What is the impact on disclosure of listing the thirteen item requirements in Item 101(c)? In practice, do registrants view Item 101(c) as a checklist? Do the prescriptive items result in disclosure of information that is not important by some registrants?
37. Should we require Item 101(c) disclosure only in the initial filing with follow-up disclosure of any material changes for subsequent years? Should any such requirement be conditioned on timely reporting or some other consideration? Should the requirements differ for registration statements and periodic reports?
38. Is there any information currently disclosed in the description of business that should be presented in a different context such as MD&A or risk factors? Why?
39. In some circumstances, disclosure is required under Item 101(c)(1) if material. The item specifies that, to the extent material to an understanding of the registrant's business taken as a whole, the description of each segment shall include the information in (c)(1)(i) through (x) and that matters in (c)(1)(xi) through (xiii) shall be discussed for the registrant's business in general; where material, the segments to which these matters are significant shall be identified. Additionally, some sub-items of Item 101(c)(1) require disclosure if material, such as (c)(1)(ii) and (c)(1)(ix),
40. What types of investors or audiences are most likely to value the information required by Item 101(c)? Would an alternative format or presentation of the information improve the value of such disclosure to a particular type of investor or audience? If so, what type of format or presentation?
41. What is the cost of providing the disclosure required by Item 101(c), including the administrative and compliance costs of preparing and disseminating this disclosure? How would these costs change if we made any of the changes contemplated here? Please provide quantified estimates where possible and include only those costs associated with providing disclosure under Item 101(c).
Item 101(c)(1)(iv) requires disclosure of the importance to the segment and the duration and effect of all patents, trademarks, licenses, franchises and concessions held.
A broad range of industries benefit from intellectual property, both directly and indirectly,
In the biotechnology and pharmaceutical industries, registrants that provide detailed patent disclosure often disclose the jurisdiction in which the patent was filed, year of expiration, type of patent (
In the information technologies and services industry, registrants protect their intellectual property through the use of patents, trademarks, copyrights, trade secrets, licenses and confidentiality agreements.
In general, registrants in the information technologies and services industry use copyrights to protect against the unauthorized copying of software programs
42. Should we retain the current scope of Item 101(c)(1)(iv), which requires disclosure of a registrant's patents, trademarks, licenses, franchises and concessions? Should we expand the rule to include other types of intellectual property, such as copyrights? Should we remove the individual categories and instead require disclosure of “intellectual property”? If so, should we define that term and what should it encompass?
43. What, if any, additional information about a registrant's reliance on or use of technology and related intellectual property rights should we require and why? Should we revise Item 101(c)(1)(iv) to require more detailed intellectual property disclosure, similar to the disclosure currently provided by some biotechnology and pharmaceutical registrants? If so, should we require such detailed disclosures for all or only some of a registrant's intellectual property, such as those that are material to the business?
44. For registrants with large intellectual property portfolios, does aggregate disclosure of the total number of patents, trademarks and copyrights and a range of expiration dates provide investors with sufficient information? If not, what additional information do investors need about a company's portfolio of intellectual property? Would tabular disclosure or an alternate format or presentation of a registrant's intellectual property portfolio make the information more useful to investors? What would be the benefits and challenges of requiring disclosure of this information in this format?
45. Should we limit these disclosure requirements to registrants in particular industries? If so, which industries should we specify and why? Is disclosure about a registrant's intellectual property most useful in the context of the description of business, disclosure about trends and developments affecting results of operations, or in a discussion of risk and risk management?
46. What are the competitive costs of disclosure under Item 101(c)(1)(iv)?
Item 101(c)(1)(ix) requires disclosure of any material portion of a business that may be subject to renegotiation of profits or termination of contracts or subcontracts at the election of the government.
U.S. government contracts generally contain provisions that enable the contract to be terminated, in whole or in part, without prior notice, at the government's convenience (due to lack of funding or for other reasons) or for default based on performance. ASC 912-275-50-1 requires footnote disclosure of renegotiation uncertainties, their significance, and renegotiation discussions relating to the current year. In addition, ASC 912-275-50-6 states that if there are indications that a contract termination may occur and the termination would have a material effect on the contractor's operations, disclosure of the circumstances and the potential effects shall be made in the notes to financial statements. The staff has observed that, rather than provide duplicative disclosure, some government contractors cross-reference their discussion of the government's right to terminate a contract under Item 101(c)(1)(ix) to either their accounting policy disclosure for revenue recognition in the critical accounting estimates disclosure in MD&A or to their significant accounting policies in the notes to the financial statements.
Business contracts with agencies of the U.S. government and the various laws and regulations relating to procurement and performance of U.S. government contracts impose terms and rights that are different from those typically found in commercial contracts. In a 1972 Notice to Registrants, the Commission noted that government contracts are subject to renegotiation of profit and to termination for the convenience of the government.
Registrants with U.S. government contracts tend to disclose that the funding of these contracts is subject to the availability of Congressional appropriations and that, as a result, long-term government contracts are partially funded initially with additional funds committed only as Congress makes further appropriations. These registrants disclose that they may be required to maintain security clearances for facilities and personnel in order to protect classified information. Additionally, these registrants state that they may be subject to routine government audits and investigations, and any deficiencies or illegal activities identified during the audits or investigations may result in the forfeiture or suspension of payments and civil or criminal penalties.
47. Is disclosure about government contracts important to investors? Why? Is there any additional information about a registrant's contracts with the government that would be important to investors?
48. Rather than focusing specifically on government contracts, should we require registrants to briefly describe all material contracts? Would such a requirement elicit disclosure not otherwise provided in MD&A or the description of business?
Pursuant to NEPA, which mandated consideration of the environment in regulatory action, the Commission adopted Item 101(c)(1)(xii) in 1973 to require disclosure of the material effects compliance with federal, state and local environmental laws may have on the capital expenditures, earnings and competitive position of the registrant.
49. Should we increase or reduce the environmental disclosure required by Item 101(c)(1)(xii)? Why? What kind of information should we add to or remove from this requirement?
50. Is disclosure about the material effects that compliance with provisions regulating the discharge of materials into the environment, or otherwise relating to the protection of the environment, may have upon a registrant's capital expenditures, earnings and competitive position important to investors? If so, should we require registrants to present this disclosure in a specific format? Would this disclosure be more appropriate in MD&A or the business section?
51. Should we require specific disclosure about the material effects that other regulations may have on a registrant's capital expenditures, earnings and competitive position? If so, are there specific laws and regulations that our rules should cover?
Although not referenced in Item 101, many registrants discuss government regulations relevant to their business.
Registrants in the financial services industry regularly describe federal and state regulation as well as supervision by the Federal Reserve Board, while registrants with a material amount of U.S. government contracts disclose the laws and regulations for government contracts. Registrants with tax strategies involving foreign jurisdictions typically disclose that they are subject to income taxes in both the U.S. and numerous foreign jurisdictions, and that future changes to U.S. and non-U.S. tax law could adversely affect their anticipated financial position and results. Some disclose the impact on their business of tax treaties between the U.S. and one or more foreign jurisdictions.
52. Given that many registrants provide disclosure of material government regulations without a specific line-item requirement, are the current disclosure requirements sufficient? Would a specific requirement seeking this disclosure provide additional information that is important to investors? If so, what specific information and level of detail should we require and why? What would be the costs of requiring disclosure of this information?
53. Foreign regulations, including foreign tax rates and treaties, may have a material impact on a registrant's operations. Should we specifically require registrants to describe foreign regulations that affect their business? If so, what specific information and level of detail should we require? How would any additional information inform investment and voting decisions? Would there be challenges for registrants to provide such disclosure?
Item 101(c)(1)(xiii) requires disclosure of the number of persons employed by the registrant. The Division of Corporation Finance (“Division”) has provided interpretive guidance on this requirement stating that, in industries where the general practice is to hire independent contractors rather than employees, companies should disclose the number of persons retained as independent contractors as well as the number of regular employees.
The number of persons employed by the registrant can help investors assess the size and scale of a registrant's operations. Changes in the number or type of persons employed can also be indicative of trends or shifts in a registrant's operations. Disclosure of the number of employees varies among registrants. Some registrants distinguish between the number of full-time and part-time employees, and others specify the number of employees in each department or division. Registrants with large numbers of employees often disclose the approximate number of employees and discuss their employees' membership in a union or similar organization. Other registrants characterize the state of their employee relations and disclose whether their employees are covered by a collective bargaining agreement or represented by a labor union.
54. Does disclosure of the number of persons employed by the registrant help investors assess the size, scale and viability of a registrant's operations and any trends or shifts in operations? Is this disclosure important to investors and why? Is there any additional information about employees that would be important to investors? If so, what information?
55. For new registrants filing a registration statement that have not had revenue from operations during each of the preceding three fiscal years, Item 101(a)(2)(iii) requires disclosure of any anticipated material changes in the number of employees in the various departments such as research and development, production, sales or administration.
56. Should we require registrants to distinguish among their total number of persons employed, such as by distinguishing between:
• Full-time and part-time or seasonal employees;
• Employees and independent contractors; or
• Domestic and foreign employees?
Why or why not?
57. Rather than requiring registrants to disclose the number of employees or independent contractors, should we require or permit registrants to provide a range? Why? Should we allow for different ranges based on the size of the registrant? Would reporting a range rather than a specific number reduce the costs of producing this disclosure?
58. Should we require disclosure of additional information about a registrant's employees or employment practices? What would be the challenges of requiring disclosure of any additional information, and what would be the benefits to investors?
59. As outsourcing and subcontracting have become more prevalent in the last few decades,
Item 102 of Regulation S-K requires disclosure of the location and general character of the principal plants, mines and other materially important physical properties of the registrant and its subsidiaries. Item 102 also requires registrants to identify the segments, as reported in the financial statements, that use the properties described. Instruction 1 states that registrants must disclose such information as reasonably will inform investors as to the suitability, adequacy, productive capacity and extent of utilization of the facilities by the registrant.
Since 1935, we have required disclosure similar to that required under Item 102.
In 1996, the Task Force on Disclosure Simplification recommended the Commission revise Item 102 to more effectively elicit disclosure of material facts about a registrant's principal properties, rather than lists of properties and their immaterial characteristics.
In response to Item 102, registrants typically disclose information about their headquarters such as the location, size and whether they own or lease the property, as well as information about other properties material to the business. In addition to this disclosure, some registrants cross-reference to the discussion in the notes to the financial statements such as to the note on purchase and lease commitments or to the note on property, plant and equipment.
Registrants in certain industries may provide more specific disclosures. For example, registrants with retail stores often disclose the number of their stores, location, size and lease termination dates. Registrants in the hotel and lodging industry tend to disclose the location and number of rooms at each of their properties. Some registrants with casino operations disclose the number of table games and slot machines at each location. Registrants in the restaurant industry tend to disclose the number of their restaurants, location and whether they are registrant-operated or franchisee-operated stores. In the paper mill or paper production industry, registrants typically provide tabular disclosure for facilities including their geographic location and related products or use. By contrast, some registrants, such as those that provide services or information technology, may not have material physical properties and tend to disclose information about their corporate headquarters, office space and other facilities.
60. Should we retain or eliminate Item 102? Why or why not? How could Item 102 be improved?
61. Would any additional disclosure about a registrant's properties be important to investors? If so, what additional disclosure would be important? What would be the challenges to registrants of requiring disclosure of any such additional information, and what would be the benefits to investors?
62. For registrants that may not have material physical properties, is the disclosure that registrants typically provide about their corporate headquarters, office space and other facilities important to investors?
63. Should we require property disclosure only for registrants in certain industries? If so, how should we identify these industries?
64. Should the disclosure requirements focus instead on the risks to a registrant's business resulting from the availability and cost of properties it needs for its operations?
65. What types of investors or audiences are most likely to value the information required by Item 102?
66. What is the cost of providing the disclosure required by Item 102, including the administrative and compliance costs of preparing and disseminating this disclosure? How would these costs change if we made any of the changes contemplated here? Please provide quantified estimates where possible and include only those costs associated with providing disclosure under Item 102.
Financial information is essential to understanding a registrant's performance, financial condition and future prospects. The Commission has long recognized the need for a narrative explanation of the financial statements, as a numerical presentation and accompanying footnotes alone may be insufficient for an investor to assess the quality of the earnings and the likelihood that past performance is indicative of future performance.
Regulation S-X requires companies to provide annual and quarterly financial statements,
• Item 301 requires disclosure of selected financial data;
• Item 302(a) requires disclosure of selected quarterly financial data;
• Item 303 requires disclosure of management's discussion and analysis of financial condition and results of operations.
We are reviewing these disclosure requirements to determine whether they continue to provide investors with information that is important to evaluating a registrant's performance, financial condition and prospects for the future and what, if any, aspects of the disclosure requirements are duplicative. We are seeking public input on whether we should consider any new disclosure requirements and whether we should eliminate or modify any existing disclosure requirement related to such matters.
Item 301 requires registrants to disclose selected financial data that highlight significant trends in the registrant's financial condition and results of operations.
Two commenters suggested revising Item 301 to allow registrants to omit the earliest two of the last five fiscal years where the information cannot be provided without unreasonable cost or expense.
Item 301 is intended to provide selected financial data in a convenient and readable format that highlights significant trends in the registrant's financial condition and results of operations.
In October 1970, the Commission expanded Form 10-K to include “Item 2—Summary of Operations,” which required registrants to furnish in comparative columnar form a five-year summary of operations and any additional fiscal years necessary to keep the summary from being misleading.
Most of the items required by Item 301 are also required in the annual financial statements. Unlike the financial statements required in a Form 10-K, however, Item 301 information covers each of the registrant's last five fiscal years. Accordingly, Item 301 disclosure for items such as net sales and income or loss from continuing operations in the income statement
Earlier years required to be disclosed under Item 301 are typically available in prior annual reports. When the precursor to Item 301 was adopted in 1970, prior annual reports were not readily accessible.
Despite some overlap with current and prior financial statements, Item 301 disclosure can provide information that might not be available to investors for all five years. Specifically, retrospective changes to the annual financial statements would typically be reflected in the selected financial data table across all five years instead of the three years covered in the financial statements.
67. Is the Item 301 disclosure that is not otherwise available or readily accessible important to investors? Are there benefits to having the five-year information in one table?
68. Should we retain, modify or eliminate Item 301? Why? Does it achieve the goal of highlighting significant trends in a registrant's financial condition and results of operation? Does it also achieve the goal of providing selected financial data in a convenient and readable format? How would the elimination of Item 301 affect investors? Would elimination of this requirement increase costs to investors because they would then need to obtain this information from prior filings?
69. If we retain Item 301, should we modify this requirement and, if so, how? Should we modify the item to require additional disclosure and, if so, what additional disclosure would be important to investors and why?
70. Instruction 1 to Item 303(a) specifies that, where trend information is relevant, reference to the five-year selected financial data pursuant to Item 301 may be necessary.
71. EGCs are not required to present selected financial data for any period prior to the earliest audited period presented in connection with its first effective registration statement.
72. Should we require Item 301 disclosure for the full five years only in certain instances such as when a registrant revises its annual financial statements or if information on the earliest two of the last five years is available without unreasonable cost or expense?
73. Currently, Item 301 disclosure is required in comparative columnar form. If we continued to require this disclosure, should we consider other presentation or format requirements?
74. What types of investors or audiences are most likely to value the information required by Item 301?
75. What is the cost of providing the disclosure required by Item 301, including the administrative and compliance costs of preparing and disseminating this disclosure? How would these costs change if we made any of the changes contemplated here? Please provide quantified estimates where possible and include only those costs associated with providing disclosure under Item 301.
When proposing the requirement for selected financial data, the Commission sought to strike a reasonable balance between specified content and a flexible approach that permits registrants to select the data that best indicates performance.
For registrants that provide additional items in their selected financial data, disclosure varies. Financial institutions commonly provide additional metrics that may include return on average assets and capital ratios. Registrants in the telecommunications industry may include the number of subscribers while retailers may include the number of stores or average store size. While such information is not required under U.S. GAAP, it is not considered a “non-GAAP financial measure” such that reconciliation under Item 10(e) of Regulation S-K would be required.
76. Does Instruction 2 provide a reasonable balance between specified content and a flexible approach that permits registrants to select the data that best indicates performance? Why or why not? If not, how should we modify Instruction 2? For example, should we modify Instruction 2 to be more prescriptive or provide for a more flexible approach? If a flexible approach should be used, should we require registrants to disclose their reasons for the items it included?
77. Should we require auditor involvement (
78. What is the impact of listing specific items of disclosure in Instruction 2? Do registrants view the items listed in Instruction 2 as a checklist? Should additional items be considered?
Item 302(a)(1) requires certain registrants to disclose quarterly financial data of selected operating results
The staff is separately considering Item 302(b), which requires certain disclosures of oil and gas activities, as part of its work to develop
A few years after adopting Form 10-Q, in 1974, the Commission noted that quarterly data was still being “reported on an extremely abbreviated basis and annual financial statements [had] generally been presented without regard for or disclosure of trends occurring within a year.”
The Commission recognized that numerous commenters opposed the requirements, suggesting that interim results are materially affected by random events and that including such data in annual financial statements would lend them an appearance of reliability that could be misleading.
While most of the disclosure required by Item 302(a) is required in prior quarterly reports, Item 302(a)(1) also requires a separate presentation of certain items for a registrant's fourth quarter, which is not otherwise required. Although there is no similar requirement for disclosing the fourth fiscal quarter, U.S. GAAP typically allows investors to infer fourth quarter data by requiring disclosure of disposals of components of an entity and unusual or infrequently occurring items recognized in the fourth quarter.
Additionally, as Item 302(a)(2) requires disclosure of variances in results from amounts previously reported for the two most recent fiscal years, the effect of a retrospective change in any quarter for which a Form 10-Q was filed in the more recent of the two fiscal years will be disclosed in the selected quarterly data. Absent Item 302(a)(2), this variance would not be disclosed until the following year in the corresponding fiscal quarter in which the retrospective change occurred. Disclosure in the Form 10-Q for this corresponding fiscal quarter would not include the effects of this change in the earliest of the two years presented in the Form 10-K, as this Form 10-Q would be limited to the current and prior-year interim periods.
79. Should we retain or eliminate Item 302(a)? Why? If we retain Item
80. Is fourth quarter information, which is required under Item 302(a) but not in the annual financial statements, important to investors? Do the other instances where disclosure required by Item 302(a) is not duplicative of previously provided disclosure merit retaining the item? Why or why not?
81. The disclosure required by Item 302(a) was originally intended to help investors understand the pattern of corporate activities throughout a fiscal period by disclosing trends over segments of time that are sufficiently short to reflect business turning points.
82. Should we require auditor involvement (
83. Item 302(a) disclosure is commonly provided either as an unaudited note to the financial statements in Form 10-K
84. What types of investors or audiences are most likely to value the information required by Item 302?
85. What is the cost of providing the disclosure required by Item 302, including the administrative and compliance costs of preparing and disseminating this disclosure? How would these costs change if we made any of the changes contemplated here? Please provide quantified estimates where possible and include only those costs associated with providing disclosure under Item 302.
86. Would costs to investors increase if Item 302 was eliminated and if so, how?
87. What are the benefits of providing the disclosure required by Item 302? How could the benefits change if we made any of the changes contemplated here? Please provide quantified or qualitative estimates where possible relating to disclosure under Item 302.
Item 303 of Regulation S-K requires disclosure of information relevant to assessing a registrant's financial condition, changes in financial condition and results of operations.
Overall, these MD&A requirements are intended to satisfy three principal objectives:
• Provide a narrative explanation of a registrant's financial statements that enables investors to see the registrant through the eyes of management;
• enhance the overall financial disclosure and provide the context within which financial information should be analyzed; and
• provide information about the quality of, and potential variability of, a registrant's earnings and cash flow, so investors can ascertain the likelihood that past performance is indicative of future performance.
The Commission has provided substantial guidance in the past intended to improve the quality of MD&A disclosures.
• Quality and focus of analysis;
• forward-looking information; and
• use of key performance indicators.
One commenter suggested consolidating Commission and staff guidance on MD&A, stating that consolidation would reduce the time and effort necessary to identify and read all applicable sources and improve the
MD&A requires not only a discussion but also an analysis of known material trends and uncertainties and should not reiterate financial statement information in a narrative form.
The Commission has focused on improving the analysis in MD&A for many years. For example, the 1989 MD&A Interpretive Release explained that MD&A is intended to give investors an opportunity to look at a registrant through the eyes of management by providing both a short and long-term analysis of the business of the registrant.
Prior to 1980, Commission rules required registrants to provide a summary of earnings, including a discussion of unusual conditions that affected the appropriateness of the earnings presentations.
Commission guidance has continued to stress the importance of materiality in MD&A and stated that disclosure should emphasize material information and de-emphasize or, if appropriate, delete immaterial information.
In addition to emphasizing materiality, the Commission has also recommended a “layered approach” as a way to improve the quality of analysis in MD&A.
Executive-level overviews should discuss the most important matters to MD&A, and the Commission has cautioned that this overview should not be a duplicative layer of disclosure repeated elsewhere.
88. What requirements in Item 303 are important to investors? How could Item 303 be improved?
89. Do the current requirements of Item 303 result in disclosure that
90. There are various sources of Commission and Division guidance on MD&A. These include Commission releases, sections of the Division's Financial Reporting Manual and staff Compliance and Disclosure Interpretations.
91. Should we revise our rules to require registrants to provide an executive-level overview? If so, should our rules prescribe the information that must be covered? What would be the benefits and challenges of prescribing the content of the overview and what content should we require? For example, should we require an executive-level overview to discuss the most significant accounting estimates and judgments? Should any requirement for an executive-level overview be limited to registrants of a certain size?
92. If we were to require an executive-level overview, how could we encourage registrants to provide an overview that does not simply duplicate disclosure provided elsewhere?
93. Are there other methods that registrants could employ or new rules that we should consider that would result in more meaningful analysis in MD&A?
94. What types of investors or audiences are most likely to value the information required by Item 303 and does the audience for disclosure vary across the different parts of Item 303 disclosure? If so, how? Would the manner of presentation affect how various types of investors benefit from Item 303 disclosure?
95. Should we require a different format or presentation of MD&A such as a requirement for the discussion to be tagged or presented in a structured manner?
96. Should we require auditor involvement (
97. What is the cost of providing the disclosure required by Item 303, including the administrative and compliance costs of preparing and disseminating this disclosure? How would these costs change if we made any of the changes contemplated here? Please provide quantified estimates where possible and include only those costs associated with providing disclosure under Item 303.
98. What are the benefits of providing the disclosure required by Item 303? How could the benefits change if we made any of the changes contemplated here? Please provide quantified or qualitative estimates where possible relating to disclosure under Item 303.
Discussion and analysis of known trends, demands, commitments, events and uncertainties requires disclosure of forward-looking information.
In 1987, the Commission distinguished between required and optional forward-looking disclosure: Required forward-looking disclosure is based on currently known trends, events and uncertainties that are reasonably expected to have material effects, while optional forward-looking disclosure involves either anticipating a future trend or event or anticipating a less predictable impact of a known event, trend or uncertainty.
In 1989, the Commission also explained that the safe harbors of Securities Act Rule 175(c) and Exchange Act Rule 3b-6(c) apply to required statements concerning the future effect of known material trends and uncertainties.
The Commission adopted the foregoing rules in 1979 to encourage the disclosure of projections and forward-looking information as recommended by the Sommer Report.
Where a trend, demand, commitment, event or uncertainty is known, management must make two assessments:
(1) Is the known trend, demand, commitment, event or uncertainty likely to come to fruition? If management determines that it is not reasonably likely to occur, no disclosure is required.
(2) If management cannot make that determination, it must evaluate objectively the consequences of the known trend, demand, commitment, event or uncertainty, on the assumption that it will come to fruition. Disclosure is then required unless management determines that a material effect on the registrant's financial condition or results of operations is not reasonably likely to occur.
Several federal courts of appeals have since referenced the Commission's two-step test and addressed its role in potential liability under Exchange Act Section 10(b) and Rule 10b-5 thereunder. Although the courts are divided on the issue of whether Item 303 requirements create a general duty to disclose in the Rule 10b-5 context, these courts have agreed that the Supreme Court's standard in
99. Does the two-step test for disclosure of a known trend, demand, commitment, event or uncertainty result in the most meaningful forward-looking disclosure? Why or why not? How do registrants determine when something is “reasonably likely” to occur?
100. Should we revise the two-step test to apply a different standard in the first prong and if so, how? For example, should we require disclosure when a trend, event or uncertainty is more likely than not, probable, or reasonably possible to occur, rather than “reasonably likely” to occur?
In the context of Item 303(a)(4) (off-balance sheet arrangements), the Commission previously considered whether the “reasonably likely” threshold was appropriate for prospective information. Most commenters supported the “reasonably likely” standard. Many commenters opposed a “remote” threshold stating it would be difficult for management to apply, yield voluminous disclosures; attribute undue prominence to information that is not important to investors; confuse or mislead investors; and elicit information that would not be comparable among firms. The Commission adopted the “reasonably likely” threshold concluding that it focused on the information most important to an understanding of a registrant's off-balance sheet arrangements and their material effects. The Commission also noted potential difficulty in attempting to comply with the “remote” threshold and that use of a consistent threshold throughout MD&A would preclude the potential confusion that could result from disparate thresholds.
101. Should we eliminate the two-step test in favor of a different standard for identifying required and optional forward-looking disclosure and, if so, what test would be appropriate? For example, should we revise Item 303 to incorporate the probability/magnitude standard from
102. We have stated previously that quantification of the material effects of known material trends and uncertainties can promote understanding and may be required to the extent material.
The Commission has previously stressed that registrants should identify and address those key variables and other qualitative and quantitative factors that are peculiar to and necessary for an understanding and evaluation of the individual registrant.
Some registrants discuss industry-specific key performance indicators in MD&A, although there is not a specific requirement for this disclosure. For example, electronic gaming or social media companies typically discuss their numbers of monthly active users; numbers of unique users; numbers of unique payers; and other metrics relating to usage. Software service companies typically discuss their numbers of subscribers; customer renewal rates; and customer retention rates. Hospitals typically discuss their numbers of admissions; numbers of beds; the average length of inpatient stays; and occupancy rates. Retailers typically discuss comparable store sales, sales per square foot or gross merchandise value. Recent academic studies find that the industry-specific key factors disclosed by retailers and manufacturers provide incremental information that can help to predict registrants' future performance beyond traditional financial statement variables.
Where there is no commonly accepted method of calculating a particular non-financial metric, the Commission has said that the registrant should provide an explanation of the calculation of the metric to promote comparability across registrants within the industry.
103. Should we revise Item 303 to include a principles-based requirement for all registrants to disclose performance metrics and other key variables important to their business? Why or why not?
104. Should we require disclosure of any commentary, analysis, performance indicators or business drivers related to a registrant's key indicators? If so, why? For example, would it be feasible to adopt prescriptive requirements for discussion of specific performance metrics that are applicable to an entire industry and are easily comparable between registrants?
105. What types of investors or audiences are most likely to value industry-specific key performance indicators?
106. What would be the costs and benefits of requiring registrants in certain industries to disclose standardized performance metrics? How could we identify which performance metrics should be standardized across an industry?
Item 303(a)(3) requires a discussion and analysis of a registrant's results of operations and specifies four areas of disclosure:
• Any unusual or infrequent events or transactions or any significant economic changes that materially affected the amount of reported income from continuing operations and the extent to which income was so affected;
• known trends or uncertainties that have had, or that the registrant reasonably expects will have, a material impact on net sales or revenues or income from continuing operations;
• material increases in net sales or revenues, including the extent such increases are attributable to increases in prices, increases in the volume or amount of goods or services being sold, or to the introduction of new products or services;
• for the three most recent fiscal years, a discussion of the impact of inflation and changing prices on the registrant's net sales and revenues, and on income from continuing operations.
Instruction 1 to Item 303(a) states that the discussion and analysis shall cover the three-year period covered by the financial statements and use year-to-year comparisons or any other format that in the registrant's judgment would enhance a reader's understanding.
One commenter disagreed with eliminating the requirement to include prior-period results in MD&A because doing so would require investors to look for the information elsewhere.
Prior to the Commission's adoption of the MD&A disclosure requirements, Guide 22 and Guide 1 called for a summary of earnings and operations, as well as a full narrative explanation of the summary. The Guides also called for a separate discussion and analysis of the summary, including explanations of material changes from period to period in revenues and expenses.
In 2003, the staff conducted a review of annual reports filed by all Fortune 500 registrants and issued a significant number of comments seeking, among other things, greater analysis of
107. Should we retain, eliminate or modify the period-to-period comparisons provided in MD&A? Why?
108. How could Item 303(a)(3) be improved? Would any additional disclosure about a registrant's results of operations be important to investors? If so, what additional disclosure would be important and why?
109. Does the three-year comparison provide material information about trends or uncertainties that would not be reflected in filings for prior periods? Should we permit registrants to omit the earliest period in the three-year comparison when the earliest of the three years does not provide information that is important to investors? What would be the advantages and disadvantages of limiting the period-to-period comparisons in MD&A to the most recent two fiscal periods?
110. Should we allow registrants to eliminate the earliest of the two periods discussed so long as they cross-reference or include a hyperlink to the prior periods discussion in earlier Forms 10-K and 10-Q? Why or why not?
111. In complying with Item 303(a)(3), registrants almost exclusively rely on period-to-period comparisons even though our rules permit “any other format that in the registrant's judgment would enhance a reader's understanding.”
112. Does the disclosure required by Item 303(a)(3) provide useful information about registrants that have not yet generated revenue or begun operations? Would additional disclosure about these registrants, such as a description of their plans of operations be more useful to investors? If so, what additional information, if any, that is not already required under Item 101(a)(2) would be useful to investors?
Analysis of a registrant's liquidity and capital resources is critical to assessing a registrant's future prospects.
Item 303(a)(2) requires discussion and analysis of a registrant's capital resources. A registrant must describe its material commitments for capital expenditures and indicate the general purpose of those commitments and the anticipated source of funds needed to fulfill those commitments.
The Commission first adopted requirements for disclosure of liquidity and capital resources in 1980 to address what it viewed as a growing need to analyze enterprise liquidity and capital resources in addition to revenues and income.
Despite the Commission's guidance, the staff has observed that discussions of liquidity and capital resources often recite various changes in line items from the statement of cash flows without a detailed analysis. Although registrants generally discuss their liquidity needs and the sources of cash available to meet those needs as of the end of the reporting period, disclosure of known trends and uncertainties affecting their future needs and availability of cash often is less detailed.
When adopting disclosure requirements for liquidity and capital resources, the Commission recognized that the terms “liquidity” and “capital resources” lacked precision in definition but stated that “additional specificity would decrease the flexibility needed by management for a meaningful discussion.”
113. How could we revise Item 303(a) to elicit a more meaningful analysis of a registrant's liquidity and capital resources while retaining the flexibility of registrants to analyze liquidity and capital resources in the context of their business and the way they manage liquidity?
114. Item 303(a) provides that discussions of liquidity and capital resources may be combined whenever the two topics are interrelated. Would it lead to more useful analysis if we required registrants to provide separate disclosure of these two topics? Why? Would doing so encourage greater disclosure of trends, events and uncertainties affecting capital resources?
115. When drafting MD&A, how do registrants currently interpret the term “capital resources”? Would defining the term “capital resources” be helpful for registrants or, alternatively, is the plain meaning of the term sufficiently clear? In light of the reference to capital expenditures and the sources of funds needed to fulfill those expenditures in Item 303(a)(2)(i), do registrants currently interpret the term “capital resources” as including mostly funds committed for material capital expenditures and the source of those funds?
116. Should we modify the definition of “liquidity” in Instruction 5 to Item 303(a) and, if so, how?
117. For what periods should we require discussion and analysis of liquidity and capital resources and why? Should our requirements include more periods than what is required by the statement of cash flows? Why? Are developments in the most recent fiscal year sufficient to constitute a “trend” as the term is used in Item 303?
118. Should we require registrants to provide a sensitivity analysis in the discussion and analysis of liquidity and capital resources? If so, what should be the nature of such an analysis? If not, why not?
119. Should the registrant provide additional measures of intra-period liquidity and capital resources? For example, should the registrant provide measures of average daily liquidity, average quarterly liquidity, or other measures? Should the registrant provide a chart or graph of intra-period liquidity? How should such information be considered in connection with the information provided at the end of the quarter?
120. Should we consider more detailed disclosure requirements for liquidity, such as liquidity risks and maturity mismatches?
Access to short-term borrowings for working capital and to fund operations can be an important component of a registrant's liquidity and capital resources.
Short-term borrowings are common among financial institutions and industrial companies alike.
Short-term borrowings can be affected, sometimes severely and rapidly, by illiquidity in the markets as a whole.
Our rules require a liquidity analysis on both a long-term and short-term basis.
The Commission has previously considered the applicability of short-term borrowing disclosure requirements for all registrants. In 1994, in connection with the elimination of various financial statement disclosure schedules, the Commission eliminated a short-term borrowings disclosure requirement for registrants that were not bank holding companies.
In 2010, the Commission proposed new disclosure requirements for short-term borrowings.
While a number of commenters generally supported the proposed rules' objectives of greater transparency of short-term borrowings as part of a registrant's overall liquidity profile, they also expressed numerous concerns about the quantitative requirements of the proposed rule. For example, commenters were opposed to the
The proposed rule was a change from existing Industry Guide 3 instructions, which allows categories of short-term borrowings to be aggregated where they do not exceed thirty percent of the company's stockholders' equity at the end of the period. Instruction to Item VII of Industry Guide 3.
121. Do current disclosure requirements under Item 303 elicit adequate disclosure of a registrant's reliance on short-term borrowings?
122. Should we revise Item 303 to require specific line-item disclosure of a registrant's use and analysis of short-term borrowings as a source of funding? Are there aspects of the 2010 proposal we should revisit? Would doing so lead to any additional disclosure or analysis that registrants do not already provide under current requirements and guidance? Should we consider other qualitative or quantitative measures for disclosure of short-term borrowings? If so, what measures should we consider?
123. Should we consider different disclosure requirements for financial institutions versus non-financial institutions? If so, which disclosure should we require and why?
124. Should we require registrants to provide chart or graph of its short-term borrowings?
Item 303(a)(4) requires, in a separately-captioned section, disclosure of a registrant's off-balance sheet arrangements that have or are reasonably likely to have a current or future effect on a registrant's financial condition, changes in financial condition, revenues or expenses, results of operations, liquidity, capital expenditures or capital resources that is material to investors.
• The nature and business purpose of such off-balance sheet arrangements;
• the importance to the registrant of such off-balance sheet arrangements in respect of its liquidity, capital resources, market risk support, credit risk support or other benefits;
• the amounts of revenues, expenses and cash flows arising from such arrangements; the nature and amounts of any interests retained, securities issued and other indebtedness incurred in connection with such arrangements; and the nature and amounts of any other obligations or liabilities (including contingent obligations or liabilities) of the registrant arising from such arrangements that are or are reasonably likely to become material and the triggering events or circumstances that could cause them to arise; and
• any known event, demand, commitment, trend or uncertainty that will result in or is reasonably likely to result in the termination, or material reduction in availability of a registrant's off-balance sheet arrangements that provide material benefits, and the course of action that the registrant has taken or proposes to take in response to any such circumstances.
Item 303(a)(4)(ii) defines off-balance sheet arrangements as certain guarantees, retained or contingent interests in assets transferred to an unconsolidated entity, obligations under certain derivative instruments,
The Sarbanes-Oxley Act required the Commission to adopt rules providing that each annual and quarterly financial report required to be filed with the Commission must include disclosure about off-balance sheet arrangements.
In its 2002 statement, the Commission noted that off-balance sheet arrangements often are integral to both liquidity and capital resources and that registrants should “consider all of these items together, as well as individually,”
The 2002 statement was consistent with Commission rules and guidance existing at the time. For example, Item 303(a)(2)(ii) specifically required registrants to disclose off-balance sheet financing arrangements in their discussion of capital resources.
In response to the Sarbanes-Oxley Act, the Commission adopted more specific disclosure requirements for off-balance sheet arrangements in 2003.
In 2004, as part of a broader effort to expand the events that registrants must report on a current basis, the Commission adopted additional requirements for disclosing off-balance sheet arrangements on Form 8-K.
In the proposing release for Item 303(a)(4), the Commission recognized that parts of the proposed off-balance sheet disclosure requirements might overlap with disclosure presented in the footnotes to the financial statements. The Commission stated that the proposed rules were designed to provide more comprehensive information and analysis in MD&A than what was provided in the footnotes.
Since the adoption of Item 303(a)(4), the FASB has issued additional requirements that further overlap with this item.
Because of this overlap, in response to Item 303(a)(4), registrants often provide cross-references to the relevant notes to their financial statements or provide disclosure that is duplicative of information in the notes. While many of the requirements in Item 303(a)(4) overlap with U.S. GAAP, some of the requirements related to the location, presentation and nature of the disclosure are not the same. Additionally, Item 303(a)(4) disclosure is not audited.
Item 303(a)(4)(i) specifies that off-balance sheet arrangements should be discussed in a separately-captioned section. The instructions to Item 303(a)(4) permit that discussion to cross-reference to information provided in the footnotes to the financial statements, rather than repeat it, provided that the MD&A disclosure integrates the substance of the footnotes in a manner designed to inform readers of the significance of the information that is cross-referenced.
125. Does Item 303(a)(4) elicit disclosure that is important to investors? Is this information otherwise available in Commission filings?
126. If we retain the disclosure requirements in Item 303(a)(4), should we expand the disclosure required by this item? If so, what additional disclosure would be important to investors and why? For example, should we revise our rules to require registrants to analyze the risks and financial potential associated with its off-balance sheet arrangements?
127. If we retain the disclosure requirements in Item 303(a)(4), should this information be located in MD&A, the notes to the financial statements, or both? Is the location of the disclosure important? Are there challenges associated with auditing this information?
128. If we eliminate Item 303(a)(4), do the other requirements in Item 303 and the requirements in U.S. GAAP require adequate disclosure in terms of the location, presentation and nature of information about off-balance sheet arrangements? Would eliminating Item 304(a)(4) result in costs to investors?
129. In the adopting release for Item 303(a)(4), the Commission noted that “[t]he MD&A rules already require disclosure regarding off-balance sheet arrangements and other contingencies.”
130. Should we require additional disclosure of off-balance sheet arrangements that occurred during a reporting period, such as an exhibit identifying all such arrangements?
Item 303(a)(5) requires tabular disclosure of a registrant's known contractual obligations for long-term debt, capital leases, operating leases, purchase obligations and other long-term liabilities reflected on the registrant's balance sheet under U.S. GAAP.
For purchase obligations, the Commission defined this term as an agreement to purchase goods or services that is enforceable, legally binding on the registrant and specifies all significant terms.
The fifth category of contractual obligations, “Other Long-Term Liabilities Reflected on the Registrant's Balance Sheet under GAAP,” captures all other long-term liabilities that are reflected on the registrant's balance sheet under the registrant's applicable U.S. GAAP. Common examples of other obligations disclosed in this line-item of the table include postretirement benefits, interest on debt, and tax liabilities for uncertain tax positions.
Item 303(a)(5) requires registrants to disclose the amounts of payments due by specified time periods, aggregated by the type of contractual obligation.
In response to a 2001 petition for an interpretive release,
When adopting Item 303(a)(5), the Commission recognized that much of the disclosure required by this item is addressed under U.S. GAAP requirements.
Item 303(a)(5) directly refers to ASC Topics in defining three of the five required categories of contractual obligations that must be included within the table.
By providing aggregated information of contractual obligations in a single location and appropriate context for investors to assess the impact of off-balance sheet arrangements with respect to liquidity and capital resources, Item 303(a)(5) was intended to improve transparency of a registrant's short- and long-term liquidity and capital resource needs. This disclosure was also intended to “improve an investor's ability to compare registrants.”
The Commission has issued guidance on Item 303(a)(5) on one occasion since its adoption.
The Commission's guidance also explained that tabular disclosure of contractual obligations should be prepared with the goal of presenting a meaningful snapshot of cash requirements arising from contractual payment obligations. Registrants were instructed to highlight any changes in presentation that are made so that investors may use the information to make comparisons from period to period. The Commission suggested that footnotes should be used to provide information necessary for an understanding of the timing and amount of specified contractual obligations. Registrants also should consider additional narrative discussion outside of the table to promote understanding of the tabular data.
131. Does the table of contractual obligations present a meaningful snapshot of a registrant's cash requirements for contractual obligations? How could the format of the disclosure in the table be improved? Should we consider an alternative presentation or format for this disclosure?
132. Should we require narrative disclosure to accompany the tabular disclosure? For example, should we require registrants to discuss how they plan to meet current and future obligations disclosed in the table? If so, what additional narrative disclosure would be useful to investors?
133. Item 303(a)(5) was intended to provide aggregated information of contractual obligations in a single location and appropriate context for investors to assess the impact of off-balance sheet arrangements with respect to liquidity and capital resources. Would narrative disclosure improve readers' ability to compare registrants by reconciling the information in the table to information elsewhere in MD&A and financial statements? Should comparability among registrants continue to be a goal? Should we continue to require this disclosure in a single location or is disclosure elicited under U.S. GAAP, in various parts of a registrant's filings, sufficient?
134. Item 303(a)(5) requires disclosure of five categories of contractual obligations. Should we expand the rule to include other categories of contractual obligations and if so, what categories should we consider?
135. Would additional guidance or instructions about how to treat certain types of obligations, such as interest payments, repurchase agreements or tax liabilities, be helpful to registrants in preparing this disclosure? Would such guidance limit the intended flexibility of the rule?
136. In the 2010 Liquidity and Capital Resources Interpretive Release, the Commission suggested that separating amounts in the table into those that are reflected on the balance sheet and those arising from off-balance arrangements might be useful to a clear understanding of the information presented. Should we revise Item 303(a)(5) to require registrants to separate amounts in the table of contractual obligations into those that are reflected on the balance sheet and those arising from off-balance sheet arrangements? Should we require this disclosure pursuant to some threshold amount?
A registrant's results of operations, financial condition, and changes to financial condition often depend on estimates involved in applying accounting policies that entail uncertainties and subjectivity. Critical accounting estimates are those accounting judgments and estimates that relate to the items that are material to the financial statements, taken as a whole, and that management believes are most critical—that is, those that are most important to portraying the registrant's financial condition and results and require management's most difficult, subjective or complex judgments.
In 2001, the Commission encouraged registrants to explain in their MD&A the judgments and uncertainties affecting the application of their critical accounting policies, as well as the likelihood that materially different amounts would be reported under different conditions or using different assumptions.
In 2002, the Commission proposed new rules that would have required, among other things, disclosure of accounting estimates resulting from the application of critical accounting policies.
• Describe the critical accounting estimates (including the methodology underlying each critical accounting estimate, assumptions about highly uncertain matters and other assumptions that are material) and identify where and how they affect the registrant's reported financial results, financial condition and changes in financial condition;
• provide a better understanding of the sensitivity of the reported operating results and financial condition to changes in the critical accounting estimates or their underlying assumptions;
• state whether or not senior management discussed the development, selection and disclosure of those critical accounting estimates with the registrant's audit committee.
The Commission did not adopt these rules, but subsequently provided interpretive guidance on disclosure of critical accounting estimates.
• The nature of the estimates or assumptions is material due to the levels of subjectivity and judgment necessary to account for highly uncertain matters or the susceptibility of such matters to change; and
• the impact of the estimates and assumptions on financial condition or operating performance is material.
The FASB has also stated that distinguishing between a change in an accounting principle and a change in an accounting estimate is sometimes difficult, and in some cases, a change in accounting estimate is effected by a change in accounting principle.
Despite Commission guidance, many registrants repeat the discussion of significant accounting policies from the notes to the financial statements in their discussion of critical accounting estimates in MD&A and provide limited additional discussion of the critical accounting estimates. We are seeking public input on how to revise our requirements to improve the discussion of critical accounting estimates in MD&A.
137. Should we revise Item 303 to require disclosure about critical accounting estimates? If so, what information would be important to investors?
138. Should we define “critical accounting estimates”? If so, should the definition be based on our 2001 guidance,
139. Why do registrants repeat the discussion of accounting policies presented in the notes to the financial statements? How can we encourage registrants to eliminate repetition in MD&A of the discussion of accounting policies provided in the notes to the financial statements?
140. Do registrants find the guidance for disclosing critical accounting estimates from the 2003 MD&A Interpretive Release helpful in determining whether such disclosure is required? Would it be helpful for registrants if we incorporated this or other elements of our guidance on critical accounting estimates into Regulation S-K?
141. Should we revise our requirements to elicit more comparable disclosure among registrants? If so, how? Should we adopt prescriptive requirements relating to critical accounting estimates? Are there any accounting estimates common to a particular industry that are “critical” to all participants in that industry?
142. Should we require the disclosure of management's judgments and estimates that form the basis for MD&A disclosure? For example, should we require registrants to disclose the quantitative and qualitative factors that form its assessment of materiality? Should we require registrants to disclose how they assessed materiality?
143. Should we require management to disclose the nature of its assessment of errors that it determined to be immaterial and therefore were not corrected?
144. Should we require disclosure of other critical accounting estimates, such as those that impact other metrics or measures, such as the number of new customers or the number of subscribers?
Disclosure of a registrant's most significant risks provides investors with important context for assessing the registrant's financial potential. Risk-related disclosure is required by multiple items of Regulation S-K and certain financial reporting requirements.
• Item 503(c), which requires disclosure of the most significant factors that make an investment in a registrant's securities speculative or risky;
• Item 305, which requires quantitative and qualitative disclosure about market risk.
Item 503(c) requires disclosure of the most significant factors that make an investment in a registrant's securities speculative or risky and specifies that the discussion should be concise and organized logically.
• A registrant's lack of an operating history,
• a registrant's lack of profitable operations in recent periods,
• a registrant's financial position,
• a registrant's business or proposed business, or
• the lack of a market for a registrant's common equity securities or securities convertible or exercisable for common equity securities.
One commenter stated that risk factors should be more entity-specific and connected to financial results.
Several comment letters stated there should be additional risk-related disclosure on specific topics.
We received two comment letters on the impact of the Private Securities Litigation Reform Act (“PSLRA”) on risk-related disclosure. One commenter acknowledged that liability concerns may contribute to the length of Exchange Act documents but expressed concern about any effort to require issuers to reduce the length or number of risk factors included in a filing.
The five factors specified in Item 503(c) as factors that may make an offering speculative or risky have not changed since the Commission published its initial guidance on risk factor disclosure in 1964. These factors were derived from previous stop order proceedings under Section 8(d) of the Securities Act where the Commission suspended the effectiveness of previously filed registration statements due, in part, to inadequate disclosure about speculative aspects of the registrant's business.
Since the Commission first published guidance on risk factor disclosure in 1964,
• Focused on the “most significant” or “principal” factors that make a registrant's securities speculative or risky,
• placed in the forefront of the filing,
• organized and concise.
The length and number of risk factors disclosed by registrants varies. Although Item 503(c) directs registrants to provide a concise risk factors discussion, one study found that registrants include an average of 22 different risk factors in disclosure spanning an average of 8 pages.
Although Item 503(c) instructs registrants not to present risks that could apply to any registrant, risk factor disclosure typically includes generic risk factors. Registrants often use risk factors that are similar to those used by others in their industry or circumstances as the starting point for risk disclosure, and the disclosure is not always tailored to each registrant's particular risk profile. Examples of generic disclosures include risk factors about a registrant's failure to compete successfully, the effect of general economic conditions on a registrant's business, changes in regulation, and dependence upon a registrant's
145. How could we improve risk factor disclosure? For example, should we revise our rules to require that each risk factor be accompanied by a specific discussion of how the registrant is addressing the risk?
146. Should we require registrants to discuss the probability of occurrence and the effect on performance for each risk factor? If so, how could we modify our disclosure requirements to best provide this information to investors? For example, should we require registrants to describe their assessment of risks?
147. How could we modify our rules to require or encourage registrants to describe risks with greater specificity and context? For example, should we require registrants to disclose the specific facts and circumstances that make a given risk material to the registrant? How should we balance investors' need for detailed disclosure with the requirement to provide risk factor disclosure that is “clear and concise”? Should we revise our rules to require registrants to present their risk factors in order of management's perception of the magnitude of the risk or by order of importance to management? Are there other ways we could improve the organization of registrants' risk factors disclosure? How would this help investors navigate the disclosure?
148. What, if anything, detracts from an investor's ability to gain important information from a registrant's risk factor disclosure? Do lengthy risk factor disclosures hinder an investor's ability to understand the most significant risks?
149. How could we revise our rules to discourage registrants from providing risk factor disclosure that is not specific to the registrant but instead describes risks that are common to an industry or to registrants in general? Alternatively, are generic risk factors important to investors?
150. Should we specify generic risks that registrants are not required to disclose, and if so, how should we identify those risks? Are there other ways that we could help registrants focus their disclosure on material risks?
151. Should we retain or eliminate the examples provided in Item 503(c)? Should we revise our requirements to include additional or different examples? Would deleting these examples encourage registrants to focus on their own risk identification process?
152. Should we require registrants to identify and disclose in order their ten most significant risk factors without limiting the total number of risk factors disclosed?
153. Are there ways, in addition to those we have used in Item 503, our Plain English Rules and guidance on MD&A, to ensure that registrants include meaningful, rather than boilerplate, risk factor disclosure?
154. Risk profiles of registrants are constantly changing and evolving. For example, registrants today face risks, such as those associated with cybersecurity, climate change, and arctic drilling,
155. What types of investors or audiences are most likely to value the Item 503(c) disclosures?
156. What is the cost of providing the disclosure required by Item 503(c), including the administrative and compliance costs of preparing and disseminating this disclosure? How would these costs change if we made any of the changes contemplated here? Please provide quantified estimates where possible and include only those costs associated with providing disclosure under Item 503(c).
Item 305 requires quantitative and qualitative disclosure of market risk sensitive instruments that affect a registrant's financial condition.
(1) Tabular presentation of fair value information and contract terms relevant to determining future cash flows, categorized by expected maturity dates;
(2) Sensitivity analysis expressing the potential loss in future earnings, fair values, or cash flows from selected hypothetical changes in market rates and prices; or
(3) Value at risk (“VaR”) disclosures expressing the potential loss in future earnings, fair values, or cash flows from market movements over a selected period of time and with a selected likelihood of occurrence.
Registrants are required to categorize market risk sensitive instruments into instruments entered into for trading purposes and instruments entered into for purposes other than trading.
Item 305(b) requires qualitative information about market risk. Registrants must describe, to the extent material, their primary market risk exposures, how those exposures are managed, and any changes to either the primary market risk exposures or the way that risk exposures are managed.
The 2012 Exposure Draft aimed to provide more useful information on exposures to liquidity risk and to interest rate risk by requiring, among other things, tabular disclosure of liquidity risk related to financial assets and financial liabilities or cash flow obligations, disaggregated by expected maturities; carrying amounts of classes of financial assets and financial liabilities, segregated according to time intervals based on contractual repricing; an interest rate sensitivity table showing the effects on net income and shareholder equity of specific hypothetical shifts of interest rates; and quantitative or narrative disclosure as necessary to understand exposures to liquidity risk and interest rate risk. For a discussion of the 2012 Exposure Draft,
The adequacy of market risk disclosure emerged as an important financial reporting issue in the 1990s following a substantial increase in the use of derivatives and other instruments subject to market risk and the significant, sometimes unexpected, losses registrants experienced from their use of these instruments.
To achieve these goals, the Commission used the following guiding principles in adopting Item 305:
• Disclosures should make transparent the impact of derivatives on a registrant's statements of financial position, cash flows, and results of operations;
• Disclosures should provide information about a registrant's exposures to market risk;
• Disclosures should explain how market risk sensitive instruments are used in the context of the registrant's business;
• Disclosures about market risk exposures should not focus on derivatives in isolation, but rather should reflect the risk of loss inherent in all market risk sensitive instruments;
• Market risk disclosure requirements should be flexible enough to accommodate different types of registrants, different degrees of market risk exposure, and alternative ways of measuring market risk;
• Disclosures about market risk should address, where appropriate, special risks relating to leverage, option, or prepayment features; and
• New disclosure requirements should build on existing requirements, where possible, to minimize compliance costs.
Item 305 was designed to address concerns that market risks associated with derivatives and other market-sensitive instruments were not adequately disclosed.
Division staff has observed that the instructions to Item 305 may inadvertently discourage some disclosure. For example, a sensitivity analysis requires disclosure of the potential loss to the future earnings, fair values, or cash flows of market risk sensitive instruments from a hypothetical change in rates or prices.
Considering commenters' differing views on the efficacy of Item 305 and the complexity of Item 305's required disclosures, we seek input on whether, and how, changes to Item 305 would be beneficial to both investors and registrants.
157. Is Item 305 effective in eliciting disclosure about market risks and risk management practices that investors consider important? If not, how could Item 305 be improved?
158. Does Item 305 result in information that allows investors to effectively assess (1) a registrant's aggregate market risk exposure, and (2) the impact of market risk sensitive instruments on a registrant's results of operations and financial condition? If not, how could we revise Item 305 to achieve these goals?
159. Do the disclosure alternatives in Item 305(a) elicit adequate quantitative disclosure about market risk? Do the rules or the instructions discourage registrants from fully evaluating and disclosing their market risk exposures, such as in a sensitivity analysis? Should the rules be more prescriptive? If so, in what ways should we revise the rules and instructions to Item 305(a)?
160. Should additional or different principles guide the market risk disclosure requirements? Should we expand our definition of “market risk sensitive instruments” to require registrants to provide additional disclosure about other risks, including credit risk, liquidity and funding risk and operational risk?
161. Should we limit the quantitative disclosure requirement to certain registrants such as financial institutions or registrants engaged in financial services? Why or why not?
162. What types of investors or audiences are most likely to value the information required by Item 305?
163. What is the cost of providing the disclosure required by Item 305, including the administrative and compliance costs of preparing and disseminating this disclosure? How would these costs change if we made any of the changes contemplated here? Please provide quantified estimates where possible and include only those costs associated with providing disclosure under Item 305.
Item 305(a) specifies three disclosure alternatives for registrants to present quantitative information about market risk: Tabular disclosure, sensitivity analysis, and VaR.
In response to the proposing release for Item 305, some commenters suggested greater flexibility and recommended a “management approach” to disclosure. As suggested by the commenters, this disclosure would focus on the information and methods that management actually uses internally to evaluate, monitor, and manage market risk.
We are also interested in whether we should modify Item 305 given accounting developments since the item's adoption. When the Commission adopted Item 305 in 1997, minimal authoritative literature on the accounting for options and complex derivatives existed.
Item 305 disclosure also tends to vary among registrants. Many registrants provide a sensitivity analysis to present market risk information, while others rely on tabular presentation or VaR. For large financial institutions, it is not unusual to use some combination of the three to capture different market risk sensitive instruments.
164. How have standard risk management practices and methods of reporting market risk evolved since the adoption of Item 305 in 1997? Should we revise Item 305 to reflect those changes and if so, how? Should we provide for new disclosure alternatives in addition to, or in lieu of, existing alternatives?
165. What revisions should we consider to better link disclosure that identifies, quantifies, and analyzes a registrant's material market risks to its: (a) Market risk sensitive instruments, (b) financial statements, (c) capital adequacy, and (d) any other metrics important to an understanding of market risk exposures?
166. Should we eliminate the prescribed disclosure alternatives and allow registrants to discuss market risk according to the methods used by management to manage the risk? Would allowing a “management approach” provide investors with more insight about the way management actually assesses market risks, or would this approach unduly hinder investors' ability to compare market risk disclosures across registrants?
167. Is the disclosure required by Item 305 repetitive of the disclosure required by U.S. GAAP and Rule 4-08 of Regulation S-X? Conversely, does Item 305 result in disclosure that is important to investors and is not found elsewhere in a registrant's filing? Even considering any repetition, do investors benefit from disclosure about market risk exposure outside of the audited financial statements?
In adopting Item 305, the Commission acknowledged the tension between approaches to market risk disclosure that favor comparability and approaches that favor flexibility.
The Commission designed Item 305 to be flexible by prescribing three disclosure alternatives without stipulating standardized methods and procedures specifying how to comply with each alternative.
To address comparability, the Commission included a requirement that registrants describe the characteristics of the model and the assumptions used to prepare the quantitative market risk disclosures. By requiring a description of the model and its assumptions, the Commission intended to assist investors in evaluating the potential effect of variations in the model's characteristics and assumptions.
In 2012, the FASB examined the question of comparability and considered standardizing liquidity and interest rate risk disclosure as part of a project that is currently in Exposure Draft form.
This Exposure Draft was partly in response to demand by users for audited, standardized, and consistent disclosures by public companies. The Exposure draft noted that, as part of a May 2010 proposed Accounting Standards Update (Accounting for Financial Instruments and Revisions to the Accounting for Derivative Instruments and Hedging Activities—Financial Instruments (Topic 825) and Derivatives and Hedging (Topic 815)), the FASB performed extensive outreach and received feedback that the risks inherent in a class of financial instruments and the way in which an entity manages those risks through its business operations should be instrumental in developing the reporting model for financial instruments. The important risks identified by users of financial statements during the FASB's outreach efforts were credit risk, liquidity risk, and interest rate risk.
Although initiated, in part, as a response to comments received from financial statement users to an earlier FASB release on financial statements, the majority of respondents to the Exposure Draft, eighty-four percent of whom were preparers, did not support the proposed disclosures.
168. Should we revise Item 305 to provide for more standardized disclosure that would enhance comparability among registrants? How should we balance standardization with different methods and assumptions that registrants may use to evaluate, monitor, and manage market risk? How would standardization affect investors and registrants?
Item 503(c) focuses exclusively on disclosure of significant risks and does not address disclosure of a registrant's strategy for managing risk. Item 305(b), however, requires disclosure about a registrant's primary market risks and how those risks are managed. In the past, Commission staff has discouraged registrants from including mitigating language in their Item 503 risk factor disclosure because of concern that mitigating language could dilute investors' perception of the magnitude of the risk. As a result, registrants typically do not discuss their efforts to mitigate risk in connection with their risk factors disclosure, although some registrants describe their risk management practices elsewhere in their filings, such as in MD&A and as required by Item 305 for market risk.
Disclosure about a registrant's approach to risk management could enhance investor understanding of the possible impact of a disclosed risk and the registrant's overall risk profile. Division staff has observed that most large financial institutions have implemented enterprise risk management programs and currently include detailed disclosure about those programs in their filings. Additional disclosure about changes to, or significant deviations from, the stated policies could provide investors with important information about the registrant's exposure to risk.
We are mindful of the potential drawbacks of requiring registrants to provide risk management or risk mitigation disclosure. Disclosure of management's efforts to mitigate risk may suggest to investors that the registrant's risk exposure is not significant. In addition, risk management strategies could include confidential or proprietary information and disclosure could result in competitive harm to the registrant. For example, a registrant may develop and rely on a proprietary method for hedging financial risk, and disclosure of the method could allow others to exploit or trade against the method such that it is no longer effective or becomes too expensive.
169. Should we require registrants to describe their risk management processes? If so, what level of detail would be appropriate? If a registrant has no formal risk management approach or process, should we require it to describe how it monitors and evaluates risk?
170. Should we require registrants also to describe their assessment of any risk management process? If so, how often should such disclosure be required?
171. Should we require registrants with complex risk management approaches or processes to provide only an enterprise-level description, or is a more granular description appropriate for these registrants?
172. Should we require registrants to disclose when risk tolerance limits or other fundamental aspects of its risk management approach are waived or changed, including any assumptions or relevant changes in business strategy that underlies the new limits or policies?
173. Should we require registrants to identify, if material, other “primary risk exposures” not already addressed and to disclose actions taken to manage those risks?
174. How could we facilitate a more integrated discussion of risk exposure and risk mitigation? Should we require registrants to disclose management's view of how material risk exposures are related and how risk mitigation actions are connected?
175. To the extent we require disclosure of risk management and risk management processes, should we move the disclosure about the extent of a board of directors' oversight of risk from Item 407(h) to this new requirement? Similarly, should we move compensation risk disclosure to this new requirement, or should we otherwise provide an option for compensation risk disclosure to be given in the risk management discussion rather than in the compensation discussion?
176. Should we require registrants to disclose their efforts to manage or mitigate each risk factor disclosed, similar to the risk management disclosure required for market risk under Item 305(b)(1)(ii)? What are the challenges, including those associated with preparation and competitive harm, with this disclosure?
177. Would additional disclosure about risk mitigation inhibit investors' ability to fully appreciate the significance of the risk? Would requiring a registrant to explain how it addresses a disclosed risk discourage registrants from disclosing generic or insignificant risks? Alternatively, would registrants provide boilerplate disclosure about how they address less meaningful risks, thereby resulting in even longer risk factor disclosure?
178. Should we require registrants to address mitigation or management of each risk factor as part of the risk management discussion? If so, should we also clarify that, although references to the general risk management discussion will not satisfy this requirement, cross-references to appropriate portions of MD&A or the financial statements will, if disclosure otherwise would be redundant?
179. Should we require registrants to disclose their known uncertainties about their risk management and risk management policies and how these might affect the registrant?
Outside of Items 503(c) and 305, a number of Items in Regulation S-K elicit risk-related disclosures. These include Item 103, related to material litigation and certain environmental proceedings; Item 101(d)(3), in connection with risk related to foreign operations; Item 303(a), in that material trends, uncertainties, or events that are required to be described may also speak to certain risks; and Item 407(h), regarding the extent of a board's role in risk oversight. In the S-K Study, the staff recommended that we consider whether to consolidate requirements relating to risk factors, legal proceedings, and other quantitative and qualitative information about risk and risk management into a single requirement.
180. Should we require registrants to provide a consolidated discussion of risk and risk management, including legal proceedings, in a single section of a filing? If so, what information should be included? How should this information be presented?
181. How could investors benefit from a consolidated discussion of risk factors, legal proceedings and other quantitative and qualitative information about market risk and risk management? What would be the challenges of requiring such a presentation?
182. How would a consolidation of risk-related disclosure affect the cost of preparing a filing, if at all?
Disclosure about a registrant's capital stock and transactions by registrants in their own securities helps inform investment and voting decisions by providing investors with information about a security that can be useful in assessing its value. Several items in Regulation S-K require this and related disclosure about a registrant's securities:
• Item 202 requires a description of the terms and conditions of securities that are being registered;
• Item 701 requires disclosure of recent sales of unregistered securities and use of proceeds from registered offerings of securities;
• Item 703 requires tabular disclosure of shares of equity securities purchased by the registrant and affiliated purchasers.
Additionally, Item 201(b)(1) requires disclosure of the number of holders of each class of a registrant's common equity.
Item 201(b)(1) requires disclosure of the approximate number of holders of each class of common equity as of the latest practicable date.
Several decades ago, most investors of U.S. publicly traded registrants owned their securities in registered form, meaning that the securities were directly registered in the name of a specific investor on the record of security holders maintained by or on behalf of the registrant. Today, the vast majority of investors own their securities as a beneficial owner
In 1964, the Commission proposed amending Form 10-K to require registrants to disclose, in addition to the number of record holders, the amount of each class of equity securities known by the registrant to be held “in street names.”
Item 201(b)'s reference to record holders is consistent with Section 12(g) of the Exchange Act. Section 12(g) requires issuers that are not banks, bank holding companies or savings and loan holding companies and have total assets exceeding $10 million to register a class of equity securities if the securities were “held of record” by either (i) 2,000 persons, or (ii) 500 persons who are not accredited investors.
183. Should we retain or eliminate Item 201(b)(1)? Why? If retained, should we modify the item and if so, how?
184. As the vast majority of investors now hold their shares in street name, does disclosure about the number of record holders continue to be important to investors? Should we require registrants to disclose the amount of each class of equity securities held in street name? Should we require registrants to disclose the number of beneficial owners? If so, how should we define “beneficial owner” for purposes of Item 201(b)(1)? How would investors benefit from this additional information? What would be the challenges registrants might face in tracking the number of beneficial owners?
185. What types of investors or audiences are most likely to value the information required by Item 201(b)(1)?
Item 202(a)-(d) and (f) requires a brief description of the capital stock, debt, warrants, rights, American Depositary Receipts or any other securities that are being registered.
Item 202 derives from Schedule A of the Securities Act, which requires disclosure of the capitalization of the registrant, including a description of the classes of capital stock and funded debt and any securities covered by options.
While registrants are required to file as exhibits complete copies of their articles of incorporation and bylaws as currently in effect, registrants are not required to describe these documents or their registered securities in their periodic filings.
Changes in the terms and conditions of registered securities are disclosed in Form 8-K and Schedule 14A, which require discussion of modifications to the rights of any class of securities and amendments to the articles of incorporation or bylaws.
Item 12 of Schedule 14A requires disclosure if action is to be taken regarding the modification of any class of securities of the registrant, or the issuance or authorization for issuance of securities of the registrant in exchange for outstanding securities. Section (b) of Item 12 requires disclosure of any material differences between the outstanding securities and the modified or new securities in respect of any of the matters concerning which information would be required in the description of the securities in Item 202 of Regulation S-K. Item 19 of Schedule 14A requires disclosure of amendments to the charter, bylaws or other documents.
186. How do investors in the secondary market access information about the terms and conditions of a registrant's securities? Do investors rely only on the bylaws and articles of incorporation filed as exhibits to the registrant's Form 10-K?
187. In addition to the disclosure requirements in registration statements and certain proxy statements, should we require registrants to provide Item 202 disclosure each year in Form 10-K? Would requiring this information in the annual report facilitate investor access to important disclosure? Should we require registrants to disclose in their quarterly and annual reports whether changes have been made to the terms and conditions of their securities during the reporting period? Why? Are the Form 8-K requirements sufficient?
188. What types of investors or audiences are most likely to value the information required by Item 202?
189. What is the cost of providing the disclosure required by Item 202, including the administrative and compliance costs of preparing and disseminating this disclosure? How would these costs change if we made any of the changes contemplated here? Please provide quantified estimates where possible and include only those costs associated with providing disclosure under Item 202.
190. What are the benefits of providing the disclosure required by Item 202? How could the benefits change if we made any of the changes contemplated here? Please provide quantified or qualitative estimates where possible relating to disclosure under Item 202.
Item 701(a)-(e) requires disclosure of all sales of unregistered securities sold by the registrant within the past three years and specifies disclosure of: The date, title and amount of securities sold; the principal underwriters and other purchasers, if the securities were not publicly offered; the aggregate offering price for securities sold for cash and the nature of the transaction and the nature and aggregate amount of consideration received by the registrant; the exemption from registration claimed; and the terms of conversion or exercise.
Item 701's requirement to disclose recent sales of unregistered securities is based, in part, on Schedule A.
In 1996, the Commission adopted amendments to require timely disclosure of unregistered equity offerings and amended Forms 10-K and 10-Q to include Item 701(a)-(e).
In 2004, the Commission sought more timely disclosure of unregist ered equity offerings and added Item 3.02 to Form 8-K. Item 3.02 requires registrants to
Some of the disclosure required by Item 701(a)-(e) may overlap with disclosure in the statement of stockholders' equity, which is required in the annual financial statements,
191. Should we retain or eliminate Item 701(a)-(e)? Why? Does the disclosure required under Item 701(a)-(e) provide important information that is not available in either MD&A or the financial statements?
192. Does the Item 3.02 of Form 8-K disclosure requirement for issuances of one percent or greater and the Item 701 requirement for all issuances strike the right balance between disclosing larger issuances promptly and all others quarterly? Is one percent an appropriate threshold? If not, what would be an appropriate threshold and why?
193. Should we revise Forms 10-K and 10-Q to require disclosure of all unregistered sales of securities during the reporting period, including those already reported on Form 8-K? What would be the benefits to investors? Alternatively, should we require registrants to cross-reference or include a hyperlink to any previously filed Form 8-K containing Item 701 information for the reporting period or incorporate such forms by reference? What would be the advantages or disadvantages associated with either of these approaches?
194. Should we remove the Item 701 disclosure requirement from Forms 10-K and 10-Q? If so, should we revise Item 3.02 of Form 8-K to remove the one percent threshold and require registrants to disclose all unregistered sales of securities on Form 8-K? Alternatively, should we eliminate Item 3.02 of Form 8-K and instead require disclosure only in Forms 10-K and 10-Q?
195. Disclosure provided in response to Item 701(a)-(e) can range from a single paragraph to multiple pages. In Form 10-K, this disclosure is provided as part of Item 5 of Part II (Market for Registrant's Common Equity, Related Stockholder Matters and Issuer Purchases of Equity Securities) while in Form 10-Q this disclosure is provided as Item 2 of Part II (Unregistered Sales of Equity Securities and Use of Proceeds). Should we require this disclosure where it currently appears, in the context of the liquidity discussion in MD&A, or elsewhere?
196. Do registrants face any particular challenges in complying with the item's disclosure requirements?
Item 701(f) requires a registrant to disclose the use of proceeds from its first registered offering.
• The effective date of the Securities Act registration statement;
• the offering date or an explanation of why the offering has not commenced;
• if the offering terminated before any securities were sold, an explanation of the termination;
• if the offering did not terminate before any securities were sold, registrants must disclose (i) whether the offering has terminated and, if so, whether it terminated before the sale of all securities registered; (ii) the names of the managing underwriters, if any; (iii) the title of each class of securities registered; (iv) for each class of securities, the amount registered, the aggregate offering price of the amount registered, the amount sold, and the aggregate offering price of the amount sold to date; (v) the amount of expenses incurred by the registrant in connection with the issuance and distribution of the securities registered; (vi) net offering proceeds after deducting expenses; (vii) the amount of net offering proceeds used for certain enumerated purposes; and (viii) a brief description of any material change from the prospectus disclosure about the use of proceeds.
Item 701(f) requires registrants to provide disclosure in each subsequent
The precursor to Item 701(f) originated in Rule 463 of the Securities Act, which was adopted with related Form SR in 1971.
In 1980, the Commission proposed revisions to Rule 463 and Form SR to require, among other things, disclosure of use of proceeds beyond first-time registered offerings.
In 1997, the Commission eliminated Form SR and adopted Item 701(f) to require disclosure about the use of offering proceeds in periodic reports.
Other disclosure requirements may elicit information about the use of offering proceeds. For example, registrants may disclose the proceeds from initial public offerings as a material source of cash in the liquidity discussion within MD&A.
197. Should we retain or eliminate disclosure about the use of offering proceeds required by Item 701(f)? Why? If we retain this requirement, how could we improve it? For example, should we modify the item, such as by expanding it to offerings other than a registrant's first registered offering or by requiring other additional disclosure? Why?
198. In Form 10-K, this disclosure is provided as part of Item 5 of Part II (Market for Registrant's Common Equity, Related Stockholder Matters and Issuer Purchases of Equity Securities) while in Form 10-Q this disclosure is provided as Item 2 of Part II (Unregistered Sales of Equity Securities and Use of Proceeds). Should we require this information in its current location, in the context of liquidity or elsewhere? Should we require disclosure only if the actual use of proceeds differs materially from the description of the offering?
Item 703 requires tabular disclosure of purchases of registered equity securities by the registrant or any affiliated purchaser including:
• Total number of shares repurchased;
• average price paid per share;
• total number of shares purchased as part of publicly announced plans or programs; and
• maximum number (or approximate dollar value) of shares that may yet be purchased under the plans or programs.
Item 703 also requires footnote disclosure of (1) the date each plan or program was announced, (2) the dollar amount (or share amount) approved, (3) the expiration date (if any) of each plan or program, (4) each plan or program that has expired during the period covered by the table, and (5) each plan or program the registrant has determined to terminate prior to expiration, or under which the issuer does not intend to make further purchases.
Item 703 requires disclosure for each month included in the period covered by the report. Form 10-Q requires this information for any equity repurchase made in the quarter covered by the
Another commenter recommended enhanced disclosure of the “pros” and “cons” of share repurchase programs by addressing, among other things, (i) the time period specified for each program, (ii) the maximum number of shares authorized by the board to be repurchased, (iii) the cash (including any borrowings) spent on repurchases and dividends compared to that spent on reinvestment, and (iv) the impact of repurchase programs on corporate indebtedness.
In 2003, the Commission adopted Item 703 to increase the transparency of security repurchases by registrants and their affiliates and to inform investors of registrants' stated repurchasing intentions and subsequent repurchases.
In recent years, stock repurchases by registrants have increased significantly.
The staff has observed that registrants generally comply with the item requirements but often do not analyze the impact of stock repurchases in the context of MD&A. Even when the amount used to repurchase shares exceeds a registrant's net income or cash generated from operating activities for the reporting period, registrants do not always analyze these repurchases in MD&A.
While some of the disclosure required under Item 703 overlaps with requirements under U.S. GAAP,
While Item 703 requires disclosure of all monthly repurchases on a quarterly basis,
199. Is the information required under Item 703 about repurchases of a registrant's equity securities important to investors? If so, are there any revisions we could make to Item 703 to improve the disclosure provided to investors?
200. Should we require more granular information on repurchases of a registrant's equity securities? If so, what additional detail or more granular information should we require? For example, should we require disclosure about incurrence of indebtedness to fund repurchases or the impact repurchases had on performance measures, such as earnings per share or other items? If so, how should this information be formatted and presented?
201. Does Item 703 provide important information that is not also disclosed in a registrant's financial statements? Are there benefits to investors in providing this information in both the financial statements and in non-financial statement disclosure?
202. Item 703 requires disclosure of all repurchases of registered securities and does not have a de minimis requirement. Do investors find disclosure of all repurchases of securities during a registrant's fiscal quarter important to making a voting or investment decision? Should we adopt a general materiality standard or specify a monetary threshold for Item 703 disclosure in periodic reports?
203. Item 703 disclosure is required on a quarterly basis, while relevant U.S. GAAP disclosure is required on an annual basis. Should we require more frequent Item 703 disclosure? If so, what timeframe for reporting repurchases would be appropriate?
204. Should we require registrants to report repurchases on Form 8-K? For example, should we require Form 8-K disclosure only of repurchases that exceed a certain threshold, similar to Item 3.02 of Form 8-K, which requires registrants to disclose sales of equity securities that constitute more than one percent of the shares outstanding of the class of equity securities? If so, what should this threshold be and why?
The Industry Guides express the disclosure policies and practices of the Division and are intended to assist registrants and their counsel in preparing disclosure for their filings.
In proposing to re-designate the Industry Guides, the Commission noted that industry guidelines “maximize” the quality of disclosure in certain industries. Accordingly, though not specifically applicable to Exchange Act filings, Industry Guide 5 may be useful in determining the type of information that might be important in an Exchange Act filing for a real estate program.
We are seeking public input on whether the Industry Guides elicit disclosure that is important to investment and voting decisions. We are interested in commenters' views on
Between 1962 and 1992, the Commission published various Guides and Industry Guides to assist registrants in preparing and filing registration statements and periodic reports and to shorten the comment process.
In connection with the adoption of the integrated disclosure system in 1982, the Guides relating to specific industries were re-designated as Industry Guides and the titles of the Securities Act Industry Guides and Exchange Act Industry Guides were listed in Items 801 and 802 of Regulation S-K, respectively.
In 1996, the Task Force on Disclosure Simplification recommended incorporating the Industry Guides into Regulation S-K, based on the Task Force's understanding that registrants find the role of the Industry Guides within our disclosure regime confusing.
Although it did not incorporate the Industry Guides into Regulation S-K,
The S-K Study recommended reviewing the Industry Guides to evaluate whether they continue to elicit useful information that would not otherwise be disclosed. The S-K Study also recommended considering whether any Industry Guide provisions should
In proposing the re-designation of the Industry Guides, the Commission cited industry guidelines as an example of the limited instances where the use of guidelines is appropriate, stating that guidelines should pertain only to areas such as industry-specific information, where more specific guidance is appropriate yet flexibility is necessary to tailor disclosures to particular facts and circumstances.
We are seeking input on whether the Industry Guides continue to achieve the benefits cited by the Commission when it re-designated the guides in 1980. Today, the Division publicly releases its comment letters.
We also are seeking public input on the advantages and disadvantages of codifying industry-specific disclosure requirements in Regulation S-K. Codifying the Industry Guides in Regulation S-K would be consistent with the approach taken by the Commission in 2008 when former Industry Guide 2 was codified as Subpart 1200 of Regulation S-K.
Another possible approach is to update but not codify the Industry Guides in Regulation S-K. While this approach may allow registrants the flexibility to omit obsolete disclosures, the fact that the guidance is not a regulatory requirement may result in less uniformity in compliance and therefore less comparability across an industry.
205. Do the Industry Guides result in disclosure that is important to investors that registrants might not otherwise disclose under Regulation S-K or Regulation S-X? If so, what are examples of this type of disclosure?
206. Do registrants find the Industry Guides useful in preparing disclosure for periodic reports?
207. To the extent that the Industry Guides call for information that registrants would not otherwise disclose but for the Industry Guides, what are the challenges of providing this disclosure?
208. Should we include additional industry-specific disclosure requirements in Regulation S-K by codifying all or portions of the Industry Guides? What are the advantages and disadvantages of including industry-specific disclosure requirements in Regulation S-K versus retaining the Industry Guides?
209. Should some or all of the Industry Guides be updated? If so, which ones? Should additional Industry Guides or industry-specific rules for other industries be developed? If so, which industries would benefit from such guidance? Should industry-specific disclosure in Regulation S-K or staff guidance be limited to certain industries? If so, what criteria should be used to identify those industries?
210. What additional costs or costs savings, including the administrative and compliance costs of preparing and disseminating disclosure, do registrants experience because of the Industry Guides? Would registrants' disclosure costs be higher, lower or the same if the disclosures currently detailed in Industry Guides were incorporated into Regulation S-K or Regulation S-X? Please provide quantitative estimates if possible.
211. The Industry Guides originally were intended to assist registrants, their counsel and accountants in the preparation of disclosure by publishing staff policies and practices related to staff review of registrant filings.
212. Does the status of the Industry Guides as staff policy rather than Commission rules have any impact on the extent to which registrants provide disclosure consistent with the Industry Guides?
213. Regulations S-K and S-X include some industry specific disclosures. For example, Form S-11
214. Should industry-specific disclosure requirements apply to every registrant in a particular industry or should they be limited to certain categories of registrants? If they should be limited, to which registrants should they apply?
215. What types of investors or audiences are most likely to value the information that registrants would not disclose but for the Industry Guides?
In recent years, Congress has mandated new disclosure requirements that address specific public policy concerns. For example, Section 1502 of the Dodd-Frank Act mandated that the Commission adopt rules regarding registrants' use of “conflict minerals” originating in specified countries, and Section 1504 of the Dodd-Frank Act
Some investors and interest groups also have expressed a desire for greater disclosure of a variety of public policy and sustainability matters, stating that these matters are of increasing significance to voting and investment decisions.
We are interested in receiving feedback on the importance of sustainability and public policy matters to informed investment and voting decisions. In particular, we seek feedback on which, if any, sustainability and public policy disclosures are important to an understanding of a registrant's business and financial condition and whether there are other considerations that make these disclosures important to investment and voting decisions. We also seek feedback on the potential challenges and costs associated with compiling and disclosing this information.
One commenter opposed mandatory disclosure of sustainability risks,
We received several comment letters that specifically mentioned climate change disclosure.
A few commenters suggested that we adopt new line-item disclosure requirements for climate change matters.
In 1975, the Commission considered a variety of “environmental and social” disclosure matters, as well as its own authority and responsibilities to require disclosure under the federal securities laws.
In 1975, the Commission also concluded that it would require disclosure relating to social and environmental performance “only if such information . . . is important to the reasonable investor—material information.”
The current statutory framework for adopting disclosure requirements remains generally consistent with the framework that the Commission considered in 1975.
In seeking public input on sustainability and public policy disclosures, we recognize that some registrants historically have not considered this information material. Some observers continue to share this view and have expressed concern that sustainability or policy-driven disclosure requirements do not always result in disclosure that a reasonable investor would consider material.
216. Are there specific sustainability or public policy issues are important to informed voting and investment decisions? If so, what are they? If we were to adopt specific disclosure requirements involving sustainability or public policy issues, how could our rules elicit meaningful disclosure on such issues? How could we create a disclosure framework that would be flexible enough to address such issues as they evolve over time? Alternatively, what additional Commission or staff guidance, if any, would be necessary to elicit meaningful disclosure on such issues?
217. Would line-item requirements for disclosure about sustainability or public policy issues cause registrants to disclose information that is not material to investors? Would these disclosures obscure information that is important to an understanding of a registrant's business and financial condition? Why or why not?
218. Some registrants already provide information about ESG matters in sustainability or corporate social responsibility reports or on their Web sites.
219. In an effort to coordinate ESG disclosures, several organizations have published or are working on sustainability reporting frameworks.
220. Are there sustainability or public policy issues for which line-item disclosure requirements would be consistent with the Commission's rulemaking authority and our mission to protect investors, maintain fair, orderly and efficient markets and facilitate capital formation, as described in Section III.A.1 of this release? If so, how could we address the evolving nature of such issues and keep our disclosure requirements current?
221. What, if any, challenges would registrants face in preparing and providing this information? What would be the additional costs of complying with sustainability or public policy line-item disclosure requirements, including the administrative and compliance costs of preparing and disseminating disclosures, beyond the costs associated with current levels of disclosure? Please quantify costs and expected changes in costs where possible.
222. If we propose line-item disclosure requirements that require disclosure about sustainability or public policy issues, should we scale the disclosure requirements for SRCs or some other category of registrant? Similarly, should we exempt SRCs or some other category of issuer from any such requirements?
223. In 2010, the Commission published an interpretive release to assist registrants in applying existing disclosure requirements to climate change matters. As part of the Disclosure Effectiveness Initiative, we received a number of comment letters suggesting that current climate change-related disclosures are insufficient. Are existing disclosure requirements adequate to elicit the information that would permit investors to evaluate material climate change risk? Why or why not? If not, what additional disclosure requirements or guidance would be appropriate to elicit that information?
Exhibits to Commission filings provide detailed information about the registrant that generally is not available in the form itself. Item 601 of Regulation S-K specifies, by form type, the exhibits that registrants must file with Securities Act and Exchange Act forms. The exhibit requirements for Exchange Act forms overlap with many—but not all—of the exhibit requirements for Securities Act forms. Similarly, although there are some differences between the exhibit requirements for Forms 8-K, 10-Q and 10-K, many of the required exhibits are the same. Exhibits required in Exchange Act reports cover such categories as certain transactions,
The requirement to file exhibits originated in Schedule A of the Securities Act, which requires registrants to file copies of certain agreements, opinions and governing instruments.
To the extent that exhibits contain confidential and proprietary information, Commission rules permit registrants to omit this information from their public filings. For Exchange Act filings, registrants may obtain confidential treatment of information under Rule 24b-2. This rule requires registrants seeking confidential treatment to submit an application to the Commission objecting to disclosure of such information along with an analysis of the applicable exemption under FOIA.
We are seeking input on Item 601 of Regulation S-K to determine whether its requirements continue to provide investors with information important to making informed investment and voting decisions. Consistent with the scope of this release, we are considering only those exhibits required in quarterly and annual reports filed under the Exchange Act, which are identified in the following table.
224. Should we modify or eliminate any of the exhibit requirements in Item 601? If so, which ones and why? Should we add any new exhibit requirements to Item 601? If so, what requirements should we add and why?
225. Should we revise any of our exhibit requirements to change the presentation or format of the exhibits?
226. Should the Commission consider changes to improve the usefulness of the exhibits? For example, should the exhibits be provided in a tagged or searchable manner?
227. What types of investors or audiences are most likely to value the information that registrants disclose in the exhibits?
228. What is the cost of providing the disclosure required under Item 601, including administrative and compliance costs of preparing and disseminating this disclosure? How would these costs change if we made any of the changes contemplated here? Please provide quantified estimates if possible and include only those costs associated with Item 601.
In response to Item 601, registrants generally must file exhibits as complete documents, including any schedules or attachments. These schedules and attachments can be lengthy and sometimes contain proprietary information. The only exception to the requirement to file schedules and attachments applies to a plan of acquisition, reorganization, arrangement, liquidation or succession filed under Item 601(b)(2).
The Commission first permitted registrants to omit schedules and attachments for Item 601(b)(2) exhibits in 1980.
Material contracts filed under Item 601(b)(10) often include schedules that contain information that is not material to investors or that has been disclosed or sufficiently described elsewhere in the exhibit or in the disclosure. Examples of schedules and attachments providing information that may be immaterial include detailed product specifications attached to royalty agreements; implementation plans attached to service agreements; premises descriptions and plots as schedules to real estate leases; and licensing agreements with schedules listing immaterial patents. To the extent these schedules contain confidential and proprietary information, registrants may be permitted to omit such information from the public filing.
229. Should we continue to allow registrants to omit schedules and attachments for exhibits filed under Item 601(b)(2)? Why? If so, what qualitative or quantitative factors should be considered when determining if omission is appropriate?
230. Should we allow registrants to omit immaterial schedules and attachments from their filed exhibits? If so, should we expand this approach to all exhibits, or should we limit it to material contracts filed under Item 601(b)(10)? Should we provide examples or other guidance on how registrants could evaluate materiality for purposes of including schedules and attachments? If so, what type of guidance would be most useful for assessing the importance of the information (
231. If we allow the omission of immaterial schedules and attachments from all or certain filed exhibits, should we require registrants to include with such exhibits a list briefly identifying the contents of all omitted schedules, together with an agreement to provide a supplemental copy of any omitted schedule to the Commission upon request, similar to the requirement in Item 601(b)(2)?
232. Schedules and attachments to exhibits sometimes contain personally identifiable information (“PII”), and registrants may request confidential treatment of that information. Division staff generally does not object to the omission of PII from exhibits without a formal confidential treatment request, provided the registrant does not omit any other information from its exhibits. If we retain the requirement for registrants to file schedules and attachments to exhibits, should we codify current staff practice and permit registrants to omit PII without making a formal request under Rule 24b-2 of the Exchange Act? Should we limit such an accommodation to information contained in schedules and attachments to exhibits, or should we expand it to all exhibit filings?
Any amendment or modification to a previously filed exhibit to a Form 10-K or Form 10-Q must be filed as an exhibit to a Form 10-K or Form 10-Q.
For amendments to articles of incorporation or bylaws, Item 601 requires registrants to file a complete copy of the document as amended.
With adoption of the integrated disclosure system, the Commission consolidated several requirements in Forms 10-Q and 10-K for amendments and modifications to previously filed exhibits.
Registrants frequently amend agreements, such as credit facilities, licensing agreements, manufacturing agreements and supply agreements, to extend their duration. Registrants also amend credit facilities to increase the amount available for borrowing. Other than amended articles of incorporation or bylaws, multiple amendments to the same agreement may be dispersed among different periodic reports.
233. Should we continue to require registrants to file all amendments or modifications to previously filed exhibits as required under Item 601(a)(4)? Should we instead amend Item 601(a)(4) to exclude immaterial amendments? If so, should we provide guidance to registrants about how to determine whether an amendment is immaterial? Instead of materiality, should we permit registrants to exclude amendments based on a different standard? If so, what standard would be appropriate?
234. Does an amendment-only exhibit provide investors with the information they need to evaluate the impact of the amendment on the registrant? Should we instead require registrants to file a complete, amended and restated agreement each time an exhibit is modified, consistent with the requirement for amendments to articles of incorporation and bylaws? If so, should we require registrants to identify changes in the amended and restated contracts such as by underlining or highlighting the changes? Would complying with such a requirement be more burdensome for agreements than for articles of incorporation or bylaws? If so, why?
If an exhibit to a registration statement is filed in preliminary form, Instruction 1 to Item 601 provides that registrants are not required to file an amendment to the exhibit if it has been changed only (1) to insert certain information that appears elsewhere in an amendment to the registration statement or a prospectus filed pursuant to Securities Act Rule 424(b), or (2) to correct typographical errors, insert signatures or make other similar immaterial changes.
The Commission adopted the predecessor to Instruction 1 of Item 601 in 1954 in connection with new rules designed to simplify the registration procedure for offers involving competitive bidding.
While Instruction 1 is intended to address timing concerns in certain registered offerings, it also affects registrants' ability to incorporate exhibits by reference to other filings. To the extent a registrant modifies an incomplete exhibit that was filed in preliminary form, as permitted under Instruction 1, the incomplete exhibit already on file may not be incorporated by reference into its Exchange Act reports. Instead, the registrant would be required to file the complete exhibit with an Exchange Act report for the relevant reporting period.
235. Should we eliminate Instruction 1?
236. Should we expand the applicability of Instruction 1 to all filings? Should we expand the type of information in clauses (A) and (B) of Instruction 1 to cover additional types of information that, if changed, do not need to be refiled as an amendment to the exhibit?
237. Instruction 1 states that any incomplete exhibit may not be incorporated by reference in any subsequent filing.
Item 601(b)(10) of Regulation S-K requires registrants to file material contracts that fall into one of three broad categories:
• All contracts not made in the ordinary course of business that are material to the registrant (Item 601(b)(10)(i));
• Contracts made in the ordinary course of business of a type that are specified in the rule (Item 601(b)(10)(ii)); and
• Management contracts and compensatory plans in which any director, named executive officer, or other executive officer of the registrant participates (Item 601(b)(10)(iii)).
Any material contract that is executed or becomes effective during a reporting period must be filed as an exhibit to the Forms 10-Q or 10-K for the corresponding period.
Item 601(b)(10)(i) requires registrants to file every contract not made in the ordinary course of business that is material to the registrant and is to be performed in whole or in part at or after the filing of the report, or was entered into not more than two years before such filing.
In 1964, Congress expanded the information requirements for registration statements filed under Section 12 of the Exchange Act by adding a requirement to include material contracts not made in the ordinary course of business.
As amended, Section 12(b) required registrants to file material contracts, not made in the ordinary course of business, which are to be executed in whole or in part at or after the filing of the Exchange Act registration statement or which were made not more than two years before such filing. Schedule A includes a similar requirement for Securities Act registration statements. [15 U.S.C. 77aa(24)]. As noted at the time, the amendment to Section 12(b) followed the Commission's recommendation that registration under both the Exchange Act and the Securities Act be made as similar as possible.
The two-year requirement was intended as a “cutoff period” so registrants would not have to file all material contracts executed as early as 1932, even though they may have been fully performed years ago.
In 1977, with the adoption of Regulation S-K, the Commission expanded the exhibit requirements for contracts not made in the ordinary course of business to include those that were material to an understanding of the registrant's overall business or specifically referred to in the registrant's discussion of its reportable industry segments.
In 2004, the Commission adopted Items 1.01 and 1.02 of Form 8-K, which require disclosure when a registrant enters into, amends or terminates an agreement that is material to the registrant and is not made in the ordinary course of business.
238. Item 601(b)(10)(i) does not include any guidance for determining whether a contract not made in the ordinary course of business is material to a registrant. Should we consider revising the requirement to provide quantitative or other thresholds for determining when a contract is material to the registrant? If so, how should we define these thresholds? Would such a change facilitate registrants' compliance with this item requirement? Would such a change result in disclosure that is useful to investors?
239. Does “not made in the ordinary course of business” provide a clear standard for agreements covered by the rule? Should a different standard to apply? Should we revise Item 601(b)(10)(i) to define the types of contracts not made in the ordinary course of business that companies are required to file as exhibits? If so, how should we define such contracts?
240. Item 601(b)(10)(i) requires registrants to file material contracts that either (i) are to be performed in whole or in part at or after the filing of the periodic report, or (ii) were entered into not more than two years before such filing. This requirement was enacted in the context of requiring material contracts for newly reporting registrants that were entered into within the last two years but may have been fully performed before the period covered by the report. Do such contracts continue to be important to investors? Should we limit subparagraph (ii) to newly reporting registrants? For registrants that are already subject to reporting requirements, should we eliminate subparagraph (ii) and require registrants to file only material contracts that are to be performed in whole or in part at or after the filing of the report? Should we revise Item 601(b)(10)(i) to require all material agreements to be filed regardless of when they were entered into, as long as such agreements remain material to the registrant? Under what circumstances could a contract remain material to a registrant if it has been fully performed in a prior period?
Contracts made in the ordinary course of business conducted by a registrant and its subsidiaries generally do not need to be filed. Item 601(b)(10)(ii), however, establishes specific exceptions to the general rule and requires certain contracts to be filed even when they ordinarily accompany the kind of business conducted by the registrant and its subsidiaries. The following types of contracts must be filed, except where immaterial in amount or significance:
• Any contract to which directors, officers, voting trustees, security holders named in the registration statement or report, or underwriters are parties, other than contracts involving only the purchase or sale of current assets that have a determinable market price, at such market price;
• Any contract upon which the registrant's business is substantially dependent, such as continuing contracts to sell the major part of the registrant's products or services or to purchase the major part of the registrant's requirements of goods, services or raw materials or any franchise or license or other agreement to use a patent, formula, trade secret, process or trade name upon which the registrant's business depends to a material extent;
• Any contract calling for the acquisition or sale of any property, plant or equipment for a consideration exceeding fifteen percent of such fixed assets of the registrant on a consolidated basis;
• Any material lease under which a part of the property described in the filing is held by the registrant.
The Commission's 1965 amendments to Form 10-K included a requirement for registrants to file as exhibits certain specified contracts made in the ordinary course of business.
In 1980, the Commission codified in Regulation S-K the exhibit filing requirements, including the filing requirements for material contracts.
241. Should we expand Item 601(b)(10)(ii) to include other types of contracts that, although made in the ordinary course of business, should be filed?
242. Should we revise our overall approach to Item 601(b)(10)(ii) and if so, how? Rather than specifying categories of contracts, is there an alternative approach that would appropriately capture those ordinary course contracts that are important to investors? For example, should we replace the current requirements in Item 601(b)(10)(ii)(A)-(D) with a requirement for registrants to file all ordinary course contracts entered into (i) since the beginning of the last fiscal year, (ii) that exceed a percent of some measure, such as revenue or net income and (iii) where the registrant has a direct or indirect material interest? If we took this approach, how should we establish the relevant time frame and percentage threshold and what measures should we use? What would be the benefits and challenges of such an approach?
243. Do contracts that are required to be filed pursuant to Item 601(b)(10)(ii) contain information that is important to an understanding of the registrant or its business? Are the types of contracts identified in Item 601(b)(10)(ii) sufficiently significant that they should be filed, notwithstanding that they were made in the ordinary course of business?
244. Is “immaterial in amount or significance” a helpful standard by which to determine when a contract need not be filed? How do registrants currently apply this standard? Should we revise the item to provide guidance on the meaning of that phrase? Is it possible for contracts to be material in amount but not in significance? Should we revise the item to exclude only contracts that are immaterial in amount
245. Item 404(a) of Regulation S-K requires disclosure of any related party transaction since the beginning of the registrant's last fiscal year if the amount involved exceeds $120,000.
246. Taken together, Items 601(b)(10)(i) and (ii) require registrants to file material contracts not made in the ordinary course of business as well as certain contracts made in the ordinary course of business that are material to the registrant. Should we revise Item 601(b)(10)(ii) to require registrants simply to file all contracts that are material to an understanding of the registrant or its business, whether or not entered in the ordinary course of business? Are there any contracts currently required to be filed as exhibits under Item 601(b)(10)(ii) that would not be captured by such a principles-based approach? Conversely, would this approach require registrants to file material ordinary course contracts that they are not currently required to file? Would this change enhance the information available to investors? What would be the benefits and challenges of this approach?
To enhance consistency and clarity, we are considering whether to quantify “substantial dependence” as used in the item. Possible alternatives include establishing a dollar amount or percentage threshold, similar to the thresholds used in Item 601(b)(10)(ii)(C), as described below. While an objective requirement may provide clarity for registrants in their efforts to comply with the exhibit requirements, this approach could inadvertently exclude material contracts or result in a large number of contracts being filed that contain information that is neither material nor useful for investors.
As originally adopted in 1965, this requirement used a threshold of ten percent of all fixed assets of a registrant and its subsidiaries. In 1980, the Commission raised the threshold to fifteen percent,
In contrast to Item 601(b)(10)(ii)(C), Item 2.01 of 8-K requires a registrant to report the acquisition or disposition of a “significant amount of assets.”
When proposing amendments to Form 8-K in 2002, the Commission sought comment on whether to remove the ten percent test from Item 2.01 and replace it with the more general “materiality” test used in Item 1.01 of Form 8-K.
We are seeking public input on whether the fifteen percent threshold in Item 601(b)(10)(ii)(C) continues to provide investors with information that is important for an understanding of a registrant's business. We are interested in receiving input on whether a quantitative threshold is useful and, if so, whether fifteen percent of fixed assets is the appropriate measure. We also seek comment on the scope of contracts covered by subparagraph (C) and whether we should broaden the scope to better harmonize the exhibit filing requirements with the Form 8-K disclosure requirements. In addition, we are seeking public input on whether quantitative thresholds would be appropriate for other types of agreements required to be filed under Item 601(b)(10)(ii).
247. Should we adopt additional or different qualitative or quantitative thresholds for determining when contracts identified in Item 601(b)(10)(ii) must be filed as exhibits? If so, what should these qualitative or quantitative thresholds be? Why?
248. Should we revise Item 601(b)(10)(ii)(B) to provide qualitative or quantitative standards for what constitutes “substantial dependence”? Should we define the term “major part” in addition to or in lieu of defining “substantial dependence”? What factors should we consider in developing definitions or quantitative thresholds? What other alternatives should we consider to clarify which contracts must be filed under Item 601(b)(10)(ii)?
249. How could we design a quantitative threshold that would accommodate the diversity of registrants and business models? What would be the disadvantages of a quantitative threshold? If we used quantitative measures based on registrants' financial statements, what would be the appropriate measures to use? Alternatively, should we tie the threshold to a registrant's market capitalization?
250. Should we provide guidance on the phrase “depends to a material extent” in Item 601(b)(10)(ii)(B)? If so, should we adopt a similar approach to the one discussed in the preceding request for comment? Alternatively, should our requirements distinguish franchise or license agreements to use a patent, formula, trade secret, process or trade name from contracts to sell the major part of a registrant's products or services or to purchase the major part of a registrant's requirements of goods, services or raw materials?
251. Should we revise Item 601(b)(10)(ii)(C) to either increase or decrease the fifteen percent threshold for exhibits relating to acquisitions of property, plant or equipment? Should the threshold continue to be based on fixed assets? Alternatively, should we eliminate the threshold in favor of a principles-based requirement, such as “material” or “significant” acquisitions of property, plant or equipment?
252. Should Item 601(b)(10)(ii)(C) continue to focus on property, plant and equipment? Should we expand the scope to require registrants to file contracts for the acquisition or
Registrants will, at times, make a voluntary change in accounting principles or practices when two or more generally accepted accounting principles apply. For example, a registrant may choose to switch its inventory valuation from last-in, first-out to first-in, first-out. When such a change occurs, Item 601(b)(18) requires a registrant to file a letter from its independent accountant indicating whether, in the independent accountant's judgment, the change is preferable under the circumstances.
The precursor to Item 601(b)(18), adopted in 1971, required registrants to describe and state the reasons for any change in accounting principles or practices that would materially affect the financial statements filed or to be filed for the current year.
In 1975, the Commission amended Form 10-Q to require the accountant's letter to state whether the change, in the accountant's judgment, is preferable.
While Item 601(b)(18) requires an auditor to articulate the preferability of a change in accounting principle or policy, the nature of the auditors' statements varies.
In addition to the exhibit requirement of Item 601(b)(18), disclosure about a voluntary change in accounting principles is required under Rule 10-01(b)(6) of Regulation S-X and under U.S. GAAP. In certain instances, Public Company Accounting Oversight Board (“PCAOB”) Auditing Standards require auditors to address such changes in their opinions. While U.S. GAAP and PCAOB Auditing Standards require consideration of a registrant's change in accounting principle or practice, they differ from the Commission's requirements in terms of nature, timing and extent of reporting by the auditor. We are interested in commenters' views on whether existing disclosure requirements provide investors with sufficient information about a change in accounting principle without the need for registrants to file a preferability letter.
The auditor's opinion on the annual financial statements must discuss the nature of the change in accounting principle if the change has a material effect on the financial statements, but may not necessarily address preferability.
Unlike a preferability letter filed under Item 601(b)(18), the audit opinion will include an explicit statement as to preferability only when the registrant has not provided a reasonable justification that the alternative accounting principle is preferable.
We are seeking public input on whether to eliminate the exhibit requirement of Item 601(b)(18) in light of the significant overlap with the accounting requirements under U.S. GAAP and the PCAOB auditing standards. We are also interested in whether requirements in U.S. GAAP and PCAOB auditing standards are sufficient to alert investors to changes in a registrant's accounting policies or principles. We also seek input on the utility of Item 601(b)(18) given the small number of preferability letters filed and whether the small number of preferability letters reflects decreased utility and importance of this requirement or if, alternatively, these limited occurrences make this disclosure more valuable to investors.
253. Given the development of auditing and accounting standards over the past 40 years, including the adoption of more prescriptive standards such as SFAS No. 154
254. Should we revise Item 601(b)(18) to specify the language that must be included in a preferability letter? Is there any particular language that gives investors more insight into the determination that the change is preferable? In light of the lack of a standard for assessing preferability, do investors receive more information from a preferability letter than from an auditor's report? Does it depend on the nature of the change in accounting principle?
255. Should we eliminate Item 601(b)(18) in light of the current requirements under U.S. GAAP and the PCAOB's auditing standards? When a change in accounting principle is material, is an auditor's report without a qualified or adverse opinion sufficient to convey the independent accountant's conclusion that the registrant has justified the change to be preferable? Would eliminating the exhibit requirement affect the independent accountant's analysis of whether an accounting change is preferable?
256. Would it be more appropriate for the independent accountant to indicate in the auditor's report whether a change in accounting principle is to an alternative principle that in the auditor's judgment is preferable under the circumstances?
Item 601(b)(21) requires registrants to list all of their subsidiaries, the state or other jurisdiction of incorporation or organization of each, and the names under which such subsidiaries do business.
The term “significant subsidiary” is defined by reference to Rule 1-02(w) of Regulation S-X [17 CFR 210.1-02(w)]. Under that rule, a significant subsidiary means any subsidiary that meets any of the following conditions: (1) The registrant's and its other subsidiaries' investments in and advances to the subsidiary exceed ten percent of the total assets of the registrant and its subsidiaries consolidated as of the end of the most recently completed fiscal year (for a proposed combination between entities under common control, this condition is also met when the number of common shares exchanged or to be exchanged by the registrant exceeds ten percent of its total common shares outstanding at the date the combination is initiated); or (2) The registrant's and its other subsidiaries' proportionate share of the total assets (after intercompany eliminations) of the subsidiary exceeds ten percent of the total assets of the registrants and its subsidiaries consolidated as of the end of the most recently completed fiscal year; or (3) The registrant's and its other subsidiaries' equity in the income from continuing operations before income taxes, extraordinary items and cumulative effect of a change in accounting principle of the subsidiary exclusive of amounts attributable to any noncontrolling interests exceeds ten percent of such income of the registrant and its subsidiaries consolidated for the most recently completed fiscal year.
A legal entity identifier (“LEI”) is a 20-character, alpha-numeric code that connects to key reference information that allows for unique identification of entities engaged in financial transactions. Recently, the Commission has adopted rules requiring disclosure of LEIs in certain circumstances, if available, and in one instance the Commission has mandated use of
Another commenter recommended requiring registrants to disclose each country of operation and the name of each entity domiciled in each country of operation; the number of employees physically working in each country of operation; the total pre-tax gross revenue of each entity in each country of operation; and the total amount of payments made to governments by each entity in each country of operation.
We received two comment letters addressing LEIs.
Before the adoption of Regulation S-K, Form 10-K required registrants to disclose a list or diagram of all parents and subsidiaries of the registrant in the text of the annual report.
Item 1(a) of former 10-K required disclosure of subsidiaries of “material significance in relation to the total enterprise represented by the registrant and its subsidiaries, in respect of either (1) the investment in and advances to such subsidiary, or (2) the sales or operating revenues of such subsidiary, or (3) the essential nature of the function performed by such subsidiary in the total enterprise represented by the registrant and its subsidiaries.” The item also required certain disclosures of omitted subsidiaries such as the number of subsidiaries omitted and the total investment of the registrant in such omitted subsidiaries.
With the adoption of the integrated disclosure system, the Commission replaced the Form 10-K subsidiary disclosure requirement with a less-detailed requirement to file as an exhibit a list of subsidiaries and each subsidiary's jurisdiction of incorporation or organization.
Disclosure provided under Item 601(b)(21) has decreased in the last several years. Specifically, the average number of subsidiaries reported by
257. Should we revise Item 601(b)(21) to eliminate the exclusions and require registrants to disclose all subsidiaries? What would be the benefits and challenges associated with this alternative?
258. Should we expand the exhibit requirement to include additional disclosure about the registrant's subsidiaries? What additional information would be important to investors and why?
259. Should we require registrants to include an organization or corporate structure chart or similar graphic depicting their subsidiaries and their basis of control? How could such a graphic facilitate investors' understanding of a registrant's corporate structure? Should we require this chart or graphic as an exhibit or in the text of the annual report? What would be the challenges associated with this approach?
260. For purposes of identifying which subsidiaries a registrant may omit from the exhibit, Item 601(b)(21) relies on the definition of “significant subsidiary” in Rule 1-02(w) of Regulation S-X. Does this definition appropriately exclude subsidiaries that are not important to investors? Does it exclude any subsidiaries that should be included? Should we consider a different definition or test for excluding certain subsidiaries from the exhibit? If so, what factors should we consider?
While there are currently many ways to identify entities, there is no unified global identification system for legal entities across markets and jurisdictions. The LEI is a reference code to uniquely identify a legally distinct entity that engages in a financial transaction.
Obtaining an LEI entails both initial registration and annual maintenance fees and is done through local operating utilities such as the Global Market Entity Identifier utility in the United States.
In recent rulemakings, the Commission has prescribed disclosure of LEI, if available, for parties to certain financial transactions. For example, the Commission recently prescribed disclosure of an obligor's LEI, if available, with respect to a rating action involving a credit rating of an obligor as an entity.
261. Should we require registrants to disclose their LEI and the LEIs of their subsidiaries (if available) in the list of subsidiaries filed under Item 601(b)(21)? How would this information benefit investors? Should the industry in which the company operates or the extent to which the company engages in financial market transactions affect whether disclosure of LEIs is required? What would be the costs of requiring disclosure of this information?
262. Should our rules encourage registrants to obtain an LEI? If so, how could we structure our rules, consistent with our authority under the Securities Act and the Exchange Act, to achieve this purpose? For example, should we make obtaining and maintaining an LEI a condition to any of our existing disclosure accommodations or alternatives? Why or why not? If so, should such a condition be limited to certain types of registrants, such as those operating in financial services? For registrants that have not obtained an LEI, will these registrants seek to obtain an LEI in the future absent any regulatory incentive to do so? In addition to the fees for obtaining and maintaining an LEI, would there be other costs associated with obtaining LEIs?
263. Some registrants may have hundreds or thousands of subsidiaries or affiliates operating globally while other registrants have simple corporate structures. If we required registrants to disclose LEIs (if available) in the list of significant subsidiaries, should we limit the requirement to larger registrants or larger subsidiaries, independent of the industry in which the registrant operates? For example, should we limit the requirement to large accelerated filers or well-known seasoned issuers (WKSIs)?
Over the years, the Commission has developed a disclosure system that provides regulatory relief in the form of reduced disclosure requirements for certain smaller registrants. Although initially developed to facilitate smaller companies' access to the capital markets,
In 2012, Title I of the JOBS Act created a new category of issuer called an “emerging growth company.” Like SRCs, EGCs are eligible for a variety of accommodations, including scaled disclosure requirements.
• The last day of its fiscal year during which its total annual gross revenues are $1 billion or more;
• the date it is deemed to be a large accelerated filer under the Commission's rules;
• the date on which it has issued more than $1 billion in non-convertible debt in the previous three years; or
• the last day of the fiscal year following the fifth anniversary of the first registered sale of common equity securities of the issuer.
The Commission has specified other categories of registrants for different purposes. These include: Accelerated filers, with a public float of $75 million or more but less than $700 million; and large accelerated filers, with a public float of $700 million or more.
These categories determine periodic reporting schedules.
The following table summarizes the criteria for determining whether a company qualifies as an EGC, SRC, non-accelerated filer, accelerated filer or large accelerated filer.
The Commission's practice of providing disclosure accommodations to smaller companies with less established trading markets dates back to 1979. In providing these accommodations and determining what categories of registrants are eligible for scaled disclosure requirements, the Commission has sought to promote capital formation and reduce compliance costs while maintaining investor protections.
Our current system of reporting and registration for SRCs is based on Form S-18, which allowed an entity that was not previously a reporting company to raise a limited amount of capital without immediately incurring the full range of disclosure and reporting obligations required of other issuers.
Notably, while Form S-18 was intended to facilitate a small business's access to public capital markets, eligibility to use the form was not determined by the size of the issuer. After observing the form's use, the Commission later expanded the availability of Form S-18.
In 2007, the Commission replaced the “small business issuer” definition with the current definition for “smaller reporting companies,” which expanded the universe of registrants eligible for scaled disclosure.
Recently, we have received recommendations to revisit some of our registrant categories eligible for scaled disclosure, with particular focus on expanding the SRC definition to include a greater number of registrants.
Similarly, the Commission's Advisory Committee on Small and Emerging Companies (“ACSEC”) recommended the Commission revise the SRC definition to include companies with a public float of up to $250 million to extend regulatory relief to a broader range of smaller public companies, including, among other things, the exemption from the requirement to provide an auditor attestation of the registrant's ICFR. Item 308(b) of Regulation S-K [17 CFR 229.308(b)]. Item 308(b) applies to accelerated filers and large accelerated filers, both of which definitions exclude issuers that that are eligible to use the SRC requirements in Regulation S-K. Exchange Act Rule 12b-2 [17 CFR 240.12b-2]. Because the definitions of accelerated filer and larger accelerated filer specify that they do not include registrants that are eligible to use the requirements for SRCs for their annual and quarterly reports, a change to the threshold for SRCs would extend this exemption even without a corresponding change to the threshold for accelerated filers.
The ACSEC also has recommended the Commission revise the definition of “accelerated filer” to include companies with a public float of $250 million or more, but less than $700 million, thereby exempting companies with public float between $75 million and $250 million from the requirement to provide an auditor attestation of the registrant's ICFR.
We are interested in receiving input on how we should approach the eligibility criteria for using scaled disclosure. The FAST Act requires the Commission to revise Regulation S-K to further scale or eliminate disclosure requirements to reduce the burden on a variety of smaller issuers, including SRCs.
264. In the context of registered offerings, the Commission has determined that certain types of issuers are unsuited for short-form registration or disclosure-related relief.
265. Should we tie eligibility for scaled disclosure to a certain proportion of companies, such as companies in the lowest one percent of total U.S. market capitalization or the lowest six percent of total U.S. market capitalization, as previously recommended by the ACSPC?
266. Should we allow one or more categories of larger companies, such as companies with a longer reporting history or more readily available public information to benefit from scaled disclosure requirements as a means of reducing compliance costs?
267. The benefits of disclosure may be greater for smaller registrants because information asymmetries between investors and managers of smaller companies are typically higher than for larger, more seasoned companies with a large following.
Registrants that qualify as an SRC or EGC are allowed to provide less detailed disclosure about their business operations and financial condition and to limit the number of periods for which disclosure is required.
SRCs also are required to provide only two years of audited financial statements
Not all EGCs qualify as SRCs. EGCs are only required to provide two years of audited financial statements in an initial public offering of common equity securities and may limit their MD&A to only those audited periods presented in the financial statements.
Section 71003 of the FAST Act amended Section 102 of the JOBS Act to allow an EGC that is filing a registration statement (or submitting a draft registration statement for confidential review) under Section 6 of the Securities Act on Form S-1 or Form F-1 to omit financial information for historical periods otherwise required by Regulation S-X if it reasonably believes the omitted information will not be required in the filing at the time of the contemplated offering, so long as the issuer amends the registration statement prior to distributing a preliminary prospectus to include all financial information required by Regulation S-X at the time of the amendment. This provision took effect 30 days after the date of enactment of the FAST Act. Section 71003 also directs the Commission to revise the general instructions to Form S-1 and Form F-1 to reflect this self-executing change. In addition, Section 84001 of the FAST Act requires the Commission to revise Form S-1 to permit an SRC to incorporate by reference into its registration statement any documents filed by the issuer subsequent to the effective date of the registration statement. Public Law 114-94, Sec. 71003, 129 Stat. 1312 (2015).
We recently adopted interim final rules to implement Sections 71003 and 84001 of the FAST Act.
SRCs are not required to provide certain line-item requirements in Regulation S-K, including Item 201(e) (Market price of and dividends on the registrant's common equity and related stockholder matters—Performance Graph),
The following table summarizes the scaled disclosure accommodations available to EGCs and SRCs for periodic reports as well as certain other filings.
a. Comments Received
Two commenters suggested that EGCs should be exempt from Item 305 disclosure.
In simplifying disclosure requirements for small businesses, we seek to facilitate capital formation without compromising investor protection. Previous Commission efforts in this area have focused on reducing requirements that impede the formation and growth of small businesses and,
The disclosure items formerly required by Form S-18 generally were consistent with the corresponding items in Form S-1. However, Form S-18 required less extensive narrative disclosure and simplified financial statements, consistent with Regulation A. Based on input from public hearings and written comments, the Commission sought to require in Form S-18 only the information that normally would be applicable to those small businesses expected to use the form. Accordingly, the Commission reduced or eliminated requirements that it determined were particularly burdensome to small businesses and tended to elicit information that, in the small business context, was less relevant or less beneficial to investors.
For example, Form S-18 did not use the description of business requirement from Regulation S-K. Instead, Form S-18 provided smaller issuers the flexibility to discuss other business-related disclosure, such as their dependence on a limited number of customers or suppliers (including suppliers of raw materials or financing) and cyclicality of their industry, only if it would have “a material impact upon the registrant's future financial performance.”
Under Regulation S-B, the narrative disclosure requirements generally paralleled those in Regulation S-K at the time, except that Regulation S-B incorporated the simplified requirements of Form S-18. The financial information required by Regulation S-B was substantially similar to that required by Form S-18, except that Regulation S-B also addressed interim financial statement requirements.
In 2007, the Commission eliminated the separate Regulation S-B disclosure requirements and instead provided scaled disclosure requirements in Regulation S-K and Regulation S-X.
In response to comment letters and the recommendation of the ACSPC, the Commission revised the requirements in Regulation S-X to require two years of comparative audited balance sheet data for SRCs, rather than the one year previously required by Regulation S-B.
Unlike Regulation S-B, which required small business issuers to comply with the entire Regulation S-B disclosure regime, the amendments to Regulation S-K adopted in 2007 permitted SRCs to comply selectively with the scaled disclosure requirements on an item-by-item basis.
In recent years, the Small Business Forum has recommended that the Commission:
• Eliminate or significantly reduce the extent of XBRL tagging requirements for SRCs; and
• permit SRCs to exclude line item-responsive disclosures from their periodic reports if such disclosures are not material.
Similarly, in the last few years, the ACSEC has recommended that the Commission:
• exempt SRCs from XBRL tagging requirements;
• exempt SRCs from filing immaterial attachments to material contracts;
• when adopting new disclosure rules, consider whether such rules place a disproportionate burden on SRCs in terms of the cost of, and time spent on, compliance with such requirements, and if so, provide for exemptions from or phase-in periods for such new rules for SRCs.
In 2015, the FAST Act directed the Commission to revise Regulation S-K to further scale or eliminate requirements in order to reduce the burden on EGCs, accelerated filers, SRCs, and other smaller issuers, while still providing all material information to investors.
268. Are there any disclosure requirements for which scaling is not appropriate?
269. How should we assess whether scaled disclosures are effective at
270. Are there disclosure requirements that are particularly beneficial for investors in smaller registrants? For example, are there disclosure requirements that elicit information that is not as readily available outside of smaller registrants' filings although this information might be readily available outside of a filing for larger or more seasoned companies? If so, which requirements and why? Does the information elicited from smaller registrants by these disclosure requirements appropriately consider the costs of these requirements to these smaller registrants?
271. Are there additional item requirements that we should consider scaling for SRCs? Are there any current scaled disclosure requirements that we should scale further or eliminate entirely?
272. Should we allow EGCs to take advantage of the scaled disclosure requirements currently available only to SRCs, such as the less extensive requirements for the description of business set forth in Item 101(h) of Regulation S-K or the elimination of the contractual obligations table available under Item 303(d) of Regulation S-K?
273. Should we reorganize Regulation S-K, as recommended by one commenter,
274. Should we eliminate or reduce the XBRL tagging requirements for SRCs? What, if any, XBRL tagging should we require of SRCs?
275. Should we permit SRCs to exclude disclosure that would be responsive to specific items in Regulation S-K from their periodic reports if such disclosures are not material? Should we permit SRCs to omit all such disclosure or should we limit this accommodation to specific items in Regulation S-K?
276. What types of investors or audiences would be affected by further scaling? How?
277. Do our scaled disclosure requirements appropriately consider the costs and benefits of these requirements to smaller registrants and investors in these registrants? What savings (or costs avoided) for registrants, including the administrative and compliance costs of preparing and disseminating disclosure, would likely arise from scaling additional item requirements? Please provide quantifications of savings and costs avoided where possible.
The federal securities laws have required registrants to provide annual reports since 1934.
The Commission has required quarterly reporting since 1970, when it adopted Form 10-Q to replace the semi-annual report on Form 9-K.
The New York Stock Exchange began requiring annual reports in 1914, and by 1923, over twenty-five percent of NYSE-listed companies were publishing quarterly reports with another eight percent publishing semi-annual reports. By 1933, over sixty percent of NYSE-listed companies were publishing quarterly reports and twelve percent published semi-annual reports.
The Form 10-Q proposing release also noted that “[m]any publicly held companies are releasing condensed quarterly financial information, and the major stock exchange[s] require publication of such information by listed companies.” Form 10-Q For Disclosure of Financial Information, Release No. 34-8683 (Sept. 1969) [34 FR 14239 (Sept. 10, 1969)].
In 1981, in connection with its integrated disclosure initiatives, the Commission revised Form 10-Q to “build upon the annual reporting system to ensure meaningful disclosure on a continuous basis by making quarterly reporting a mechanism to update the annual report.”
The Commission adopted quarterly reporting with the purpose of ensuring meaningful disclosure to investors on a continuous basis.
The value of quarterly financial reporting has been the subject of debate.
For a list of recent publications on short-termism,
On the other hand, some advocates of frequent reporting, typically on a quarterly basis, point out that greater frequency improves the timeliness of earnings and reduces information asymmetry between managers and investors.
The value of quarterly reporting may vary by industry or by the size of the registrant. For example, investors in smaller, capital-intensive technology companies may focus more on significant business or technology developments than on quarterly financial reports.
278. Do investors, registrants and the markets benefit from quarterly reporting? What are the benefits and costs to investors, registrants and the markets from the current system of quarterly reporting? Should we revise or eliminate our rules requiring quarterly reporting? Why or why not?
279. Should the reporting requirements be different for different types of registrants? Should we consider permitting SRCs to file periodic reports on a less frequent basis, such as semi-annually? If so, what disclosures should we require in those reports?
280. Should we allow other categories of registrants to file periodic reports on a less frequent basis, such as semi-annually? If so, which categories of registrants should be permitted to file less frequently, and what disclosure should be required?
281. Should we require certain registrants to file periodic reports on a more frequent basis such as monthly?
282. Should we consider reducing the level of disclosure required in the quarterly reports for the first and third quarters? If so, what disclosure should we require in these abbreviated quarterly reports? Should the disclosure requirements for SRCs be the same as those that apply to other categories of registrants?
283. Do quarterly reporting obligations influence the strategic goals and timelines of registrants' management? Do quarterly reporting
284. What types of investors or audiences are most likely to value the information that registrants disclose in quarterly reports?
285. What are the savings (or costs avoided) for registrants, including the administrative and compliance costs of preparing and disseminating disclosure, that would likely arise from revising or eliminating our rules requiring quarterly reporting? Please provide quantifications of savings and costs avoided where possible.
Given the volume, complexity and sophistication of corporate disclosures, the presentation and delivery of information may play a significant role in investors' ability to access and use important disclosure. The Commission's own disclosure system creates some fragmentation of information, in both location and time. Registrants provide disclosure on Forms 10-K, 10-Q, and 8-K, which are filed on EDGAR. Registrants also can provide broad, non-exclusionary distribution of information under Regulation FD either on Form 8-K or through press releases, conference calls, or Web sites.
The S-K Study recommended that the staff consider ways to present information that would improve the readability and navigability of disclosure. It also recommended that the staff explore methods to discourage repetition and disclosure of immaterial information.
In light of the S-K Study's recommendations and the recent FAST Act mandate, we are seeking public input on how our rules can facilitate the readability and navigability of disclosure documents. We are seeking public input on the use of tools such as cross-referencing, incorporation by reference, hyperlinks and registrant Web sites as well as other ways we could change our disclosure requirements to improve the readability and navigability of registrant filings.
In lieu of presenting duplicative disclosure, our rules generally permit registrants to cross-reference to information in one section of a document to satisfy a disclosure requirement in another section of the document. Several items in Regulation S-K specify that a company may include in its financial statements or related notes a cross-reference to certain information in the non-financial statement disclosure or, conversely, a company may cross-reference from the disclosure to the financial statements or notes thereto.
Some commenters suggested that the Commission require or encourage the use of cross-references within filings.
We recognize that an investor may find it easier to access all relevant information in a single location, even if a portion of the information is repeated elsewhere in the document. However, repetitive disclosure may obscure relevant information or render it difficult to evaluate the importance of the information. Below, we consider ways in which cross-references could potentially be used to reduce redundant disclosure and improve the navigability of lengthy documents.
Where different disclosure requirements call for the same information in separate parts of the same document, as discussed above, our rules generally allow the registrant to cross-reference to the applicable discussion in another part of the document rather than duplicating the disclosure.
In the Securities Act context, Commission staff has discouraged registrants from repeating disclosure in multiple places in a prospectus, instead encouraging the inclusion of a brief overview to provide context in one section along with a cross-reference to more detailed discussion elsewhere.
In seeking input on how registrants can most effectively present and deliver important information, we recognize that information may be relevant to more than one filing or more than one section of a given filing. Registrants often repeat information in response to different item requirements in Form 10-K. For example, disclosure about the registrant's business appears in the Business section, and parts of that disclosure may be repeated in MD&A, risk factors, and the footnotes to the financial statements. Repetition of this information may be beneficial in certain contexts, such as a registrant with a complex organizational structure or business model. Repetition also may provide users of disclosure with direct access to the information they need in a consistent location, particularly to the extent that different audiences for disclosure focus on different filings or sections of filings. In other instances, such repetition can be distracting.
286. Do investors find that cross-referencing within a filing in lieu of repeating the disclosure helps them locate important information? Why or why not?
287. Are there specific items in Regulation S-K that would benefit from greater use of cross-referencing to reduce duplicative disclosure? If so, which items? For these specific items, should we amend the item to specifically encourage use of cross-references? Alternatively, and as suggested by a commenter,
288. Does cross-referencing negatively affect investors' ability to use disclosure by creating inconsistency in the location of information across different registrants and different filings? To what extent does cross-referencing introduce challenges with respect to comparative analyses or large-scale automated processing of disclosure?
289. Should we require registrants to provide certain disclosures in the same location (
290. To what extent does the flexibility to use cross-references reduce compliance and administrative costs to registrants of preparing and disseminating disclosures? Please provide quantifications if possible.
Cross-references can also assist readers in navigating disclosure where disclosures are not necessarily duplicative but relate to the same topic and may be required in multiple locations throughout a filing.
291. Are there certain items or topics that would benefit from a cross-reference to related or more comprehensive disclosure in different parts of the filing? If so, what are those items or topics?
292. Do cross-references that identify related information make the disclosure more or less readable?
Registrants' ability to use cross-references is not unlimited, as the
While none of our rules prohibit the use of cross-references, there may be instances where cross-references would not satisfy the requirements or would detract from the readability or completeness of the disclosure. For example, the Commission has stated that its MD&A rules are intended to provide, in one section of a filing, a discussion of all the material impacts on the registrant's financial condition or results of operations, including those arising from circumstances discussed elsewhere in the filing.
Cross-referencing is contemplated under auditing standards.
In addition, the financial statements are not covered by the PSLRA safe harbor from liability for forward-looking statements. The PSLRA does, however, cover MD&A disclosures.
293. Are there items or topics where cross-references detract from the readability of a filing? Are there items or topics where we should prohibit cross-references and require all related information be presented in a single location? What are these items or topics?
294. Some of the Commission's guidance limiting the use of cross-referencing pre-date the expanded use of technology that allows registrants to hyperlink to referenced disclosure.
295. Should we introduce requirements or guidance for the use of cross-references in order to increase the consistency in location of information across periods and registrants? If so, what requirements or guidance should we consider?
Rule 12b-23 of the Exchange Act generally allows a registrant to incorporate by reference information in any part of a registration statement or report in answer, or partial answer, to any other item of a registration statement or report.
Part I: Business, Risk Factors, Unresolved Staff Comments, Properties, Legal Proceedings, and Mine Safety Disclosures.
Part II: Market for Registrant's Common Equity, Related Stockholder Matters and Issuer Purchases of Equity Securities, Selected Financial Data, MD&A, Quantitative and Qualitative Disclosures about Market Risk, Financial Statements and Supplementary Data, Changes in and Disagreements with Accountants on Accounting and Financial Disclosure, Controls and Procedures, and Other Information.
To incorporate Part III information into the Form 10-K, the proxy statement or information statement must be filed not later than 120 days after the end of the fiscal year covered by the Form 10-K
Rule 12b-23 provides that where material is incorporated by reference:
• The material must be clearly identified by page, paragraph, and caption or otherwise;
• the filing must state that the specified matter is incorporated by
• except in certain circumstances, a copy of any information incorporated by reference or the pertinent pages of the document containing such information must be filed as an exhibit to the report where it is incorporated by reference.
For exhibits, Rule 12b-32 allows any document or part thereof filed with the Commission to be incorporated by reference as an exhibit to any report filed with the Commission by the registrant or any other person.
The Commission has a long history of permitting incorporation by reference.
Certain Commission forms allow historical incorporation by reference, meaning a registrant or issuer may incorporate information by reference to previous filings. Examples include Exchange Act Form 8-A, which allows for incorporation by reference of the description of a registrant's securities if a comparable description is contained in a prior filing.
Certain Securities Act forms allow for forward incorporation by reference by certain issuers, where an issuer is permitted to forward incorporate by reference to Exchange Act reports filed in the future. Examples include Form S-3 and Form S-4.
Given the scope of this release and its focus on Exchange Act periodic reports, the discussion here generally is limited to historical incorporation by reference.
The Commission initially limited eligibility to incorporate by reference in registration statements to seasoned, exchange-traded companies based on the likelihood that the information in the incorporated filings has been thoroughly analyzed and reflected in the price or rating of the securities offered. For these types of registrants, the Commission concluded that the cost savings to registrants of not having to repeat or refile information disclosed elsewhere outweighed the risk to investors that the stock price does not reflect the omitted information.
The integrated disclosure system also gave rise to the current structure of Form 10-K that allows registrants to incorporate Parts I and II from the annual report to shareholders and Part III from the definitive proxy statement.
Advancements in technology support greater use of incorporation by reference. In Securities Offering Reform, the Commission expanded the use of incorporation by reference conditioned on the registrant making its incorporated Exchange Act reports and other materials readily accessible on a Web site maintained by or for the
296. To what extent does including previously disclosed information along with recent developments in a single self-contained filing facilitate an investor's understanding of a registrant's disclosure? Does repeating information that previously has been disclosed hinder an investor's ability to identify information that has changed since the registrant's last report? Does providing previously disclosed information along with information that is new or has changed better enable investors to consider the changes in context? If so, should we structure our requirements to elicit disclosure that highlights changes from a registrant's last report and provides a comprehensive discussion in a single location?
297. Should we expand or limit registrants' ability to incorporate by reference? Why or why not? Does incorporation by reference make the disclosure more or less readable?
298. Are there particular filings or sections of filings that should remain direct sources of disclosure information, rather than permitting incorporation by reference? If so, what information should be located consistently and in which filings? Which sections of those filings should contain the information? For example, is it more important for an investor to have information included directly and in full in a Securities Act registration statement than it is in an Exchange Act filing?
299. Should our requirements to provide historical and recent information within a single self-contained filing differ for registrants of different sizes, development stages, reporting histories or other factors?
300. Should registrants be permitted to incorporate by reference historical information from prior filings in lieu of presenting prior years' information in the Form 10-K? If so, when or how frequently should we require registrants to present or refresh their complete core disclosure? Should we limit this approach to certain categories of registrants and, if so, how should we determine which categories would be eligible?
301. Should we expand or limit registrants' ability to incorporate by reference to exhibits? Why or why not? Does incorporation by reference make it more difficult to locate exhibits?
302. To what extent does the flexibility to use incorporation by reference reduce compliance and administrative costs to registrants of preparing and disseminating disclosures? Please provide quantifications if possible.
Under Rule 105 of Regulation S-T, a registrant may include hyperlinks within a filing, such as a table of contents that hyperlinks to specific sections in a filing or a cross-reference that hyperlinks to another part of a filing.
Of the two formats that are generally accepted by the EDGAR system, the text-based American Standard Code for Information Interchange (“ASCII”) and hypertext markup language (“HTML”),
If a registrant includes a hyperlink in its filing, whether or not the link is permitted by Commission rules, the information in the linked material is not considered part of the filing for determining compliance with disclosure obligations. However, inclusion of the link will cause the registrant to be subject to the civil liability and antifraud provisions of the federal securities laws for the information contained in the linked material.
In 2000, the Commission stated that it is appropriate for registrants to assume liability for hyperlinked material as if it were part of the filing, because the use of hyperlinks in filings is voluntary and filers need not hyperlink to material that they do not wish to be understood as having adopted as their own. The Commission cautioned registrants not to use hyperlinks if they are not prepared to accept responsibility for the hyperlinked material.
The EDGAR system initially permitted hyperlinks only to different sections within a single document. In 2000, when the Commission expanded the permissibility of hyperlinks to allow hyperlinks to other documents and exhibits filed on EDGAR, the Commission stated that hyperlinks
The Commission's rationale for limiting the use of hyperlinks was that readers might be unable to understand the content of the filing without accessing numerous hyperlinks and that readers would be unable to print the filing as an integrated whole.
Since this 2008 guidance, there has been a significant increase in the use of the Internet as a tool for disseminating information. As of 2014, eighty-seven percent of the U.S. population uses the Internet, up from seventy-four percent in 2008.
303. Should we consider revising our rules to permit registrants to include external hyperlinks in their filings? Should we consider permitting registrants to include external hyperlinks in their filings to satisfy disclosure obligations? Why or why not? What would be the benefits and challenges of such a requirement?
304. Would increased use of hyperlinks and further disaggregation of company disclosure into multiple filings hinder the quality or readability of disclosure? If so, how? What information, if any, should we require in a single filing or location?
305. Should we require registrants to include hyperlinks with any cross-reference to specific information or a specific section within a filing? Why or why not? What would be the benefits and challenges of such a requirement? In particular, what would be the costs or savings in compliance and administrative costs to registrants of required hyperlinks?
306. As suggested by one commenter,
In certain circumstances, our rules and forms either permit or require the use of company Web sites as a means to provide information to investors. Depending on the circumstances, company Web sites may serve as a supplement to material filed or furnished via EDGAR, as an alternative to such materials, or as a stand-alone method of providing information to investors independent of EDGAR.
When a company Web site supplements Commission filings, company information is available both on EDGAR and on the company's Web site. We have encouraged or required supplemental use of Web sites to make information more broadly accessible. For example, registrants are required to:
• Disclose their Web site addresses, if available, in annual reports on Form 10-K and state whether their Exchange Act reports are available on their Web sites;
• make their Exchange Act reports and documents incorporated by reference available on their Web site as a condition to incorporation by reference of previously filed reports into prospectuses filed as part of registration statements on Form S-1 or Form S-11;
• make their Exchange Act reports and other materials incorporated by reference available on their Web site as a condition for SRCs to forward incorporate by reference into a FormS-1;
• provide their financial statements to the Commission and post them on their corporate Web site, if any, in interactive data format using XBRL;
• post on their Web sites, if they maintain one, notice of their intent to delist or deregister their securities as a condition to withdrawing from registration under Section 12(b) of the Exchange Act;
• post on their Web sites, if they maintain one, beneficial ownership reports filed by officers, directors and principal security holders under Section 16(a) of the Exchange Act.
In some situations, registrants may satisfy a disclosure requirement either by filing the disclosure on EDGAR or by making it available on the registrant's Web site, thereby using company Web sites as an alternative to EDGAR.
In addition, Item 406(c) of Regulation S-K, which requires disclosure of a registrant's code of ethics, requires the registrant to: File a copy of its code of ethics as an exhibit to its annual report; post the text of its code of ethics on its Web site and disclose in its annual report its Web site address and the fact that it has posted its code of ethics on its Web site; or undertake in its annual report to provide any person a copy of its code of ethics upon request.
Only in very limited circumstances do our rules allow a company's Web site to serve as a standalone method of providing information to investors wholly independent of EDGAR. Rules 12h-6 and 12g3-2(b) permit certain formerly reporting foreign private issuers to use their Web sites to provide information about the company in lieu of Exchange Act registration and reporting requirements. Unlike the examples above, where registrants' alternative to posting the information on their Web sites is to include it in a Commission filing, these companies are required to include the relevant disclosure on their Web sites. Otherwise, these companies would lose their exemption from registration under Section 12(g) of the Exchange Act.
Another commenter acknowledged the potential efficiency to be gained through use of the Internet and electronic delivery, but suggested that, to protect the interests of investors who rely on paper delivery, the Commission should take steps to protect the interests or access of investors who depend on non-electronic access to information.
As noted by several commenters, today's technology provides virtually instant access to information through a variety of sources outside of EDGAR, including company Web sites.
Currently, investors typically can access registrants' public filings since 1996 through EDGAR.
For historical information available on company Web sites, the Commission has stated generally that “the fact that investors can access previously posted materials or statements on a company's Web site does not in itself mean that such previously posted materials or statements have been reissued or republished for purposes of the antifraud provisions of the federal securities laws, that the company has made a new statement, or that the company has created a duty to update the materials or statements.”
• Separately identified as historical or previously posted materials or statements, including, for example, by dating the posted materials or statements; and
• located in a separate section of the Web site containing previously posted materials or statements.
In other contexts, the Commission has expressed concerns about whether information disclosed on company Web sites would be adequately preserved for purposes of the reporting and liability provisions under the federal securities laws.
Information on company Web sites currently is subject to some but not all Exchange Act liability provisions. Anti-fraud provisions of the federal securities laws, including Exchange Act Section 10(b) and Rule 10b-5, apply to statements made on a company Web site. If a registrant were to make a false or misleading statement of a material fact on its Web site in connection with the purchase or sale of a security, the registrant could face liability under Section 10(b) and Rule 10b-5. These anti-fraud provisions also apply in certain circumstances to third-party information available via hyperlink on a company Web site that could be attributable to the company, in the same way they would apply to any other statement made by, or attributable to, a company.
The reporting provisions of Exchange Act Section 13(a) and Exchange Act Rules 13a-1 and 12b-20 generally do not apply to disclosures on company Web sites. However, if a company fails to satisfy a Web site disclosure option that relieves it of its obligation to file or furnish an Exchange Act report, an action could be brought under the Exchange Act reporting provisions based on the company's failure to file the report.
Material incorporated by reference into a filed document is subject to liability under Section 18 of the Exchange Act, which provides a private cause of action for a false or misleading statement of material fact in a filed document.
Liability under Sections 11 and 12(a)(2) of the Securities Act applies to information in Exchange Act filings when it is incorporated by reference in a registration statement or prospectus. Section 11 imposes liability on an issuer for any untrue statement or omission of a material fact in a registration statement. Section 12(a)(2) of the Securities Act imposes similar liability for material misstatements or omissions in a prospectus or oral communication that constitutes an offer. This liability also applies to information incorporated by reference, where permitted, from Exchange Act filings filed after the registration statement. Under our current rules, disclosure provided on a registrant's Web site rather than in an Exchange Act filing cannot be incorporated by reference into a registration statement or prospectus. Accordingly, it would not be subject to Section 11 liability and would only be subject to Section 12(a)(2) liability to the extent it constitutes an offer.
307. Should we continue to limit the permitted sources of information incorporated by reference to Commission filings, or should we allow registrants to incorporate information from their Web sites?
308. Are there challenges investors may face in using sources outside registrant filings to obtain information about a registrant? If so, what are these challenges? Would investors seeking information on a registrant's Web site rather than in its filings require specialized equipment, knowledge or expertise that some investors may not have? What would be the impact on investors who want to receive materials in paper?
309. Would investors seeking information from third-party sources require specialized equipment, knowledge or expertise that some investors may not have? What would be the impact on investors who want to receive materials in paper? What other challenges would this approach pose for investors or for registrants?
310. Do the benefits or challenges of incorporating information by reference differ based on whether the information is incorporated from a company's Web site or from its filings?
311. If we allow registrants to provide required disclosure by incorporating information by reference to their Web sites, how could registrants limit or delineate the information on their Web sites that is “filed” for liability purposes? What obligation should the registrants have to preserve the material as incorporated or to update the incorporated information? How should it be preserved in the event the registrant exits the reporting system or goes out of business? What would be the impact on the reporting and liability provisions of the federal securities laws if this information is not preserved as required?
312. Are there categories of business or financial information that we should permit registrants to disclose by posting on their Web sites in lieu of including in their periodic reports?
313. Should we permit registrants to meet the requirements of Item 601 of Regulation S-K by incorporating exhibits by reference to documents posted on their Web sites? What would be the benefits and challenges of such an approach?
314. As an alternative to incorporation by reference, should we allow registrants to omit required information from filings when the information is otherwise provided on a registrant's Web site? If so, what information would be appropriate and what additional investor protections should we consider?
315. To the extent that information about a registrant is readily available on its Web site, what are the benefits of continuing to require disclosure of the same information in the registrant's filings? What would be the impact on registrant liability, accuracy of reported information or investor protection generally if we eliminated disclosure requirements for information that investors routinely access from Web sites?
316. Should we consider permitting incorporation by reference from sources other than a registrant's filings or its Web site? If we allow registrants to provide required disclosure by incorporating information by reference to third-party sources, should we require them to include a hyperlink to that information? Would registrants use such an option?
317. What types of investors or third parties are most likely to value disclosure made available on registrant Web sites?
318. To what extent would permitting registrants to incorporate information from their Web sites enable them to realize cost savings, including savings in the administrative and compliance costs of preparing and disseminating disclosure? Please provide quantifications of expected changes in costs if possible.
The business and financial disclosure requirements in Regulation S-K generally do not specify the precise layout or format for disclosure.
While our general approach allows registrants to use discretion in the overall layout of their disclosure, a few items prescribe the format for disclosure. In some cases, basic formatting requirements may be standardized, such as the prescribed location, order or title of required disclosure. For example, the structure of our periodic reports and related rules require registrants to include the numbers and captions of all items in the relevant form.
One commenter recommended disclosure in Q&A form for certain common risk factors, with standardized questions for all registrants allowing only for potential responses of “yes,” “no,” or “NA.”
A standard layout, format, or style requirement may enhance the comparability of disclosures across periods and across issuers and registrants. Such comparability and consistency may reduce the costs of acquiring information, increase valuation accuracy, and enhance investment efficiency.
However, flexibility in the presentation of disclosure may enhance the ability of registrants to tailor disclosure to their individual circumstances and investor bases. Flexibility in presenting disclosure could allow registrants to more effectively communicate the information most critical to understanding their particular company as prescriptive presentation requirements may increase the risk of important information being obscured by less important information. In addition, repetitive disclosure may be due in part to the structure of our Exchange Act forms and related rules, which require registrants to include in their periodic reports the numbers and captions of all items in the relevant form.
319. Do current disclosure requirements appropriately consider the need for both standardization and flexibility in presentation? If not, how could we change our requirements?
320. How could we facilitate or encourage better presentation of disclosure by registrants?
321. Would further prescribing the order and format for presenting information in annual or quarterly reports improve readability or increase comparability across registrants? Would such standardized requirements enhance the ability of investors and third parties to use disclosures, including for large-scale processing and analyses, in a more timely and efficient way?
322. Is there particular information that investors would prefer we require registrants to present in a specific order or in a particular section of the document? If so, which information should be so presented? What would be the advantages or disadvantages of such an approach?
323. Do item numbers and captions improve the clarity, navigability or overall effectiveness of disclosure? Should we revise our rules to reduce or eliminate the requirement to include the item numbers and captions from any of our forms? Why or why not?
324. Should we revise any of our current disclosure rules to require a standardized tabular or graphic presentation rather than, or in addition to, the narrative disclosure we currently require? Which disclosures could be improved by a requirement for tabular or graphic presentation? Would such a presentation improve comparability of disclosure across registrants? Does increased comparability improve transparency or is it otherwise beneficial to investors? What would be the advantages or disadvantages of such an approach?
325. Should we require registrants to present certain disclosures in question-and-answer format? If so, what information would be appropriate for this format? Should we require or permit it for certain types of registrants?
326. Should we permit or require registrants to present certain disclosures in a “check-the-box” presentation, where registrants select the appropriate disclosure from a finite list of options? For example, should we require or permit registrants to indicate by checkbox rather than narrative disclosure portions of the information regarding changes in and disagreements with accountants under Item 304 or management's conclusions regarding the effectiveness of the registrant's disclosure controls and procedures under Item 307? What would be the advantages or disadvantages of such an approach?
327. What disclosure requirements, if any, would generate more meaningful disclosure if we modified or eliminated the specific formatting or presentation requirements and permitted greater flexibility in the manner of presentation?
328. How would disclosure costs or other challenges to registrants be affected by any increase in the use of specific formatting or presentation requirements?
In first implementing our integrated disclosure system, the Commission
The Wheat Report noted that special efforts should be made to call any unusually speculative elements or risk factors of an offering to the attention of the ordinary investor using an introductory statement.
In offering prospectuses, our rules require summary presentations where the length or complexity of the prospectus makes a summary useful.
One commenter proposed the use of “tabs” to organize information topically (
As discussed in Section III.B.2., the informational needs, financial resources, and capacity to analyze disclosure may vary significantly among investors. Highly sophisticated investors may seek a different level or presentation of information than those with fewer financial or analytical resources. For example, some investors may prefer a summary presentation while others may seek detailed data that they can analyze and compare across companies or industries.
329. Other than a summary page, are there other approaches to layering or layered disclosure that we should consider for business and financial information in periodic reports? If so, what are the benefits and challenges of these approaches?
Investors, their financial advisors, and professional analysts use increasingly
Structured disclosures include both numeric and narrative-based disclosures that are made machine-readable by having reported disclosure items labeled (tagged) using a markup language, such as eXtensible Markup Language (“XML”)
Standardized markup languages, such as XBRL, use standard sets of data element tags for each required reporting element, referred to as taxonomies. Taxonomies provide common definitions that represent agreed-upon information or reporting standards, such as U.S. GAAP for accounting-based disclosures.
Commission rules currently require several categories of registrants to provide certain information in XBRL, including, the following:
One commenter supported the continued improvement of tagging and coding of financial reporting, noting that investors and regulators alike would benefit greatly from real time access to comparable, searchable and sortable data.
Several commenters, in a jointly submitted letter, provided a number of specific recommendations to enhance and modernize EDGAR, including enhanced functionality associated with structured data.
One commenter recommended that the Commission require complete “non-dimensional” financial statements to improve XBRL quality and usage.
One commenter encouraged the Commission to transform the current documents-based disclosure system to a system that collects, manages, and disseminates disclosure information as structured data with standardized tags and electronic formats.
The Commission requires registrants and other filers to provide certain information as structured data to facilitate the analysis and improve the accuracy of that information.
By requiring structured data, the Commission has sought to make disclosure easier for investors to access, analyze and compare across reporting periods, registrants, and industries.
In adopting Regulation AB requiring asset-level disclosures in XML, the Commission noted that requiring this information in a standardized machine-readable format makes the data transparent and comparable.
Our rules requiring registrants to file financial and other information in a structured format require that data to be filed as an exhibit to the filing rather than embedded in the filing itself.
First, structured data filed as a separate exhibit does not look like the disclosure in the related HTML document submitted by the registrant unless specially rendered to do so with specialized software.
An axis tag allows a filer to divide reported elements into different dimensions (
In a previous review of the use of custom tags in general in XBRL exhibits, the staff found a steady decline in custom element use by larger registrants, indicating improvements in the U.S. GAAP taxonomy and registrants' selections of tags. However, in contrast to the recent findings on axis extensions, the staff found that smaller filers were associated with an average custom tag rate almost 50% greater than that of larger filers. Staff analysis also revealed that some of the perceived quality issues associated with XBRL data are correlated with particular third-party providers of XBRL software and services, which may be, at least in part, due to continued innovation and growth in the market for filer software and services, resulting in offerings of varying functionality and ease of use.
Second, the redundant process of preparing financial statements and periodic reports in HTML or ASCII and then preparing exhibits in XBRL creates a greater chance of data entry and other errors. Staff identified a number of errors, such as characterization of a number as negative when it is positive, missing amounts and calculations, and other inaccuracies,
We continue to explore ways to incorporate structured data. We also continue to explore changes to the Commission's Web site and the EDGAR system that could enhance the usefulness of structured disclosures. For example, in December 2014, the Commission announced a pilot program under which data that registrants provide in structured formats would be combined and organized into structured data sets and posted for bulk downloads on the Commission's Web site for use by investors and academics.
Concerns have been raised about the costs and time burden associated with structured data requirements. For example, the ACSEC has focused on the costs of structuring disclosures and
We acknowledge that registrants may incur costs to provide disclosure in structured data format, particularly initial set-up costs. We seek public comment on ways to minimize the costs of providing structured disclosures, particularly over time, while still realizing the intended benefits to investors and other users of such disclosures.
330. How can the quality of structured disclosures be enhanced?
331. Are there changes to the EDGAR system that the Commission should make to render the structured disclosure filed by registrants more useful?
332. Are company-specific custom extensions, such as element or axis extensions, useful to investors or other users of structured disclosures? If so, how might these custom extensions be made more useful for enhancing automated analysis? If not, are there better ways to express disclosures that are unique to a company (
333. Should we require registrants to provide additional disclosures in a structured format? If so, which disclosures? For example, are there categories of information in Parts I and II of Form 10-K or in Form 10-Q that investors would want to receive as structured data?
334. To the extent that we consider additional structured data requirements for disclosure in periodic reports, what level of structured data requirements would be appropriate? For example, should we require registrants to identify sections, sub-sections or topics with “block text” labels, or should we require registrants to structure numeric elements and tables individually? What would be the challenges and costs of such an approach? What would be the benefit?
335. How does the availability of structured data in registrants' periodic reports affect the timeliness, efficiency, or depth of investors' review of disclosures? How do the effects of structured disclosure requirements vary across investor types? Are there other methods of structuring disclosures that would make disclosures more accessible or useful?
336. To what extent is the information currently provided in structured disclosures readily available through other sources, such as third-party data aggregators? What are the costs and benefits to investors of obtaining this data from such third parties rather than through the use of structured disclosures filed by registrants?
337. To what extent do investors, analysts, third-party data aggregators, or other market participants rely on structured data provided by registrants in their periodic reports? What specific content in structured disclosures is useful to each of these groups?
338. Are there other ways in which our requirements can improve the accuracy of tagged data? What would be the challenges to registrants posed by such alternatives?
339. Are there certain categories of registrant for which we should provide an exemption from some or all structured disclosure requirements, require more limited information to be tagged, or require a different presentation of this information? Why or why not? If so, to which registrants or structured disclosure requirements should such exemptions apply?
340. In requiring structured data, the Commission has sought to make disclosure easier for investors to access, analyze and compare across reporting periods, registrants, and industries.
We are interested in the public's views on any of the matters discussed in this concept release or on the staff's Disclosure Effectiveness Initiative. We encourage all interested parties to submit comment on these topics. If possible, please reference the specific question numbers or sections of the release when submitting comments. In addition to investors and registrants, the Commission welcomes comment from other market participants and particularly welcomes statistical, empirical, and other data from commenters that may support their views and/or support or refute the views or issues raised. We also solicit comment on any other aspect of our disclosure requirements in Regulation S-K that commenters believe may be improved upon. Please be as specific as possible in your discussion and analysis of any additional issues.
By the Commission.
Category | Regulatory Information | |
Collection | Federal Register | |
sudoc Class | AE 2.7: GS 4.107: AE 2.106: | |
Publisher | Office of the Federal Register, National Archives and Records Administration |