WELL · 42-317-46844 · DISTRICT 10
Ranch Water Unit 2 #101M
Martin County · Horizontal
Ranch Water Unit 2 #101M (API 42-317-46844) is a permitted horizontal well in Martin County filed by Xto Energy Inc.; no completion report is on file yet.
The RRC has issued one drilling permit (amended once), issued June 11, 2025, permitted to 10,103 ft.
Completion filings report 10 formation tops, including Santa Rosa, Yates, Queen, Grayburg.
Operator of record
Spring, TX · P-5 X, filed Apr 8, 2026 · 16,156 permits on file · (346) 502-1572
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | XTO Energy Inc.Jun 11, 2025 |
- 10,103
- total depth, ft
- 2
- permits on file
- Jun 11, 2025
- last permit issued
- —
- completed
- —
- cumulative oil, bbl
- —
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
Surface location
32.306926, -101.792215
OpenStreetMap → · Google Maps →
Permit surface location from the RRC GIS record, in Martin County.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 908444-98 | Drill | XTO Energy Inc. | Sep 15, 2025 | Jun 11, 2025 | Sep 14, 2025 | 10,103 |
| 908444-99 | Drill | XTO Energy Inc. | Jun 5, 2025 | Jun 11, 2025 | — | 10,103 |
Formation tops
As filed on W-2/G-1. Subsea from 2,634 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Santa Rosa | 1,177 | 1,457 |
| Yates | 2,185 | 449 |
| Queen | 2,981 | -347 |
| Grayburg | 3,364 | -730 |
| San AndresSAN ANDRES - ACTIVE CO2 FLOOD; H | 3,580 | -946 |
| Clear ForkCLEARFORK | 5,575 | -2,941 |
| Spraberry | 7,006 | -4,372 |
| Dean | 8,324 | -5,690 |
| Wolfcamp | 8,517 | -5,883 |
| Cisco | — | — |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 1,420 | 17.5 | 1,495 S |
| 9.625 | 8,112 | 12.25 | 1,740 S |
| 5.5 | 21,135 | 8.5 | 3,485 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Aug 18, 2026 | May 29, 2026 | Yes |
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.
- Wellbore filings for 42-317-46844 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-317-46844 → scanned completion filings
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.
Nearby wells and their tops
NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM
Draw a cross-section
This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.
Ranch Water Unit 242-317-46264
0.2 KM · XTO Energy Inc. · Section with this well →
| Santa Rosa | 1,182 | 1,455 |
| Yates | 2,197 | 440 |
| Queen | 2,993 | -356 |
| Grayburg | 3,389 | -752 |
| San Andres | 3,568 | -931 |
| Clear Fork | 5,595 | -2,958 |
| Spraberry | 7,017 | -4,380 |
| Dean | 8,331 | -5,694 |
10 TOPS · FIRST 8
Ranch Water Unit 242-317-46263
0.2 KM · XTO Energy Inc. · Section with this well →
| Santa Rosa | 1,177 | 1,457 |
| Yates | 2,184 | 450 |
| Queen | 2,978 | -344 |
| Grayburg | 3,361 | -727 |
| San Andres | 3,586 | -952 |
| Clear Fork | 5,561 | -2,927 |
| Spraberry | 7,005 | -4,371 |
| Wolfcamp | — |
10 TOPS · FIRST 8
Ranch Water Unit 242-317-46262
0.2 KM · XTO Energy Inc. · Section with this well →
| Santa Rosa | 1,177 | 1,457 |
| Yates | 2,171 | 463 |
| Queen | 2,982 | -348 |
| Grayburg | 3,364 | -730 |
| San Andres | 3,582 | -948 |
| Spraberry | 7,009 | -4,375 |
| Dean | 8,313 | -5,679 |
| Pennsylvanian | — |
10 TOPS · FIRST 8
Ranch Water Unit 242-317-46261
0.2 KM · XTO Energy Inc. · Section with this well →
| Clear Fork | 5,577 | -2,943 |
| Dean | 8,315 | -5,681 |
| Wolfcamp | 8,508 | -5,874 |
| Devonian | — | |
| Mississippian | — | |
| Pennsylvanian | — | |
| Silurian (undifferentiated) | — | |
| Strawn | — |
10 TOPS · FIRST 8
Ranch Water 34-2M42-317-46845
0.2 KM · XTO Energy Inc. · Section with this well →
| Santa Rosa | 1,181 | 1,465 |
| Yates | 2,205 | 441 |
| Queen | 2,994 | -348 |
| Grayburg | 3,373 | -727 |
| San Andres | 3,571 | -925 |
| Clear Fork | 5,584 | -2,938 |
| Spraberry | 7,003 | -4,357 |
| Wolfcamp | — |
10 TOPS · FIRST 8
Ranch Water Unit 242-317-46267
0.2 KM · XTO Energy Inc. · Section with this well →
| Santa Rosa | 1,181 | 1,455 |
| Yates | 2,196 | 440 |
| Queen | 2,987 | -351 |
| Grayburg | 3,379 | -743 |
| San Andres | 3,563 | -927 |
| Spraberry | 7,004 | -4,368 |
| Dean | 8,327 | -5,691 |
| Cisco | — |
10 TOPS · FIRST 8
Ranch Water Unit 242-317-46268
0.2 KM · XTO Energy Inc. · Section with this well →
| Santa Rosa | 1,181 | 1,455 |
| Yates | 2,189 | 447 |
| Queen | 2,988 | -352 |
| Grayburg | 3,387 | -751 |
| San Andres | 3,566 | -930 |
| Clear Fork | 5,584 | -2,948 |
| Spraberry | 7,006 | -4,370 |
| Cisco | — |
10 TOPS · FIRST 8
Sand Storm Unit 2 083642-317-43921
0.4 KM · XTO Energy Inc. · Section with this well →
| Santa Rosa | 1,007 | 1,604 |
| Yates | 2,210 | 401 |
| Queen | 3,311 | -700 |
| Grayburg | 3,540 | -929 |
| San Andres | 3,603 | -992 |
| Spraberry | 6,858 | -4,247 |
| Dean | 8,346 | -5,735 |
| Wolfcamp | 8,539 | -5,928 |
16 TOPS · FIRST 8
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/31746844, documented in the API reference.