PlainBillCongress, translated.Legislation. Context. Public interest.Referred to the House Committee on Transportation and Infrastructure.
Congressional Research Service
No official summary is available in the imported record yet.
People & committees
Rep. Smith, Adam [D-WA-9] · D–WA
Legislative record
A procedural vote is different from passage. Passage in one chamber does not establish enactment. Explore the glossary.
Referred to the House Committee on Transportation and Infrastructure.
Introduced in House
Introduced in House
Primary sources
Text links open the official source. We also preserved the text version used in the PlainBill explanation below.
Source last updated: Aug 19, 2026. Consult Congress.gov for the current record.
AI Conversation Starters
Choose a perspective, copy a prompt, and paste it into your preferred AI. Each prompt includes the bill version and available official source links, and asks for counterarguments as well as supporting evidence.
Analyze H.R.10077 as objectively as possible. Explain its main provisions, who would be affected, possible benefits and harms, implementation, exceptions, and uncertainties. Present the strongest arguments for and against it, and identify evidence needed to assess its public impact.
Examine H.R.10077 through a progressive lens, focusing on fairness, access, economic inequality, and effects on vulnerable communities. Explain potential benefits, costs, and unintended consequences. Consider the strongest counterarguments and distinguish stated goals from demonstrated outcomes.
Examine H.R.10077 through a conservative lens, focusing on fiscal responsibility, institutional stability, federalism, and the scope of government. Explain potential benefits, costs, and unintended consequences. Consider the strongest counterarguments and any provisions that challenge this perspective.
Examine H.R.10077 through a civil-liberties and limited-government lens. Consider individual rights, privacy, voluntary choice, accountability, and government power. Explain tradeoffs, possible safeguards, and the strongest counterarguments without assuming the proposal is beneficial or harmful.
PlainBill explanation
Based on the full Introduced in House · 2026-08-10 text. This explanation has not received human editorial review. This overview describes the proposal’s major provisions; it does not establish what its real-world effects would be.
The proposal would require entities with at least $15 billion in annual gross revenue that perform functions delegated by the Federal Aviation Administration (FAA) to certify annually that their boards include two labor representatives and two representatives with aerospace-safety experience. The FAA would have 90 days after enactment to revoke existing delegations to entities that do not meet the revised qualifications.
(A) is authorized to perform functions pursuant to a delegation made by the Administrator of the FAA under section 44702(d); and (B) in the case of an entity with at least $15,000,000,000 in annual gross revenue, certifies to the Administrator, on an annual basis, that the board of directors of such entity includes— (i) two representatives from labor organizations, including 1 representative from each labor organization that represents the employees of such entity that are directly involved in the design and manufacturing of aircraft; and (ii) two representatives with proven experience in aerospace safety and demonstrable outcomes related to such experience.
Not later than 90 days after the date of enactment of this section, the Administrator of the Federal Aviation Administration shall rescind any delegation made under section 44702(d) of title 49, United States Code, to an entity that does not meet the requirements under paragraph (2) of such section 44736(c)(2), as amended by subsection (a).
Section 2 would replace the statutory definition of an “ODA holder.” The revised definition would require the entity to be authorized to perform functions delegated by the FAA Administrator under the specified federal law.
Section 44736(c)(2) of title 49, United States Code, is amended to read as follows: (2) ODA holder The term ODA holder means an entity that— (A) is authorized to perform functions pursuant to a delegation made by the Administrator of the FAA under section 44702(d)
The additional board-membership certification would apply to entities with annual gross revenue of at least $15 billion, including entities exactly at that threshold. These entities would have to certify compliance to the FAA Administrator each year.
in the case of an entity with at least $15,000,000,000 in annual gross revenue, certifies to the Administrator, on an annual basis, that the board of directors of such entity includes—
For entities subject to the certification requirement, the board would have to include two labor-organization representatives. The text also requires one representative from each labor organization representing the entity’s employees directly involved in aircraft design and manufacturing.
(i) two representatives from labor organizations, including 1 representative from each labor organization that represents the employees of such entity that are directly involved in the design and manufacturing of aircraft
For entities subject to the certification requirement, the board would also have to include two representatives with proven aerospace-safety experience and demonstrable outcomes related to that experience.
(ii) two representatives with proven experience in aerospace safety and demonstrable outcomes related to such experience.
The FAA Administrator would be required to revoke existing delegations under the specified law when an entity does not meet the revised qualifications. The deadline would be 90 days after this section’s enactment; revocation would be mandatory.
(b) Review of existing ODA holders Not later than 90 days after the date of enactment of this section, the Administrator of the Federal Aviation Administration shall rescind any delegation made under section 44702(d) of title 49, United States Code, to an entity that does not meet the requirements under paragraph (2) of such section 44736(c)(2), as amended by subsection (a).
The supplied actions snapshot, updated August 19, 2026, records introduction in the House and referral to the House Committee on Transportation and Infrastructure on August 10, 2026.
Source snapshot updated 2026-08-19T21:07:20Z. 2026-08-10: Referred to the House Committee on Transportation and Infrastructure. 2026-08-10: Introduced in House
A closer look
Reviewed version: Introduced in House · 2026-08-10. These findings describe provisions and who may benefit; they are not judgments of waste, corruption, or motive.
This review covers the supplied bill text. “None identified” does not rule out provisions in later versions or accompanying reports and disclosures.
Provisions outside the bill’s main subject, or policy changes attached to appropriations.
None identified in the reviewed text
No unrelated provision or policy change attached to appropriations was identified in the complete supplied introduced text. This conclusion is limited to that version and does not establish the contents of other versions or accompanying materials.
Spending directed to particular recipients or places outside ordinary competitive or formula-based allocation.
None identified in the reviewed text
No congressionally directed spending for particular recipients or places was identified in the complete supplied introduced text. This conclusion is limited to that version; earmark disclosures and committee or conference materials were not supplied.
Narrow exceptions, exemptions, or preferential treatment that warrant a closer look.
None identified in the reviewed text
No materially narrow carve-out, special exemption, or preferential treatment beyond the proposal’s ordinary coverage and central policy requirements was identified in the complete supplied introduced text. This conclusion is limited to that version and does not establish absence in other versions or accompanying materials.
Full text preserved for this analysis. Legislative record snapshot: Aug 19, 2026. How PlainBill uses AI