TEXAS · WELLS · NACOGDOCHES COUNTY · CRANFORD LEASE · API 42-347-33284 · DISTRICT 06

Cranford #2

Y

Nacogdoches County · Appleby N. (Rod-TP Cons) field · Producing  · Vertical

Cranford #2 (API 42-347-33284) is a well in Nacogdoches County operated by Valence Operating Company, completed July 19, 2012 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued October 5, 2011, permitted to 8,360 ft.

Completion filings report 7 formation tops, including Pecan Gap, Austin Chalk, Buda, Base Massive.

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

Operator of record

Valence Operating Company

Based in
Kingwood, TX
P-5 status
Active (A)
P-5 last filed
Jun 4, 2026
Permits on file
990
Phone
(281) 359-3659

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleValence Operating Company
Production reportsValence Operating Companythrough Apr 2026
Latest permitValence Operating CompanyOct 5, 2011
8,360
total depth, ft
2
permits on file
Oct 5, 2011
last permit issued
Jul 19, 2012
completed
0
cumulative oil, bbl
399K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2012 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 19, 2012
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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Cranford G-6-265296Appleby, N. (Rod-TP Cons)Valence Operating Company10399KFeb 2012 – Jul 2026

Gas, mcf lease total

Last 12 months 12,742 · prior 12 12,274(+4%)

01K2K202420252026

Chain of custody

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

  1. 1Valence Operating CompanyFeb 2012 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
725102-98DrillValence Operating CompanyJan 9, 2012Oct 5, 2011Jan 5, 20128,400
725102-99DrillValence Operating CompanySep 27, 2011Oct 5, 2011Jan 5, 20128,200

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 19, 2012Cranford G-6-265296Appleby N. (Rod-TP Cons)Valence Operating CompanyProducing8,360

Formation tops

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

FormationMD ftSubsea
Pecan Gap2,540-2,070
Austin ChalkBASE AUSTIN3,313-2,843
Buda3,701-3,231
Base Massive6,566-6,096
James LimeJAMES7,063-6,593
Pettit7,331-6,861
Travis Peak7,693-7,223

Perforations

Perforated and open-hole intervals.

FromToType
7,1347,164Perforated
7,6247,660Perforated
7,9528,000Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,76811300 S
4.58,3607.875860 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
00May 17, 2013Jan 3, 2013Yes
00Nov 20, 2012Jun 19, 2012Yes

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