TEXAS · WELLS · FREESTONE COUNTY · API 42-161-32823 · DISTRICT 05

Reed P No. 1 Gas Unit #7

Y

Freestone County · Freestone (CV-Bossier Cons.) field · Producing  · Vertical

Reed P NO. 1 Gas Unit #7 (API 42-161-32823) is a well in Freestone County operated by Hilcorp Energy Company, completed March 1, 2006 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued November 24, 2003, permitted to 13,098 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 3 leases have reported 8 barrels of oil and 2.23M mcf of gas since March 2004, last reporting volume in April 2026. The leases carry 3 wells, so these are lease totals, not this well alone.

Operator of record

Hilcorp Energy Company

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,454
Phone
(713) 209-2400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHilcorp Energy Company
Production reportsHilcorp Energy Companythrough Apr 2026
Latest permitXTO Energy Inc.Nov 24, 2003

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

13,098
total depth, ft
1
permits on file
Nov 24, 2003
last permit issued
Mar 1, 2006
completed
8
cumulative oil, bbl
2.23M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2004 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 1, 2006
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 3 leases this well is completed on; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Reed "P" No. 1 Gas Unit G-5-200996Freestone (CV-Bossier Cons.)Hilcorp Energy Company182.23MMar 2004 – Apr 2026
Reed "P" No. 1 Gas Unit G-5-200997Oaks (Cotton Valley-Travis Peak)XTO Energy Inc.100Mar 2004 – —
Reed "P" No. 1 Gas Unit G-5-200998Freestone (Bossier Sand)XTO Energy Inc.100Mar 2004 – —

Gas, mcf lease total

Last 12 months 21,632 · prior 12 27,304(-21%)

02K4K6K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1XTO Energy Inc.Mar 2004 → Dec 2023
  2. 2Hilcorp Energy CompanyJan 2024 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
538868-99DrillXTO Energy Inc.Nov 20, 2003Nov 24, 2003Dec 30, 200313,600

Completions

CompletedLeaseFieldOperatorStatusDepth
Mar 1, 2006Reed P No. 1 Gas Unit G-5-200996Freestone (CV-Bossier Cons.)Hilcorp Energy CompanyProducing13,098
Mar 17, 2004Reed P No. 1 Gas Unit G-5-200997Oaks (Cotton Valley-Travis Peak)XTO Energy Inc.Not on Schedule—
Mar 17, 2004Reed P No. 1 Gas Unit G-5-200998Freestone (Bossier Sand)XTO Energy Inc.Not on Schedule—

Formation tops

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

FormationMD ftSubsea
BMA7,466-7,036
Pettit8,144-7,714
Travis Peak8,379-7,949
Cotton ValleyCOTTON VALLEY SAND10,714-10,284
Bossier11,555-11,125
Cotton ValleyCOTTON VALLEY LIME12,707-12,277

Perforations

Perforated and open-hole intervals.

FromToType
10,74411,526Perforated
10,74412,861Perforated
11,57011,930Perforated
12,75412,861Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,54012.25820 S
5.513,0888.75865 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 →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Sep 7, 2006Apr 28, 2006—
00Jun 16, 2004Mar 30, 2004Yes
00May 17, 2004——

Well logs

1 log loaded from the RRC's log index, the latest received Mar 19, 2007. Density, Neutron, Resistivity. 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 describedFiles Intervalft, as filedDatereceivedSizeMB
Combination: Resistivity/Neutron Density PorosityPLATFORM EXPRESSSpans BMA, Pettit, Travis Peak, Cotton Valley, BossierTIFF2,540 to 13,086Mar 19, 2007run Feb 4, 2004—

"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.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

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