BSEE Well API (multiregional online query)

Oil & Gas Drilling - the header record for every borehole the United States has drilled in its own federal waters since the Eisenhower administration. The U.S. Bureau of Safety and Environmental Enforcement (BSEE) keeps one row per borehole/well API number: 57,482 of them at research time, split across four offshore regions - Gulf of America (55,549 wells), Pacific (1,714), Alaska (167) and Atlantic (52). Eighteen documented columns carry identity, location, status and timing for each borehole, and a companion table adds 57k+ one-row-per-completion records keyed to the same identifiers.

Every row answers what a well inventory exists to answer: who drilled it, what type it is, where it sits on the Official Protraction Diagram grid, when it was spudded, when it hit total depth, and whether it is completed or plugged. Filtering runs on operator, region, area, block, lease, borehole status code, field name and spud date range.

Two real rows - one completed Gulf well from 1982, one plugged-and-abandoned veteran spudded in 1963 - show the grain:

API_WELL_NUMBER : 177114063100    REGION_CODE    : G (Gulf of America)
WELL_TYPE_CODE  : D               BOREHOLE_STAT  : COM (completed)
WELL_NAME       : A003            OPERATOR       : GOM Shelf LLC
BOTM_FIELD_CD   : SS169           SPUD DATE      : 4/18/1982
TOTAL_DEPTH_DATE: 5/12/1982       BH_TOTAL_MD    : 10930 ft

API_WELL_NUMBER : 177150052700    REGION_CODE    : G (Gulf of America)
WELL_TYPE_CODE  : D               BOREHOLE_STAT  : PA (plugged & abandoned)
WELL_NAME       : E006            OPERATOR       : Arena Offshore, LP
BOTM_FIELD_CD   : ST131           SPUD DATE      : 12/5/1963
TOTAL_DEPTH_DATE: 2/3/1964        BH_TOTAL_MD    : 13787 ft

That second row is why long-horizon analysts bother: Arena Offshore, LP's E006 was spudded on 12/5/1963, reached total depth on 2/3/1964, and carries a plugged-and-abandoned status effective 4/6/1997 at 13,787 feet measured depth - a thirty-four-year well lifecycle readable from six columns. Live rows for the operators, fields or decades you name arrive with the sample.

All eighteen columns ship with regulator-published definitions and data types - nothing here is reverse-engineered. Two design choices matter more than the rest. First, every well is located twice: a surface trio (SURF_AREA_CODE, SURF_BLOCK_NUMBER, SURF_LEASE_NUMBER) and a bottomhole trio (BOTM_AREA_CODE, BOTM_BLOCK_NUMBER, BOTM_LEASE_NUMBER), both sitting on the Official Protraction Diagram grid alongside BOTM_FLD_NAME_CD, which names the containing field. Second, the API well number itself encodes geography - pseudo-state and county digits up front - so these rows join cleanly against onshore and state well files without a geocoding project in the middle.

• Geo: the entire US Outer Continental Shelf, counted one borehole at a time - Gulf of America with 55,549 of the 57,482 records, Pacific with 1,714, Alaska with 167 and Atlantic with 52. Each location lands on the protraction grid at area/block/lease detail, never a regional total.
• Temporal: spud dates run from the early 1950s onward, and the earliest completion dates in the companion table fall in 1966. The two sample rows alone bracket four decades.
• Granularity: one row per borehole/well API number, with a companion one-row-per-completion table beneath it - so multi-lateral sites and re-drills keep separate identities while rolling up under one operator.

API, files, or your warehouse. Daily, weekly, or hourly.

Ask for the whole 57,482-row ledger or just your slice: one operator's boreholes across all four regions, every well in a single protraction area, or completions flattened onto headers for a decommissioning screen. Extracts arrive shaped to the dictionary above with API well numbers intact, so joins work on arrival instead of after a reconciliation project. Sample first - name the operators, fields or years you care about and check them against your own operations records before anything else happens.

• Data scientists and ML engineers get 57,482 labeled offshore boreholes under a verified eighteen-column schema - the training corpus for activity screening and classification models. See data scientists use cases.
• Investors and quant researchers read operator-level borehole counts and status churn as a supply-side signal ahead of production reports. See investors quants use cases.
• Developers and data-product builders build on stable natural keys: the API well number survives operator changes, so an app wired once stays wired. See developers builders use cases.
• Journalists, academics and students cite a federal regulator rather than a vendor aggregator, which changes the tone of the footnotes. See journalists academics use cases.
• Market researchers and consultants size offshore service markets off the installed well base - fields, blocks and operators in one flat table. See market researchers use cases.

• BSEE Data Center - Offshore Well, Permit, Production & Platform Data - the parent catalog: APD permits, OGOR production since 1996, platforms, pipelines and leases. This entry is the narrow cut; that one is the portal. Start there for breadth, here for well-header depth.
• Texas Railroad Commission Oil & Gas Data Sets - the onshore heavyweight, weekly Full Wellbore files at county detail. Federal waters versus Texas land, side by side.
• Colorado ECMC (COGCC) Data Portal - 124,387 wells with daily-refreshing geometry; the Rocky Mountain counterpart when coverage crosses onto state land.
• EMODnet Human Activities Oil & Gas Wells - European offshore well points; the transatlantic mirror for basin-to-basin comparisons.
• For tempo instead of inventory, the comparison of this dataset against Baker Hughes rig counts puts a stock measure next to a flow measure.