TEXAS · WELLS · LIBERTY COUNTY · API 42-291-02076 · DISTRICT 03

Bingle W. L. #1

Plugged

Liberty County · Hull field  · Vertical

Bingle W. L. #1 (API 42-291-02076) is a plugged well in Liberty County, plugged February 15, 2011, last operated by Quail Creek Oil Corporation.

The RRC has issued one drilling permit, issued November 6, 1992, permitted to 8,290 ft.

Its 2 leases have reported 497K barrels of oil and 219K mcf of gas since January 1993, last reporting in July 2026. The leases carry 19 wells, so these are lease totals, not this well alone.

Operator of record

Quail Creek Oil Corporation

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Apr 7, 2026
Permits on file
144
Phone
(713) 956-2070

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleQuail Creek Oil Corporation
Production reportsQuail Creek Oil Corporationthrough Apr 2026
Latest permitQuail Creek Oil CorporationNov 6, 1992
8,290
total depth, ft
1
permits on file
Nov 6, 1992
last permit issued
Nov 7, 1992
completed
497K
cumulative oil, bbl
219K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Nov 7, 1992
Shut in
—
Plugged
Feb 15, 2011

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 2 leases this well is completed on; they carry 19 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bingle, W. L. O-3-2286HullQuail Creek Oil Corporation16426K194KJan 1993 – Jul 2026
Bingle, W. L. O-3-9201Hull (Cook Mountain)Quail Creek Oil Corporation370.1K24.5KJan 1993 – Mar 2008

Oil, barrels lease total

Last 12 months 14,831 · prior 12 19,345(-23%)

01K2K3K202420252026

Gas, mcf lease total

Last 12 months 13,542 · prior 12 13,566(0%)

01K2K3K202420252026

Chain of custody

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

  1. 1Quail Creek Oil CorporationJan 1993 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
404951-99RecompletionQuail Creek Oil CorporationNov 2, 1992Nov 6, 1992Oct 27, 19928,290

Completions

CompletedLeaseFieldOperatorStatusDepth
Nov 7, 1992Bingle W. L. O-3-2286HullQuail Creek Oil CorporationPlugged—
Jun 15, 1952Bingle W. L. O-3-9201Hull (Cook Mountain)Quail Creek Oil CorporationPlugged—

Perforations

Perforated and open-hole intervals.

FromToType
7,6447,650Perforated
7,6647,675Perforated
7,6857,689Perforated
7,7447,754Perforated
7,7867,793Perforated
7,8137,828Perforated
7,8407,860Perforated
7,9027,906Perforated
7,9157,934Perforated
8,5118,748Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37555—70 S
9.6253,005—600 S
2.3758,437——
5.59,1988.75300 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 7, 1993Nov 24, 1992Yes
00Dec 11, 1992Mar 7, 1979—
00Jan 12, 1984Mar 7, 1979—

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.

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