TEXAS · WELLS · FREESTONE COUNTY · KIRSCH GAS UNIT LEASE · API 42-161-32742 · DISTRICT 05
Kirsch Gas Unit #6
Freestone County · Teague (CV-Bossier Cons.) field · Producing · Vertical
Kirsch Gas Unit #6 (API 42-161-32742) is a well in Freestone County operated by Hilcorp Energy Company, completed September 9, 2005 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit (amended once), issued August 20, 2003, permitted to 12,300 ft.
It was permitted by Xto Energy Inc. and has since transferred to Hilcorp Energy Company on the wellbore schedule.
Completion filings report 5 formation tops, including BMA, Pettit, Travis Peak, Cotton Valley.
Its lease has reported 217 barrels of oil and 873K mcf of gas since September 2005, last reporting volume in April 2026.
Operator of record
Permitted by XTO Energy Inc.; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active – Extension (X)
- P-5 last filed
- Mar 27, 2026
- Permits on file
- 3,458
- Phone
- (713) 209-2400
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Hilcorp Energy Company |
| Production reports | Hilcorp Energy Companythrough Apr 2026 |
| Latest permit | XTO Energy Inc.Aug 20, 2003 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 12,300
- total depth, ft
- 2
- permits on file
- Aug 20, 2003
- last permit issued
- Sep 9, 2005
- completed
- 217
- cumulative oil, bbl
- 873K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Sep 2005 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Sep 9, 2005
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Kirsch Gas Unit G-5-216667 | Teague (CV-Bossier Cons.) | Hilcorp Energy Company | 1 | 217 | 873K | Sep 2005 – Apr 2026 |
Gas, mcf lease total
Last 12 months 10,400 · prior 12 14,817(-30%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1XTO Energy Inc.Sep 2005 → Dec 2023
- 2Hilcorp Energy CompanyJan 2024 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 535336-98 | Drill | XTO Energy Inc. | Jan 29, 2004 | Aug 20, 2003 | Jul 23, 2005 | 12,900 |
| 535336-99 | Drill | XTO Energy Inc. | Aug 14, 2003 | Aug 20, 2003 | — | 13,600 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Sep 9, 2005 | Kirsch Gas Unit G-5-216667 | Teague (CV-Bossier Cons.) | Hilcorp Energy Company | Producing | 12,300 |
Formation tops
As filed on W-2/G-1. Subsea from 446 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| BMA | 7,599 | -7,153 |
| Pettit | 8,303 | -7,857 |
| Travis Peak | 8,521 | -8,075 |
| Cotton ValleyCOTTON VALLEY SAND | 10,751 | -10,305 |
| Bossier | 11,601 | -11,155 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 11,646 | 12,076 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 1,176 | 12.25 | 405 S |
| 7 | 11,595 | 8.75 | 1,000 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Oct 16, 2006 | Oct 11, 2005 | Yes |
| 00 | Jun 29, 2006 | — | — |
Well logs
2 logs loaded from the RRC's log index, the latest received Oct 6, 2008. Neutron. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| NEUTRON POROSITYSpans Cotton Valley, Bossier | TIFF | 11,595 to 12,310 | Oct 6, 2008run Aug 15, 2005 | 1.73 |
| NEUTRON POROSITYSpans BMA, Pettit, Travis Peak, Cotton Valley | TIFF | 1,175 to 11,595 | Oct 6, 2008run Aug 8, 2005 | 7.15 |
"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.
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.
- Wellbore filings for 42-161-32742 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-161-32742 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
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/16132742, documented in the API reference.