WELL · 42-009-42047 · DISTRICT 9

Ikard Trust #1

Plugged

Archer County · Archer County Regular field  · Vertical

Ikard Trust #1 (API 42-009-42047) is a plugged well in Archer County, plugged October 16, 2018, last operated by Rogers Drilling CO. Inc..

The RRC has issued one drilling permit, issued August 26, 2009, permitted to 5,500 ft.

It was permitted by Rogers Drilling CO. and has since transferred to Rogers Drilling CO. Inc. on the wellbore schedule.

Completion filings report 5 formation tops, including Gunsight, Palo Pinto, Strawn, Caddo.

Its lease has reported 8.23K barrels of oil since January 2010, last reporting in February 2019.

Operator of record

Rogers Drilling Co. Inc.

Permitted by Rogers Drilling Co.; the EWA schedule now lists a different operator.

Olney, TX · P-5 Y, filed Oct 4, 2025 · 93 permits on file · (940) 564-2858

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRogers Drilling Co. Inc.
Production reportsRogers Drilling Co., Inc.through Oct 2017
Latest permitRogers Drilling Co.Aug 26, 2009

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

5,500
total depth, ft
1
permits on file
Aug 26, 2009
last permit issued
Jan 2, 2010
completed
8.23K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2010 THROUGH Feb 2019

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 2, 2010
Shut in
—
Plugged
Oct 16, 2018

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Ikard Trust O-13-31541Archer County RegularRogers Drilling Co., Inc.18.23K0Jan 2010 – Feb 2019

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. 1Rogers Drilling Co.Jan 2010 → Dec 2010
  2. 2Rogers Drilling Co., Inc.Jan 2011 → Oct 2017

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
684294-99DrillRogers Drilling Co.Aug 19, 2009Aug 26, 2009Oct 21, 20095,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-31541————

Formation tops

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

FormationMD ftSubsea
GunsightGUNSIGHT LIME98090
Palo PintoPALO PINTO LIME2,552-1,482
StrawnSTRAWN LIME2,950-1,880
CaddoCADDO LIME4,722-3,652
MississippianMISSISSIPPI LIME5,289-4,219

Perforations

Perforated and open-hole intervals.

FromToType
5,2975,309Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62511012.25100 S
4.55,2977.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
00Mar 17, 2010Jan 5, 2010Yes
00Mar 11, 2010——

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