Form U-3A-2 Files Dataset

The Form U-3A-2 Files Dataset is a closed historical archive of EDGAR submissions of Form U-3A-2 and its amendment counterpart Form U-3A-2/A — the "Statement by Holding Company Claiming Exemption Under Rule U-3A-2 from the Provisions of the Public Utility Holding Company Act of 1935." Each record is one accession-numbered filing in which a public-utility holding company self-certifies to the SEC that it qualifies for an annual exemption under Rule U-3A-2 of the Public Utility Holding Company Act of 1935 (PUHCA 1935), based on the predominantly-intrastate concentration of its utility business. The dataset begins with EDGAR's general 1994 onset and terminates at the February 8, 2006 repeal of PUHCA 1935 by the Energy Policy Act of 2005, after which holding-company oversight migrated to FERC and no further Form U-3A-2 filings were made. Records are distributed in monthly ZIP containers and packaged with TXT, JSON, HTML, and PDF file types.

Dataset APIs

Dataset Files

What This Dataset Contains

One record in the Form U-3A-2 Files dataset is a single EDGAR submission of Form U-3A-2 or Form U-3A-2/A, identified by an 18-digit accession number. On disk, each record is a folder named with the dash-stripped accession number (for example 000095017205003182) sitting inside a month-scoped parent folder (YYYY-MM/) within a monthly ZIP container. The folder bundles a metadata.json describing the submission together with the original EDGAR document files that constituted that submission. Image attachments are excluded by dataset policy. The mapping is one filing, one accession number, one record.

Form U-3A-2 is a self-certification by which a public-utility holding company asserts annually that it qualifies for the exemption created by Rule U-3A-2 under PUHCA 1935. The rule exempts a holding company from registration under Section 5 of the Act when the holding company and every public-utility subsidiary are organized in a single state and conduct substantially all of their utility business within that state — the predominantly-intrastate test. Because the certification must be re-affirmed each year on or before March 1, the form recurs annually for each qualifying claimant rather than being a one-time filing. Form U-3A-2/A is the amendment vehicle for correcting or restating an earlier exemption statement and carries the same internal four-item structure as the base form. Filings are submitted under EDGAR Securities-Act category 35 (PUHCA 1935).

The dataset is historically bounded. It begins with EDGAR's 1994 onset and terminates at the February 8, 2006 repeal of PUHCA 1935 by the Energy Policy Act of 2005; subsequent oversight of utility holding companies migrated to FERC under PUHCA 2005 and is not represented here. The corpus can therefore be treated as a complete archival record of Rule U-3A-2 self-certifications submitted to EDGAR. Records are distributed in monthly ZIP containers and packaged with TXT, JSON, HTML, and PDF file types.

Content Structure of a Single Form U-3A-2 Record

A record exists in two layers. The first is the per-filing folder on disk, containing:

• metadata.json — a structured EDGAR submission descriptor identifying the filing, its filer entities, and the constituent documents.
• One or more original EDGAR document files referenced by metadata.json. For Form U-3A-2 the typical case is a single .txt file holding the SGML-wrapped form narrative; HTML and PDF variants also occur, particularly for filings near the form's retirement.

The second layer is the substantive content of the form itself, which lives inside the SGML <TEXT> body of the primary document and follows the SEC's prescribed four-item Form U-3A-2 outline, optionally followed by an Exhibit A financial-statement attachment and a signature block.

The metadata.json descriptor

The metadata file carries the filing-level header information EDGAR captured at acceptance and a manifest of the documents in the submission. Its top-level keys include:

• formType — "U-3A-2" for the base statement or "U-3A-2/A" for an amendment.
• accessionNo — the canonical dashed accession number (e.g. 0000950172-05-003182).
• filedAt — ISO 8601 acceptance timestamp with timezone offset.
• periodOfReport — the as-of date of the exemption claim, typically a fiscal year-end.
• description — the SEC's descriptive label for the form ("Form U-3A-2 - Statement by holding company claiming exemption [Rule 2]").
• linkToFilingDetails, linkToTxt, linkToHtml — URLs back to the primary document, the full SGML submission text, and the EDGAR filing index page on sec.gov.
• linkToXbrl — empty for this form type.
• id — an opaque 32-character hex identifier.
• documentFormatFiles — the document manifest array.
• dataFiles — supplementary structured-data files; consistently empty for U-3A-2.
• entities — one entry per CIK participating in the submission.

Each documentFormatFiles entry carries a sequence value (a numeric string such as "1", or a single space " " for the SGML wrapper), a size byte count as a string, the document description (e.g. FORM U-3A-2 or Complete submission text file), the EDGAR type code (e.g. U-3A-2), and a documentUrl pointing to the file on sec.gov. The entry with sequence: " " refers to the full SGML submission file that EDGAR generates around the document set; that wrapper file is referenced by URL but is not itself stored inside the record folder. Only the individually referenced document files (such as was5284.txt) are physically present on disk.

Each entities entry describes a filer or co-filer with companyName (carrying a role suffix such as (Filer)), the zero-padded 10-digit cik, the form type filed, the act category act (typically "35"), the SEC fileNo (file numbers in the 069- series are characteristic of PUHCA filers), the EDGAR filmNo for the acceptance event, the irsNo employer identifier, the two-letter stateOfIncorporation, and the fiscalYearEnd as MMDD. The state-of-incorporation field is materially informative because the exemption depends on intrastate concentration of the holding-company group.

The primary form document

The primary U-3A-2 document is plain ASCII text wrapped in EDGAR's SGML document tags. The wrapper opens with <DOCUMENT>, <TYPE>U-3A-2, <SEQUENCE>1, <FILENAME> (the on-disk filename), and <DESCRIPTION>FORM U-3A-2, then a <TEXT> body holding the form narrative, then </TEXT> and </DOCUMENT> closers. Page breaks inside the body are denoted by <PAGE> markers in the SEC's prescribed pagination style. The first lines reproduce the standard SEC heading: "Securities and Exchange Commission / Washington, D.C. / FORM U-3A-2 / Statement by Holding Company Claiming Exemption Under Rule U-3A-2 from the Provisions of the Public Utility Holding Company Act of 1935."

The narrative below the heading follows a fixed four-item outline.

Item 1 — Identification of the claimant and its subsidiaries

Item 1 lists the name, state of organization, location of the principal office, and nature of business of the holding company claiming the exemption and of every subsidiary, with the explicit exception of exempt wholesale generators (EWGs) and foreign utility companies, which are routed instead to Item 4. This item establishes the corporate-family structure and is the basis for verifying that the holding company and its public-utility subsidiaries are all organized in the same state.

Item 2 — Description of utility properties

Item 2 contains a brief narrative description of the properties used by the holding-company system for generation, transmission, and distribution of electric energy and for the production, transmission, storage, and distribution of natural or manufactured gas. The level of detail is qualitative — types of facilities, geographic footprint, asset categories — rather than asset-by-asset technical inventories.

Item 3 — Quantitative intrastate-operations data

Item 3 supplies the operational quantification supporting the predominantly-intrastate test. It typically reports prior-calendar-year volumes such as kilowatt-hours of electricity sold and thousand or billion cubic feet (Mcf or Bcf) of gas distributed, broken down by retail versus wholesale and by in-state versus out-of-state delivery. Answers are highly variable in length: non-applicable categories often appear as terse None. or Not applicable. strings, while applicable categories may carry single-figure answers (e.g. 29 Bcf.) or short paragraphs of context.

Item 4 — EWG and foreign-utility-company interests

Item 4 collects, for each interest held by the claimant or any of its system companies in an exempt wholesale generator or a foreign utility company: the name and location of the entity, the capital invested by the claimant, the entity's capitalization and earnings, and any contracts between the claimant or its system companies and the EWG or foreign utility. This carve-out reflects the Energy Policy Act of 1992 amendments to PUHCA 1935, which created the EWG and foreign-utility-company categories under new Sections 32 and 33 of the Act and required separate disclosure of those interests within the exemption statement. When no such interests exist, the item is answered with a brief negation.

Exhibit A and signature block

The narrative body is generally followed by an Exhibit A reference or, where filed inline, a consolidating statement of income and surplus and a consolidating balance sheet of the holding company and its subsidiary companies for the most recent fiscal year. The document closes with a signature block naming the corporate officer(s) executing the certification on behalf of the claimant and a notices/correspondence contact (name and mailing address) for SEC communications regarding the filing.

What the dataset record includes

For each accession the record packages the metadata.json descriptor and the document files that constitute the original EDGAR submission. The on-disk document set is typically dominated by a single SGML-wrapped .txt form file. The file-types found across the dataset as a whole are TXT, JSON, HTML, and PDF — HTML and PDF appear for filings that submitted the form or its Exhibit A in those formats, more commonly toward the end of the form's life as EDGAR migrated to HTML primary documents.

What sits outside the record

The full SGML submission wrapper (<accession>.txt), which EDGAR composes around the entire submission and which contains the EDGAR header block plus all document bodies concatenated, is referenced by URL inside documentFormatFiles but is not itself stored inside the record folder. Image files attached to the original submission are excluded by dataset policy. Form U-3A-2 carries no XBRL component and no dataFiles payload, so there is no structured-data sidecar to be excluded or included. Other PUHCA-related forms (U-1, U5S, U5B, U-13-1, U-57, and so on) belong to separate form-type datasets and are not present here.

Format evolution across the dataset window

The four-item structure of Form U-3A-2 is stable across the 1994–2006 window. The most material content change predates EDGAR coverage: the EWG and foreign-utility-company disclosures in Item 4 were introduced by the Energy Policy Act of 1992 amendments and were already in force before the first dataset record. Beyond that, the form remained a short, prescribed-outline self-certification for the entirety of its life.

The document format evolves along EDGAR's general arc. Most records are SGML-wrapped plain text with <PAGE>-delimited pagination inside <TEXT>; HTML and PDF primary or exhibit documents appear with growing frequency in the early 2000s. Because the form predates and was retired before any XBRL mandate that could have applied to it, no record carries inline XBRL or a separate XBRL instance, and linkToXbrl is consistently empty.

Interpretation and extraction notes

Several nuances matter when reading or extracting from these records:

• Dual accession formatting. Folder names use the 18-digit dash-stripped form (000095017205003182); metadata.json reports the dashed canonical form (0000950172-05-003182). Joining across the two requires normalizing one to the other.
• Variable answer length. Item answers range from one-word negations to multi-paragraph descriptions; robust extraction must handle both extremes and treat <PAGE> markers as in-document pagination rather than content.
• Intrastate-test signal. The stateOfIncorporation on each entities entry, combined with Item 1's per-subsidiary state-of-organization listing and Item 3's in-state-versus-out-of-state volume split, is the core evidence supporting the exemption claim and the natural target for structured extraction.
• Joint filings. The entities array can carry multiple CIKs when affiliated holding companies file together; role suffixes in companyName ((Filer), and occasionally other roles) distinguish the filer of record from co-filers or subjects.
• Amendments. U-3A-2/A filings replicate the four-item structure of the base form and supersede or correct an earlier exemption statement. Linkage between an amendment and the original it corrects is implicit through filer CIK and periodOfReport rather than by an explicit cross-reference field; reconstructing the chain requires grouping by claimant and reporting period.
• Wrapper-versus-document distinction. The sequence: " " entry in documentFormatFiles always describes the EDGAR-generated full submission wrapper, which is not stored locally. The numerically sequenced entries describe the actual document files that are.
• Closed corpus. Because the form was retired in February 2006, the dataset is finite and historically bounded and can be treated as a complete archival record of Rule U-3A-2 self-certifications submitted to EDGAR.

Who Files or Publishes This Dataset, and When

Who files or publishes the record

Each record is one Form U-3A-2 (or Form U-3A-2/A amendment) filed with the SEC by a public utility holding company claiming an exemption from registration under PUHCA 1935. The filer is the holding company itself, signing and verifying the statement through an officer; the underlying electric or gas utility subsidiaries and their state public service commission regulators are not filers.

The U-3A-2 population was a narrow subset of PUHCA "holding companies" — entities that directly or indirectly owned, controlled, or held with power to vote 10% or more of the outstanding voting securities of an electric utility company or gas utility company as defined in PUHCA. Within that universe, U-3A-2 filers were specifically those self-certifying an exemption under one of two prongs of PUHCA Section 3(a):

• Section 3(a)(1): holding companies whose own operations, and those of every subsidiary public utility from which a material part of income was derived, were predominantly intrastate and substantially confined to the single state of organization.
• Section 3(a)(2): holding companies that were themselves predominantly public utility companies, whose operations and those of subsidiary public utilities did not extend beyond the state of organization and states contiguous to it.

Typical filers were parents of small or geographically concentrated electric and gas utilities, including operating utilities that incidentally became holding companies by owning equity in another small intrastate utility.

When the record is required

Form U-3A-2 is a periodic, calendar-driven self-certification, not an event-driven disclosure. Rule U-3A-2 (17 CFR 250.2) requires the statement to be filed annually on or before March 1, reporting the holding company's status as of the close of the preceding calendar year.

The filing trigger is the combination of:

1. Meeting the PUHCA holding-company definition at year-end, and
2. Electing to invoke and preserve the Section 3(a)(1) or 3(a)(2) exemption on a self-executing basis (no Commission order required).

A company that newly came within PUHCA mid-year (for example, by acquiring a 10% voting interest in a covered utility) filed its initial U-3A-2 in the next March 1 cycle and refiled each year so long as it relied on the exemption. Form U-3A-2/A is filed to correct, supplement, or update a previously submitted certification; it does not satisfy the next year's annual obligation.

Regulatory framework and timeline

The obligation arises entirely under PUHCA 1935, a separate statute administered by the SEC alongside the Securities Act and Exchange Act. Section 3(a) authorized the Commission to exempt holding companies lacking the integration and interstate-control concerns the Act targeted, and Rule U-3A-2 was the implementing rule allowing qualifying companies to perfect the (a)(1) or (a)(2) exemption by self-certification rather than by application and order.

EDGAR submissions begin in 1994 (the earliest record in the dataset, January 1, 1994); pre-EDGAR filings exist on paper from the late 1930s onward but are outside this electronic set. The Energy Policy Act of 2005 (Public Law 109-58) repealed PUHCA 1935 effective February 8, 2006 (six months after enactment) and replaced it with the Public Utility Holding Company Act of 2005 (PUHCA 2005), transferring residual holding-company oversight largely to the Federal Energy Regulatory Commission (FERC). PUHCA 2005 uses a narrower framework focused on books-and-records access and does not require an SEC-filed exemption statement, so no Form U-3A-2 has been filed after early 2006 and the dataset is closed.

Important distinctions

• Exempt vs. registered holding companies: Registered holding companies under Section 5 of PUHCA 1935 filed Form U5B (registration) and annual Form U5S, plus transactional forms (U-1, U-12, U-13), and faced substantive SEC regulation. They did not file U-3A-2; a U-3A-2 filer was, by its certification, claiming it should not be treated as a registered holding company.
• Other Section 3 exemptions: Companies relying on Section 3(a)(3), Section 3(a)(4), or Section 3(a)(5) generally sought a Commission order by application rather than self-certifying on U-3A-2. The form is specific to (a)(1) and (a)(2).
• Filer vs. subject utility: State or FERC rate regulation of the underlying utility subsidiaries is a separate regime and produces no U-3A-2 filing.
• Covered utility types: Only owners of an "electric utility company" or "gas utility company" as defined in PUHCA fell within the holding-company definition. Owners of water, telephone, steam, or other utility-like businesses were outside PUHCA and never filed U-3A-2.
• Foreign parents: Non-U.S. parents of U.S. utilities typically could not satisfy the state-of-organization tests in (a)(1) or (a)(2) and instead relied on Section 3(a)(5) or other mechanisms.
• Exchange Act overlap: Many U-3A-2 filers were also Exchange Act registrants filing 10-K, 10-Q, and 8-K. The PUHCA obligation runs independently and in parallel; a U-3A-2 is not embedded in or substituted by any Exchange Act report.

How This Dataset Differs From Similar Datasets or Filings

Form U-3A-2 belongs to the closed PUHCA 1935 family administered by the SEC from 1935 through February 2006. The most useful comparisons fall into four groups: other PUHCA-family forms, order-based exemptions under Sections 3(a)(3)–(5), Exchange Act periodic reports filed by the same issuers, and the FERC-administered PUHCA 2005 successor filings. Each overlaps with U-3A-2 in filer population or subject matter but diverges sharply in trigger, content, or current availability.

Form U5B — Registration Statement of Holding Companies

U5B was the one-time registration filed by holding companies that did not qualify for an exemption and accepted full PUHCA 1935 oversight. It is the regulatory mirror image of U-3A-2: extensive corporate structure, capitalization, intercompany contracts, and subsidiary descriptions, filed once on registration rather than annually. U-3A-2 documents firms claiming exemption; U5B documents firms that could not.

Form U5S — Annual Report for Registered Holding Companies

U5S is the closest periodic analogue: an annual SEC filing by utility holding companies. The substance is opposite. U5S is a comprehensive system-wide financial and operational report (subsidiary financials, intercompany transactions, service company allocations, officer/director data) often running hundreds of pages. U-3A-2 is a brief exemption certification with revenue ratios and an intrastate attestation. U5S = registered systems with depth; U-3A-2 = exempt systems with a narrow eligibility claim.

Form U-1 — Application/Declaration Under PUHCA

U-1 is event-driven and approval-seeking: registered systems file it to obtain an SEC order for a specific transaction, financing, acquisition, or reorganization. U-3A-2 is periodic and self-executing: no event, no order, just an annual recertification. Filer populations barely overlap, since U-1 applies almost exclusively to registered (non-exempt) systems.

Form U-9C-3 — Quarterly Report of Service Companies

U-9C-3 is filed quarterly by mutual and subsidiary service companies inside registered systems and covers service-company billings and intercompany cost allocations. It differs from U-3A-2 on three axes simultaneously: cadence (quarterly vs. annual), subject (service-company economics vs. holding-company exemption status), and entity (service company vs. parent holding company). Exempt U-3A-2 filers typically had no U-9C-3 obligation.

Form U-13-60 — Annual Report for Mutual and Subsidiary Service Companies

U-13-60 is the annual counterpart to U-9C-3, again filed by service companies inside registered systems. It shares only annual cadence with U-3A-2; the entity type, subject matter (service-company costs, personnel, allocations), and underlying registered-system status are all different.

Order-based exemptions under Sections 3(a)(3)–(5)

U-3A-2 implements the rule-based, self-executing exemption under Sections 3(a)(1) and 3(a)(2) (predominantly intrastate systems). Sections 3(a)(3)–(5) exemptions covered different fact patterns — incidental utility business, foreign utility companies, temporary holding-company status — and required an affirmative SEC order rather than annual self-certification. They surface in EDGAR as one-off applications and orders, not as a recurring form. Practically, U-3A-2 yields a clean repeating annual panel; Section 3(a)(3)–(5) exemptions yield sparse, case-specific documents that cannot be aligned year over year.

Exchange Act periodic reports

Many U-3A-2 filers were also Exchange Act registrants filing 10-K, 10-Q, and 8-K. The overlap is at the entity level, not the disclosure level. A 10-K provides audited consolidated financials, MD&A, risk factors, and segment data under Regulations S-K and S-X. U-3A-2 provides only the revenue and operational ratios needed to demonstrate intrastate predominance under PUHCA 1935 — data points that do not reliably appear in Exchange Act filings. The two are complementary: 10-K for financial depth, U-3A-2 for the explicit annual exemption claim. After February 2006, 10-K continues; U-3A-2 stops.

FERC PUHCA 2005 successor filings (FERC-65, 65A, 65B)

The Energy Policy Act of 2005 repealed PUHCA 1935 effective February 2006 and transferred holding-company oversight to FERC under PUHCA 2005. The successor filings are FERC-65 (notification of holding-company status), FERC-65A (amendments), and FERC-65B (waiver of FERC-65 requirements, the closest functional analogue to U-3A-2's exemption notice). Three differences matter for data work:

• Venue: FERC eLibrary, not EDGAR; different form numbering and document formats.
• Statutory test: PUHCA 2005 centers on FERC books-and-records access and cost allocation, not the structural and intrastate-predominance restrictions of PUHCA 1935.
• Coverage seam: A continuous holding-company exemption history across the 2006 boundary requires combining U-3A-2 (through February 2006) with FERC-65/65A/65B (from February 2006 forward). Neither side covers the full timeline alone.

Boundary summary

The Form U-3A-2 Files dataset is distinct on four combined features that no other SEC dataset replicates: (1) it is tied to the repealed PUHCA 1935 regime and is therefore a closed corpus running 1994 through early 2006; (2) it is a self-certifying annual exemption claim, not a registration, transaction approval, or financial report; (3) it isolates predominantly intrastate utility holding companies, a population not separately identifiable from any Exchange Act form; and (4) it contains the specific Section 3(a)(1)–(2) revenue and operational ratios that do not appear elsewhere. U5B is one-time registration; U5S and U-1 cover registered systems; U-9C-3 and U-13-60 cover service companies; 10-K covers financial disclosure but not the exemption claim; FERC-65/65A/65B continue the regulatory thread under a different agency, statute, and repository. U-3A-2 is the canonical SEC source for the intrastate utility holding company exemption population in its final twelve years — a complement to, not a substitute for, any of the above.

Who Uses This Dataset

Because Form U-3A-2 was retired in February 2006, this is a closed historical corpus and its users reconstruct, litigate, or study the pre-2006 utility holding company landscape rather than monitor live filings.

Energy and utilities lawyers handling legacy matters

Counsel working on successor liability, environmental allocation, stranded-cost recovery, or rate-case disputes whose record reaches back into the PUHCA era pull contemporaneous self-representations directly from the form. They rely on Item 1's identification of the holding company and its subsidiaries, the certification and signature block, and the stateOfIncorporation and fileNo fields in metadata.json to fix what a registrant disclosed on a given date. Output: briefs, expert reports, and submissions to successor regulators.

M&A and transaction diligence on long-lived utility assets

Diligence teams tracing transmission rights, generation portfolios, and rate-base elements that originated before 2006 use the year-over-year Item 1 subsidiary listings together with U-3A-2/A amendment trails to confirm which operating utility sat under which holding company in which year. Reconciling accessionNo, periodOfReport, and the entities array across consecutive annual filings reconstructs the corporate genealogy needed for representations and warranties review and title work.

Forensic accountants and litigation-support analysts

Forensic accountants engaged on disputes involving defunct or merged utility entities use Item 1's certified subsidiary roster and the Exhibit A consolidating income statement and balance sheet to anchor damages models and historical control questions. The certified character of these statements is what gives them evidentiary weight in expert reports.

Federal and state utility-commission staff revisiting old records

Staff at federal energy regulators and state public utility commissions revisit Form U-3A-2 filings when adjudicating long-running rate cases, affiliate-transaction reviews, or cost-recovery proceedings whose evidentiary record predates 2006. They focus on Item 3's intrastate-versus-out-of-state volume splits (kWh sold, Mcf or Bcf distributed) and Item 1's per-subsidiary state of organization to verify what the holding company represented to the SEC at the time.

Energy economists and academic researchers

Industrial-organization and energy economists studying the pre-restructuring utility industry use Item 3's quantitative intrastate-operations data to build state-level panels of holding-company activity and Item 4's EWG and foreign-utility-company disclosures to track unregulated affiliate exposure. The closed window supports natural-experiment designs around the 2005 repeal and Energy Policy Act of 1992 amendments.

Regulatory and corporate historians

Historians of U.S. utility regulation use the corpus as primary-source evidence for how holding companies positioned themselves under Rule U-3A-2's predominantly-intrastate test in the final decade of PUHCA 1935. They read Item 1's narrative claims, Item 2's qualitative property descriptions, and amendment filings to periodize PUHCA enforcement and document the run-up to repeal.

Policy analysts assessing PUHCA repeal

Policy researchers examining how the 2005 repeal reshaped utility oversight use the population of filers in the final pre-repeal years as a baseline. The distribution of filer CIKs, stateOfIncorporation values, and Item 3 in-state operations supports retrospective impact studies and comparison to the successor framework administered by federal energy regulators.

Archival data engineers and RAG developers

Teams building searchable archives of historical EDGAR content or domain corpora for retrieval-augmented systems treat the dataset as a self-contained ingest target. The bounded scope (1994 through February 2006), stable four-item outline, and consistent metadata.json schema make it well suited to closed-period extraction pipelines and to grounding LLM answers about pre-2006 utility holding structures that current EDGAR sources cannot supply.

Demand for this dataset concentrates wherever pre-2006 utility corporate facts still matter: legacy litigation, deep-record regulatory proceedings, diligence on long-lived assets, academic and policy research on the pre-restructuring industry, and archival systems covering discontinued form types. Item 1's subsidiary listings, Item 3's intrastate volumes, Item 4's EWG disclosures, and the U-3A-2/A amendment chain are the load-bearing fields across these uses.

Specific Use Cases

The use cases below tie directly to the bounded 1994 through February 2006 scope of the Form U-3A-2 Files dataset and to the specific items, exhibits, and metadata fields the records carry.

Reconstructing pre-2006 utility holding company genealogies

Diligence teams and successor-liability counsel rebuild year-by-year corporate trees by joining Item 1 subsidiary listings across consecutive annual filings for the same claimant CIK. Grouping records on entities[].cik and periodOfReport, then folding in U-3A-2/A amendments by matching claimant and reporting period, produces a per-year roster of operating utilities under each holding company. The output is a longitudinal subsidiary map used in M&A representations and warranties, title work on long-lived transmission and generation assets, and tracing of stranded-cost obligations to their pre-2006 owners.

Building a state-level panel of intrastate utility operations

Energy economists extract Item 3's quantitative intrastate operations data — kWh sold, Mcf or Bcf distributed, retail versus wholesale, in-state versus out-of-state — and combine it with the stateOfIncorporation field on each entities entry to assemble a 1994–2006 state-by-year panel of exempt holding company activity. The closed window and fixed February 2006 endpoint make the panel suitable for difference-in-differences and event-study designs around the PUHCA 1935 repeal and the Energy Policy Act of 1992 EWG amendments.

Tracking EWG and foreign utility company exposure across the exempt population

Item 4 is the only place inside a U-3A-2 record where exempt wholesale generator and foreign utility company interests are itemized — by entity name, location, capital invested, capitalization and earnings, and intercompany contracts. Researchers and policy analysts mine Item 4 across the corpus to measure how unregulated affiliate exposure grew inside the predominantly-intrastate exempt population during the run-up to repeal, and to identify which exempt holding companies carried material EWG or foreign utility positions in any given year.

Anchoring evidentiary records in legacy rate cases and cost-recovery disputes

Federal and state commission staff and forensic accountants pull specific accession numbers as the contemporaneous self-representation a holding company made to the SEC on a given date. The Item 1 subsidiary roster, the certified Exhibit A consolidating statement of income and surplus and consolidating balance sheet, and the signature block together support damages models, affiliate-transaction reviews, and rate-base questions in proceedings whose record reaches back into the PUHCA era. The certified character of Exhibit A is what gives those numbers evidentiary weight.

Reconstructing amendment chains for restated exemption claims

Because U-3A-2/A amendments carry no explicit cross-reference to the filing they correct, reconstructing the chain requires grouping records by claimant CIK and periodOfReport and ordering by filedAt. Litigation-support analysts and historians use the resulting chains to identify which exemption claims were later restated, what changed between the original and the amendment (typically in Item 1 subsidiary identity or Item 3 volumes), and how often a given holding company revised its predominantly-intrastate representation.

Grounding a closed-period RAG corpus on pre-2006 utility holding structures

Archival data engineers ingest the dataset as a self-contained retrieval target for questions that current EDGAR and FERC sources cannot answer — for example, which subsidiaries a named holding company claimed under Rule U-3A-2 in a specific year, or what intrastate volumes it reported. The fixed four-item outline, consistent metadata.json schema, and bounded 1994–February 2006 scope let the pipeline normalize once and stop, with no concern that new records will arrive after repeal.

Dataset Access

Dataset Index JSON API: [https://api.sec-api.io/datasets/form-u3a2-files.json](https://sec-api.io/datasets)

This endpoint returns metadata describing the Form U-3A-2 Files dataset, including its name, description, last update timestamp, earliest sample date, total record count, total size, covered form types (U-3A-2 and U-3A-2/A), container format (ZIP), and file types contained inside each archive (TXT, JSON, HTML, PDF). It also returns the full dataset download URL and a containers array listing every individual container file with its size, record count, last updated timestamp, and direct download URL. This endpoint does not require an API key, which makes it convenient for polling daily to detect which containers were modified in the most recent refresh and to selectively download only the containers that changed.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-699c-a2b3-a3ea08452f9f",
        

          3
            "datasetDownloadUrl": "https://api.sec-api.io/datasets/form-u3a2-files.zip",
        

          4
            "name": "Form U-3A-2 Files Dataset",
        

          5
            "updatedAt": "2026-04-15T12:01:52.475Z",
        

          6
            "earliestSampleDate": "1994-01-01",
        

          7
            "totalRecords": 2200,
        

          8
            "totalSize": 28346056,
        

          9
            "formTypes": ["U-3A-2", "U-3A-2/A"],
        

          10
            "containerFormat": "ZIP",
        

          11
            "fileTypes": ["TXT", "JSON", "HTML", "PDF"],
        

          12
            "containers": [
        

          13
              {
        

          14
                "downloadUrl": "https://api.sec-api.io/datasets/form-u3a2-files/2026/2026-03.zip",
        

          15
                "key": "2026/2026-03.zip",
        

          16
                "size": 13818783,
        

          17
                "records": 154,
        

          18
                "updatedAt": "2026-03-21T02:51:19.000Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

Download Entire Dataset: [https://api.sec-api.io/datasets/form-u3a2-files.zip](https://sec-api.io/datasets)?token=YOUR_API_KEY

Downloads the complete dataset as a single ZIP archive containing every container file. This endpoint requires a valid API key passed via the token query parameter.

Download Single Container: [https://api.sec-api.io/datasets/form-u3a2-files/2026/2026-03.zip](https://sec-api.io/datasets)?token=YOUR_API_KEY

Downloads one individual monthly container instead of the full dataset, which is useful for incremental updates after a daily refresh. Container paths are listed in the containers array of the index JSON. This endpoint requires a valid API key.

Frequently Asked Questions

What forms does this dataset cover?

The dataset covers Form U-3A-2 (the base statement) and Form U-3A-2/A (the amendment counterpart). Both forms are EDGAR submissions filed under Securities-Act category 35 (PUHCA 1935) and share the same internal four-item outline.

What does one record in this dataset represent?

One record is a single EDGAR submission of Form U-3A-2 or Form U-3A-2/A, identified by an 18-digit accession number. Each record is a folder containing a metadata.json descriptor and the original EDGAR document files (typically a single SGML-wrapped .txt form file, occasionally HTML or PDF documents) that constituted the submission.

Who was required to file Form U-3A-2?

Public-utility holding companies self-certifying an exemption under Section 3(a)(1) or 3(a)(2) of PUHCA 1935 — that is, companies whose own operations and those of their public-utility subsidiaries were predominantly intrastate (3(a)(1)) or predominantly confined to the state of organization and contiguous states (3(a)(2)). The filer was the holding company itself, signing through a corporate officer, not the operating utility subsidiaries.

When was Form U-3A-2 filed each year?

Rule U-3A-2 (17 CFR 250.2) required the statement to be filed annually on or before March 1, reporting the holding company's status as of the close of the preceding calendar year. Form U-3A-2/A amendments could be filed at any time to correct, supplement, or update a previously submitted certification but did not satisfy the next year's annual obligation.

What time period does the dataset cover?

The dataset begins on January 1, 1994 (EDGAR's general onset for PUHCA filings) and ends in early 2006. The Energy Policy Act of 2005 repealed PUHCA 1935 effective February 8, 2006, terminating the Form U-3A-2 obligation; no further records can be added, so the corpus is closed.

How does Form U-3A-2 differ from Form U5S?

U5S was a comprehensive annual report for registered holding companies under Section 5 of PUHCA 1935, often hundreds of pages long, with subsidiary financials, intercompany transactions, and service-company allocations. Form U-3A-2 is the opposite: a brief annual exemption certification by holding companies claiming they should not be treated as registered holding companies. The two populations are mutually exclusive — a registrant filed U5S, an exempt holding company filed U-3A-2.

What file formats are inside the dataset?

The dataset is distributed as monthly ZIP containers. Inside each container, records carry TXT (the SGML-wrapped form narrative), JSON (the metadata.json descriptor), and — more commonly toward the end of the form's life — HTML and PDF documents for filings or Exhibit A attachments submitted in those formats. Form U-3A-2 carries no XBRL component.

How do I access the dataset programmatically?

The Dataset Index JSON API at https://api.sec-api.io/datasets/form-u3a2-files.json returns metadata and per-container download URLs without requiring an API key. The full dataset can be downloaded as a single ZIP at https://api.sec-api.io/datasets/form-u3a2-files.zip?token=YOUR_API_KEY, and individual monthly containers at https://api.sec-api.io/datasets/form-u3a2-files/YYYY/YYYY-MM.zip?token=YOUR_API_KEY. The two download endpoints require a valid API key.