TEXAS · WELLS · DUVAL COUNTY · API 42-131-10865 · DISTRICT 04

Duval Ranch Sec. 257 GU #1

Plugged

Duval County · Lundell (Queen City #4) field  · Vertical

Duval Ranch Sec. 257 GU #1 (API 42-131-10865) is a plugged well in Duval County, plugged August 17, 2012, last operated by Killam Oil CO. Ltd..

The RRC has issued 2 drilling permits between 1977 and 1978, permitted to 5,735 ft.

It was permitted by Mobil Oil Corporation and has since transferred to Killam Oil CO. Ltd. on the wellbore schedule.

Operator of record

Killam Oil Co. Ltd.

Permitted by Mobil Oil Corporation; the EWA schedule now lists a different operator.

Based in
Laredo, TX
P-5 status
Active (A)
P-5 last filed
Apr 9, 2026
Permits on file
837
Phone
(956) 724-7141

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleKillam Oil Co. Ltd.
Production reportsKillam Oil Co., Ltd.through Mar 2006
Latest permitMobil Oil CorporationApr 6, 1978

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

5,735
total depth, ft
2
permits on file
Apr 6, 1978
last permit issued
Jul 10, 1966
completed
0
cumulative oil, bbl
45K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Aug 2012

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 10, 1966
Shut in
—
Plugged
Aug 17, 2012

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Duval Ranch Sec. 257 GU G-4-39775Lundell (Queen City #1)Killam Oil Co., Ltd.100Jan 1993 – Aug 2012
Duval Ranch Sec. 257 GU G-4-39776Lundell (Queen City #2)Killam Oil Co., Ltd.1045KJan 1993 – Aug 2012
Duval Ranch Sec. 257 GU G-4-39777Lundell (Queen City #4)Killam Oil Co., Ltd.100Jan 1993 – Aug 2012

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. 1Killam Oil Co., Ltd.Apr 1995 → Mar 2006

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
21526-99RecompletionMobil Oil CorporationApr 6, 1978Apr 6, 1978—5,735
3820-99RecompletionMobil Oil CorporationJul 25, 1977Jul 25, 1977—5,733

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 10, 1966Duval Ranch Sec. 257 GU G-4-39777Lundell (Queen City #4)Killam Oil Co. Ltd.Plugged—
Jul 10, 1966Duval Ranch Sec. 257 GU G-4-39776Lundell (Queen City #2)Killam Oil Co. Ltd.Plugged—
Jul 10, 1966Duval Ranch Sec. 257 GU G-4-39775Lundell (Queen City #1)Killam Oil Co. Ltd.Plugged—

Perforations

Perforated and open-hole intervals.

FromToType
5,4245,440Perforated
5,4565,479Perforated
5,6355,644Perforated

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 12, 1984——

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