WELL · 42-001-02146 · DISTRICT 6

Vickery J. R. #57

Plugged

Anderson County · Slocum field  · Vertical

Vickery J. R. #57 (API 42-001-02146) is a plugged well in Anderson County, plugged February 6, 1990, last operated by HD Operating CO LLC.

The RRC has issued one drilling permit, issued October 7, 1991, permitted to 730 ft.

It was permitted by DG&E/Slocum, Limited Partnership and has since transferred to HD Operating CO LLC on the wellbore schedule.

Completion filings report 2 formation tops, including Newby, Carrizo.

Its lease has reported 951K barrels of oil and 55 mcf of gas since January 1993, last reporting in July 2026. The lease carries 210 wells, so these are lease totals, not this well alone.

Operator of record

HD Operating Co LLC

Permitted by Dg&e/Slocum, Limited Partnership; the EWA schedule now lists a different operator.

Kilgore, TX · P-5 Y, filed Nov 4, 2025 · (972) 977-2462

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHD Operating Co LLC
Production reports84 Energy LLCthrough Oct 2025
Latest permitDg&e/Slocum, Limited PartnershipOct 7, 1991

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

730
total depth, ft
1
permits on file
Oct 7, 1991
last permit issued
—
completed
951K
cumulative oil, bbl
55
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Feb 6, 1990

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; they carry 210 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Vickery, J. R. O-6-1592SlocumHD Operating Co, LLC210951K55Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 1,231 · prior 12 6,241(-80%)

05001K202420252026

Chain of custody

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

  1. 1Dg&e/Slocum, Limited PartnershipJan 1993 → Mar 1994
  2. 2Basa Resources, Inc.Apr 1994 → Mar 2024
  3. 384 Energy LLCApr 2024 → Oct 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
392478-99ReenterDg&e/Slocum, Limited PartnershipOct 3, 1991Oct 7, 1991Oct 21, 1991730

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-6-1592————

Formation tops

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

FormationMD ftSubsea
Newby537-55
Carrizo548-66

Perforations

Perforated and open-hole intervals.

FromToType
551590Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.7560——
5196——
2.375562——
77289115 S
7728——

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 31, 1992Nov 26, 1991—
00Jan 29, 1992——
00Jan 12, 1984Oct 15, 1973—

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