TEXAS · WELLS · FREESTONE COUNTY · YORK, B. P. LEASE · API 42-161-33207 · DISTRICT 05

York B. P. #9

Shut in

Freestone County · Teague (CV-Bossier Cons.) field · Temp Abandoned  · Vertical

York B. P. #9 (API 42-161-33207) is a well in Freestone County operated by Valence Operating Company, completed November 11, 2022 and listed as temp abandoned on the RRC schedule, shut in March 1, 2020.

The RRC has issued one drilling permit, issued February 14, 2005, permitted to 12,497 ft.

Completion filings report 6 formation tops, including Bac, BMA, Pettit, Travis Peak.

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 Feb 2020
Latest permitValence Operating CompanyFeb 14, 2005
12,497
total depth, ft
1
permits on file
Feb 14, 2005
last permit issued
Nov 11, 2022
completed
0
cumulative oil, bbl
1.68M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2005 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Nov 11, 2022
Shut in
Mar 1, 2020
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
York, B. P. G-5-211287Teague (CV-Bossier Cons.)Valence Operating Company101.68MApr 2005 – Jul 2026

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. 1Valence Operating CompanyApr 2005 → Feb 2020

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
557647-99DrillValence Operating CompanyFeb 14, 2005Feb 14, 2005Mar 10, 200512,800

Completions

CompletedLeaseFieldOperatorStatusDepth
Nov 11, 2022York B. P. G-5-211287Teague (CV-Bossier Cons.)Valence Operating CompanyTemp Abandoned · shut in Mar 1, 202012,497

Formation tops

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

FormationMD ftSubsea
Bac4,175-3,745
BMA7,710-7,280
Pettit8,430-8,000
Travis Peak8,650-8,220
Cotton Valley10,875-10,445
Bossier12,015-11,585

Perforations

Perforated and open-hole intervals.

FromToType
11,97011,980Perforated
11,97012,320Perforated
12,00612,016Perforated
12,30012,320Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,75512.25695 S
5.512,4978.751,586 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
00Nov 16, 2022Nov 15, 2022—
00Aug 18, 2006Mar 15, 2006—
00Dec 9, 2005Jun 2, 2005Yes
00Oct 7, 2005——

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