TEXAS · WELLS · HANSFORD COUNTY · WINDER-WOOD 1 LEASE · API 42-195-31776 · DISTRICT 08

Winder-Wood 1 #2

Plugged

Hansford County · Hansford NW. (Upper Morrow) field  · Vertical

Winder-Wood 1 #2 (API 42-195-31776) is a plugged well in Hansford County, plugged March 30, 2011, last operated by Laredo Petroleum Inc..

The RRC has issued one drilling permit, issued July 11, 2007, permitted to 7,400 ft.

Operator of record

Laredo Petroleum Inc.

Based in
Tulsa, OK
P-5 status
Inactive (I)
P-5 last filed
Nov 29, 2022
Permits on file
1,795
Phone
(918) 513-4570

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLaredo Petroleum Inc.
Production reportsnone
Latest permitLaredo Petroleum, Inc.Jul 11, 2007
7,400
total depth, ft
1
permits on file
Jul 11, 2007
last permit issued
Aug 8, 2007
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2008 THROUGH —

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 8, 2007
Shut in
—
Plugged
Mar 30, 2011

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
Winder-Wood 1 G-14-254453Hansford, NW. (Upper Morrow)Laredo Petroleum, Inc.100Jan 2008 – —

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
641625-99DrillLaredo Petroleum, Inc.Jun 28, 2007Jul 11, 2007Jul 28, 20077,400

Completions

CompletedLeaseFieldOperatorStatusDepth
Aug 8, 2007Winder-Wood 1 G-14-254453Hansford NW. (Upper Morrow)Laredo Petroleum Inc.Plugged—

Perforations

Perforated and open-hole intervals.

FromToType
1,9602,010Perforated
2,1402,146Perforated
2,2382,270Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,60011680 S
4.52,7008.875650 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
00Apr 9, 2010Mar 13, 2008Yes
00Feb 8, 2010——

Well logs

2 logs loaded from the RRC's log index, the latest received Oct 19, 2010. 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
RESISTIVITYTIFF1,600 to 7,493Oct 19, 2010run Aug 7, 20079.92
NEUTRON/DENSITY POROSITYTIFF1,600 to 7,471Oct 19, 2010run Aug 6, 20075.64

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