WELL · 42-469-33229 · DISTRICT 2

New J. K. Estate #3

Plugged

Victoria County · Johnstone (Middle Frio) field  · Vertical

New J. K. Estate #3 (API 42-469-33229) is a plugged well in Victoria County, plugged February 23, 2009, last operated by Dale Operating Company.

The RRC has issued 2 drilling permits between 1997 and 2000, permitted to 6,000 ft.

Completion filings report one formation top, including Frio.

Its 3 leases have reported 2.45K barrels of oil and 225K mcf of gas since July 1997, last reporting in February 2009. The leases carry 3 wells, so these are lease totals, not this well alone.

Operator of record

Dale Operating Company

Dallas, TX · P-5 Y, filed Nov 4, 2025 · 424 permits on file · (940) 642-6602

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDale Operating Company
Production reportsDale Operating Companythrough Aug 2006
Latest permitDale Operating CompanyMay 31, 2000
6,000
total depth, ft
2
permits on file
May 31, 2000
last permit issued
Jun 3, 2000
completed
2.45K
cumulative oil, bbl
225K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 1997 THROUGH Feb 2009

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 3, 2000
Shut in
—
Plugged
Feb 23, 2009

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
New, J. K. Estate G-2-183619Johnstone (Middle Frio)Dale Operating Company10160KJun 2000 – Feb 2009
New, J.K. Estate O-2-8389Johnstone (Lower Frio)Dale Operating Company12.45K6.77KDec 1997 – Dec 2004
New, J. K. Estate G-2-164253Johnstone (Lower Frio)Dale Operating Company1058.6KJul 1997 – Feb 1998

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. 1Dale Operating CompanyJul 1997 → Aug 2006

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
495689-99RecompletionDale Operating CompanyMay 31, 2000May 31, 2000Jun 1, 20005,303
463081-99DrillDale Operating CompanyMay 29, 1997May 29, 1997Jun 15, 19976,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-164253————
—— G-2-183619————
—— O-2-8389————

Formation tops

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

FormationMD ftSubsea
FrioMIDDLE FRIO4,364-4,267

Perforations

Perforated and open-hole intervals.

FromToType
4,3644,368Perforated
5,3045,310Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,43512.25457 S
4.55,6027.875565 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
00Sep 11, 2001Apr 25, 2001Yes
00Aug 10, 2001——
00Aug 21, 1998May 29, 1998—
00Aug 7, 1998——
00Oct 24, 1997Aug 5, 1997Yes
00Sep 15, 1997——

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