TEXAS · WELLS · HANSFORD COUNTY · API 42-195-31780 · DISTRICT 08

Hansford Gas Unit 10 #2

Plugged

Hansford County · Wildcat field  · Vertical

Fields on the latest permit · any of 4
Hansford (Morrow, Middle) · Hansford (Morrow, Upper) · Hansford (White Dolomite) · Hunter (Brown Dolomite)
Not one formation; the well must be completed in one of them, and no target formation is stated. The district's wildcat field is also on the permit.

Hansford Gas Unit 10 #2 (API 42-195-31780) is a plugged well in Hansford County, plugged January 17, 2008, last operated by Laredo Petroleum Inc..

The RRC has issued 2 drilling permits between 2005 and 2007, permitted to 7,850 ft.

It was permitted by Laredo Petroleum, Inc. and has since transferred to Laredo Petroleum Inc. on the wellbore schedule.

Operator of record

Laredo Petroleum Inc.

Permitted by Laredo Petroleum, Inc.; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitLaredo Petroleum, Inc.Dec 11, 2007

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

7,850
total depth, ft
2
permits on file
Dec 11, 2007
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

On this page2 well logs

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Jan 17, 2008

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
649027-99DrillLaredo Petroleum, Inc.Nov 6, 2007Dec 11, 2007Jan 7, 20087,850
557835-99DrillJones Energy, Ltd.Feb 16, 2005Mar 17, 2005—7,850

Well logs

2 logs loaded from the RRC's log index, the latest received Nov 23, 2015. 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 POROSITYTIFF1,642 to 7,852Nov 23, 2015run Jan 13, 20085.25
RESISTIVITYTIFF1,642 to 7,852Nov 23, 2015run Jan 13, 20084.17

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