WELL · 42-297-30399 · DISTRICT 2

Bolland, Ernest A. #3

N

Live Oak County  · Vertical

Bolland, Ernest A. #3 (API 42-297-30399) is a former disposal or injection well in Live Oak County, last operated by Blair-Vreeland; its UIC permit is no longer active.

The RRC has issued one drilling permit, issued September 29, 1983, permitted to 4,762 ft.

Completion filings report 2 formation tops, including Hockley, Pettus.

Its lease has reported 40.3K barrels of oil and 16.4K mcf of gas since January 1993, last reporting in July 2026. The lease carries 4 wells, so these are lease totals, not this well alone.

Operator of record

Blair-Vreeland

Corpus Chrsti, TX · P-5 Y, filed Nov 5, 2004 · 26 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsDouble Play Oil & Gas, Incthrough Oct 2002
Latest permitBlair-VreelandSep 29, 1983
4,762
total depth, ft
1
permits on file
Sep 29, 1983
last permit issued
—
completed
40.3K
cumulative oil, bbl
16.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

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; they carry 4 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bolland, Ernest A. O-2-4870Bolland Ranch (Pettus)Apex Energy, Inc.440.3K16.4KJan 1993 – Jul 2026

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

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Triple L Oil CompanyJan 1993 → Oct 1997
  2. 2Dewbre Petroleum CorporationNov 1997 → Oct 2001
  3. 3Double Play Oil & Gas, IncNov 2001 → Oct 2002

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
215734-99RecompletionBlair-VreelandSep 27, 1983Sep 29, 1983—4,762

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-2-4870————

Formation tops

As filed on W-2/G-1. Subsea from 111 ft elevation.Download CSV →

FormationMD ftSubsea
Hockley4,178-4,067
Pettus4,458-4,347

Perforations

Perforated and open-hole intervals.

FromToType
4,0004,006Perforated
—4,525Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62535212.25175 S
4.54,6527.875730 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
00Aug 9, 1999Apr 9, 1999—
00Feb 22, 1989Feb 3, 1989—
00Jan 12, 1984—Yes

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

0
bbl, last 12 reported months
311K
bbl, all reported
Feb 2010
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000062796W-14 DisposalPlugged Jun 11, 20105008004,000–4,020

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

Last 12 months 0 · prior 12 0

0120092010

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/29730399, documented in the API reference.