WELL · 42-501-34122 · DISTRICT 8

Bluebonnet 273 #1WD

Plugged

Yoakum County  · Vertical

Bluebonnet 273 #1WD (API 42-501-34122) is a plugged well in Yoakum County, plugged March 14, 1996, last operated by E R Operating Company.

The RRC has issued 2 drilling permits between 1996 and 2016, permitted to 13,100 ft.

Completion filings report 11 formation tops, including Santa Rosa, Yates, San Andres, Glorieta.

It holds an active disposal or injection permit, with 1.04M barrels injected in the 12 months reported through November 2025.

Operator of record

E R Operating Company

Dallas, TX · P-5 Y, filed Nov 4, 2025 · 65 permits on file · (214) 435-0153

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitE R Operating CompanyFeb 19, 2016
13,100
total depth, ft
2
permits on file
Feb 19, 2016
last permit issued
—
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2016 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Mar 14, 1996

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bluebonnet 273 O-11-70654Bluebonnet (Devonian)Roosevelt Resources LP100Jun 2016 – Jul 2026

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
813950-99ReenterE R Operating CompanyFeb 19, 2016Feb 19, 2016Apr 9, 201612,639
444338-99DrillCollins & Ware, Inc.Feb 1, 1996Feb 1, 1996Feb 1, 199613,100

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-70654————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
Santa RosaRED BED-SANTA ROSA1,100
Yates3,162
San AndresSAN ANDRES - HIGH FLOWS, H2S, CO4,554
Glorieta6,112
Clear ForkCLEARFORK - ACTIVE CO2 FLOOD7,346
Wichita-AlbanyWICHITA7,925
Wolfcamp9,040
Pennsylvanian9,676
Strawn10,918
Mississippian11,658
Leonard—

Perforations

Perforated and open-hole intervals.

FromToType
8,10611,434Perforated
12,35212,540Open hole
12,35612,540Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37544517.5400 S
8.6254,80012.252,200 S
5.512,3567.875630 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jan 13, 2023Aug 7, 2022—
00May 30, 2018Jan 23, 2018—
00Jan 31, 2018——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

1.04M
bbl, last 12 reported months
8.18M
bbl, all reported
Nov 2025
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000113637H-1 InjectionActive20,0003,1506,960–12,639

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 1,036,679 · prior 12 1,112,126(-7%)

050K100K150K20242025

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/50134122, documented in the API reference.