WELL · 42-225-31092 · DISTRICT 6

Temple #1

N

Houston County · Wildcat field  · Vertical

Temple #1 (API 42-225-31092) is a well in Houston County operated by Katy Resources Etx LLC, completed June 2, 2007.

The RRC has issued 2 drilling permits between 2006 and 2009, permitted to 19,800 ft.

Completion filings report 4 formation tops, including Austin Chalk, Knowles, Bossier, Pettit.

No lease production has been reported under this well’s leases.

Operator of record

Katy Resources Etx LLC

Shreveport, LA · P-5 Y, filed May 6, 2011 · 5 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleKaty Resources Etx LLC
Production reportsProex Energy Management, L.L.C.through Nov 2016
Latest permitKaty Resources Etx, LLCOct 7, 2009

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

19,800
total depth, ft
2
permits on file
Oct 7, 2009
last permit issued
Jun 2, 2007
completed
0
cumulative oil, bbl
230K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2007 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 2, 2007
Shut in
—
Plugged
—

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Temple G-6-255214Raintree (Travis Peak Cons.)Proex Energy Management, L.L.C.10230KJul 2009 – Jul 2026
Temple G-6-247804WildcatKaty Resources Etx, LLC100Jun 2007 – Jul 2009

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. 1Katy Resources Etx, LLCJul 2009 → Jan 2011
  2. 2Sun River Operating, Inc.Feb 2011 → May 2012
  3. 3Proex Energy Management, L.L.C.Dec 2015 → Nov 2016

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
685870-99RecompletionKaty Resources Etx, LLCOct 6, 2009Oct 7, 2009Jul 1, 200919,449
628464-99DrillEncana Oil & Gas(usa) Inc.Nov 2, 2006Nov 13, 2006Jan 8, 200719,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-247804————
—— G-6-255214————

Formation tops

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

FormationMD ftSubsea
Austin Chalk——
Knowles——
BossierTOP BOSSIER——
PettitTOP PETTET——

Perforations

Perforated and open-hole intervals.

FromToType
12,06012,396Perforated
12,88813,168Perforated
13,70414,047Perforated
14,14014,592Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3754,56117.51,247 S
9.62512,00012.251,160 S
519,2566.5610 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
00Jun 12, 2010Mar 16, 2010Yes
00Mar 30, 2010——
00Jul 2, 2009Dec 14, 2007Yes
00Jun 10, 2009——

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