WELL · 42-355-33874 · DISTRICT 4

Levy A #1

Y

Nueces County · Agua Dulce (Consolidated Frio) field · Producing  · Directional

Levy A #1 (API 42-355-33874) is a well in Nueces County operated by B.P. Productions Inc., completed April 22, 2011 and listed as producing on the RRC schedule.

The RRC has issued 2 drilling permits between 2007 and 2011, permitted to 7,500 ft.

Completion filings report 2 formation tops, including Frio, None.

Its 2 leases have reported 6.58K barrels of oil and 137K mcf of gas since December 2007, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

B.P. Productions Inc.

Victoria, TX · P-5 Y, filed Jan 4, 2026 · 42 permits on file · (361) 578-8024

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleB.P. Productions Inc.
Production reportsB.P. Productions Inc.through Jul 2025
Latest permitB.P. Productions Inc.May 19, 2011
7,500
total depth, ft
2
permits on file
May 19, 2011
last permit issued
Apr 22, 2011
completed
6.58K
cumulative oil, bbl
137K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2007 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 22, 2011
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Levy G-4-246022WildcatB.P. Productions Inc.100Dec 2007 – Jul 2026
Levy "A" O-4-13740Agua Dulce (Consolidated Frio)B.P. Productions Inc.16.58K137KApr 2011 – Jul 2026

Gas, mcf lease total

Last 12 months 1,483 · prior 12 1,802(-18%)

05001K202420252026

Oil, barrels lease total

Last 12 months 22 · prior 12 129(-83%)

050100202420252026

Chain of custody

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

  1. 1B.P. Productions Inc.Apr 2011 → Jul 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
716620-99RecompletionB.P. Productions Inc.May 17, 2011May 19, 2011Apr 13, 20116,000
648435-99DrillWhitehead Prod. Co., Inc.Oct 25, 2007Nov 6, 2007Dec 10, 20077,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-246022————
—— O-4-13740————

Formation tops

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

FormationMD ftSubsea
Frio5,390-5,297
Frio5,400-5,307
FrioFRIO B6,220-6,127
FrioFRIO B6,328-6,235
None——

Perforations

Perforated and open-hole intervals.

FromToType
5,5885,594Perforated
5,9805,983Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,20012.25293 S
5.57,0498.751,343 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 8, 2013Jan 19, 2012Yes
00Apr 22, 2009Feb 9, 2008Yes
00Mar 31, 2009——

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