WELL · 42-479-35249 · DISTRICT 4

Puig-Ruthada #17

Plugged

Webb County · Aviators field  · Vertical

Puig-Ruthada #17 (API 42-479-35249) is a plugged well in Webb County, plugged April 20, 2011, last operated by Killam Oil CO. Ltd..

The RRC has issued 2 drilling permits between 1991 and 2011, permitted to 2,000 ft.

Completion filings report 5 formation tops, including Cole, Shaley Sand, Mirando City, Oil Sand.

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

Operator of record

Killam Oil Co. Ltd.

Laredo, TX · P-5 Y, filed Feb 4, 2026 · 837 permits on file · (956) 724-7141

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleKillam Oil Co. Ltd.
Production reportsBuck Management Co. L.L.C.through Mar 2001
Latest permitKillam Oil Co., Ltd.Jan 28, 2011

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

2,000
total depth, ft
2
permits on file
Jan 28, 2011
last permit issued
Feb 10, 2011
completed
23.4K
cumulative oil, bbl
98
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 10, 2011
Shut in
—
Plugged
Apr 20, 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 6 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Puig-Ruthada O-4-177AviatorsBuck Management Co. L.L.C.523.4K98Jan 1993 – Jul 2026
Puig-Ruthada O-4-13644AviatorsKillam Oil Co., Ltd.100Feb 2011 – Aug 2011

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. 1Buck, GeorgeJan 1993 → Jan 1996
  2. 2Buck Management Co. L.L.C.Feb 1996 → Mar 2001

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
709139-99ReenterKillam Oil Co., Ltd.Jan 25, 2011Jan 28, 2011Jan 25, 20112,000
388571-99DrillBuck, GeorgeJun 3, 1991Jun 5, 1991Aug 19, 19912,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-4-177————
—— O-4-13644————

Formation tops

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

FormationMD ftSubsea
Cole1,435-574
Shaley Sand1,454-593
Mirando City1,730-869
Oil Sand1,750-889
Hard Shaley Sand1,760-899

Perforations

Perforated and open-hole intervals.

FromToType
1,4351,442Perforated
1,7221,730Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.51,7907.875207 S
4.51,8167.875330 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
00Jun 3, 2011Mar 15, 2011Yes
00Dec 17, 1991Nov 4, 1991Yes
00Dec 4, 1991——

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