WELL · 42-233-32458 · DISTRICT 10

Holt J. N. #3

Plugged

Hutchinson County · Hutchinson N. (Mississippian) field  · Vertical

Holt J. N. #3 (API 42-233-32458) is a plugged well in Hutchinson County, plugged June 9, 2006, last operated by Strat Land Exploration Company.

The RRC has issued 2 drilling permits (amended once) between 1991 and 2004, permitted to 7,200 ft.

Completion filings report 4 formation tops, including Brown Dolomite, Douglas, Cleveland, Mississippian.

Its lease has reported 20.9K barrels of oil and 82 mcf of gas since January 1993, last reporting in December 2006. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Strat Land Exploration Company

Based in
Tulsa, OK
P-5 status
Inactive (I)
P-5 last filed
Dec 15, 2021
Permits on file
607
Phone
(918) 584-3844

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleStrat Land Exploration Company
Production reportsStrat Land Exploration Companythrough Jun 2004
Latest permitStrat Land Exploration CompanyJul 19, 2004
7,200
total depth, ft
3
permits on file
Jul 19, 2004
last permit issued
Jan 6, 2006
completed
20.9K
cumulative oil, bbl
82
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Dec 2006

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 6, 2006
Shut in
—
Plugged
Jun 9, 2006

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 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Holt, J. N. O-14-6746Hutchinson, N. (Mississippian)Strat Land Exploration Company220.9K82Jan 1993 – Dec 2006

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. 1Strat Land Exploration CompanyJan 1993 → Jun 2004

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
547931-98RecompletionStrat Land Exploration CompanyNov 29, 2004Jul 19, 2004—7,200
547931-99RecompletionStrat Land Exploration CompanyJul 7, 2004Jul 19, 2004—7,200
389544-99DrillStrat Land Exploration CompanyJul 2, 1991Jul 8, 1991Jul 10, 19917,200

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-14-6746————

Formation tops

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

FormationMD ftSubsea
Brown Dolomite3,14063
Douglas4,936-1,733
Cleveland5,696-2,493
MississippianMISSISSIPPI6,580-3,377

Perforations

Perforated and open-hole intervals.

FromToType
6,6556,704Perforated
6,7446,778Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,58512.25875 S
4.56,9807.875200 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
00Nov 7, 2006May 15, 2006—
00Oct 11, 1991Sep 26, 1991Yes
00Oct 9, 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/23332458, documented in the API reference.