WELL · 42-389-32440 · DISTRICT 8

Osprey 9 #902

Plugged

Reeves County · Toro (Delaware) field  · Vertical

Osprey 9 #902 (API 42-389-32440) is a plugged well in Reeves County, plugged September 6, 2016, last operated by Oxy USA Wtp LP.

The RRC has issued one drilling permit (amended once), issued November 17, 2006, permitted to 7,000 ft.

It was permitted by Thompson, J. Cleo and has since transferred to Oxy USA Wtp LP on the wellbore schedule.

Completion filings report 2 formation tops, including Lamar, Bell Canyon.

Operator of record

OXY USA WTP LP

Permitted by Thompson, J. Cleo; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Sep 4, 2025 · 2,289 permits on file · (713) 215-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOXY USA WTP LP
Production reportsnone
Latest permitThompson, J. CleoNov 17, 2006

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

7,000
total depth, ft
2
permits on file
Nov 17, 2006
last permit issued
Jun 14, 2010
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2008 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 14, 2010
Shut in
—
Plugged
Sep 6, 2016

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
Osprey '9' O-10-39692Toro (Delaware)OXY USA WTP LP100Apr 2008 – Jul 2026

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
628693-98DrillThompson, J. CleoJan 21, 2010Nov 17, 2006Dec 19, 20065,350
628693-99DrillCS SolutionsNov 7, 2006Nov 17, 2006Dec 19, 20067,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-39692————

Formation tops

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

FormationMD ftSubsea
Lamar5,100-2,345
Bell Canyon5,146-2,391

Perforations

Perforated and open-hole intervals.

FromToType
5,1485,184Perforated
5,1555,195Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,52012.25800 S
5.55,3507.875350 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
00Sep 24, 2010Jun 22, 2010—
00Apr 16, 2010Apr 28, 2008—
00Jan 26, 2010——

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) and the University Lands library. then paste it into their search.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

18
bbl, last 12 reported months
4.57M
bbl, all reported
Apr 2017
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000101857H-1 InjectionPlugged Sep 13, 201620,0002,3754,750–5,350

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 18 · prior 12 740,110(-100%)

050K100K150K20162017

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