TEXAS · WELLS · WILLACY COUNTY · BONDY GU LEASE · API 42-489-31148 · DISTRICT 04

Bondy GU #1

Y

Willacy County · Chile Vieja (Frio Deep) field · Producing  · Vertical

Bondy GU #1 (API 42-489-31148) is a well in Willacy County operated by Dewbre Petroleum Corporation, completed August 3, 2006 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued May 11, 2006, permitted to 16,680 ft.

It was permitted by Suemaur Expl. & Prod., LLC and has since transferred to Dewbre Petroleum Corporation on the wellbore schedule.

No lease production has been reported under this well’s leases.

Operator of record

Dewbre Petroleum Corporation

Permitted by Suemaur Expl. & Prod., LLC; the EWA schedule now lists a different operator.

Based in
Corpus Christ, TX
P-5 status
Active (A)
P-5 last filed
Oct 22, 2025
Permits on file
366
Phone
(361) 888-7978

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDewbre Petroleum Corporation
Production reportsDewbre Petroleum Corporationthrough Apr 2026
Latest permitSuemaur Expl. & Prod., LLCMay 11, 2006

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

16,680
total depth, ft
1
permits on file
May 11, 2006
last permit issued
Aug 3, 2006
completed
0
cumulative oil, bbl
1.98M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2006 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 3, 2006
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Bondy GU G-4-226742Chile Vieja (Frio Deep)Dewbre Petroleum Corporation101.98MAug 2006 – Jul 2026

Gas, mcf lease total

Last 12 months 53,142 · prior 12 45,232(+17%)

02K4K6K202420252026

Chain of custody

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

  1. 1Suemaur Expl. & Prod., LLCAug 2006 → Feb 2018
  2. 2South Leeville, LLCMar 2018 → May 2018
  3. 3Dewbre Petroleum CorporationJun 2018 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
619104-99DrillSuemaur Expl. & Prod., LLCMay 11, 2006May 11, 2006May 29, 200618,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Aug 3, 2006Bondy GU G-4-226742Chile Vieja (Frio Deep)Dewbre Petroleum CorporationProducing16,680

Perforations

Perforated and open-hole intervals.

FromToType
15,19415,220Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3752,53517.52,020 S
9.62511,05612.25580 S
516,6716.75360 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
00May 29, 2007Sep 21, 2006Yes
00May 24, 2007——

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