TEXAS · WELLS · LOVING COUNTY · FRASER TXL "F" LEASE · API 42-301-31289 · DISTRICT 7B
Fraser TXL F #1
Loving County · Chaparral Draw (Olds) field · Vertical
Fraser Txl F #1 (API 42-301-31289) is a plugged well in Loving County, plugged September 5, 2018, last operated by Wpx Energy Permian LLC.
The RRC has issued one drilling permit, issued February 6, 2006, permitted to 5,000 ft.
It was permitted by Chaparral Energy, L.L.C. and has since transferred to Wpx Energy Permian LLC on the wellbore schedule.
Completion filings report 3 formation tops, including Ramsey, Olds, Bell Canyon.
Its lease has reported 441 barrels of oil and 9.17K mcf of gas since October 2006, with no volume in the three years through April 2026. The lease carries 2 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Chaparral Energy, L.L.C.; the EWA schedule now lists a different operator.
- Based in
- Oklahoma City, OK
- P-5 status
- Active (A)
- P-5 last filed
- Oct 22, 2025
- Permits on file
- 956
- Phone
- (405) 235-3611
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | WPX Energy Permian LLC |
| Production reports | WPX Energy Permian, LLCthrough Nov 2009 |
| Latest permit | Chaparral Energy, L.L.C.Feb 6, 2006 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 5,000
- total depth, ft
- 1
- permits on file
- Feb 6, 2006
- last permit issued
- Oct 9, 2006
- completed
- 441
- cumulative oil, bbl
- 9.17K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Oct 2006 THROUGH Nov 2009
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Oct 9, 2006
- Shut in
- —
- Plugged
- Sep 5, 2018
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; they carry 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Fraser TXL "F" O-10-37903 | Chaparral Draw (Olds) | WPX Energy Permian, LLC | 2 | 441 | 9.17K | Oct 2006 – Nov 2009 |
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.
- 1Chaparral Energy, L.L.C.Oct 2006 → Nov 2009
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 613633-99 | Drill | Chaparral Energy, L.L.C. | Feb 3, 2006 | Feb 6, 2006 | Jun 10, 2006 | 5,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Oct 9, 2006 | Fraser TXL F O-10-37903 | Chaparral Draw (Olds) | WPX Energy Permian LLC | Plugged | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,810 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Ramsey | 3,215 | -405 |
| Olds | 3,246 | -436 |
| Bell CanyonBELL CANYON E | 3,432 | -622 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,291 | 3,354 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 850 | 12.25 | 400 S |
| 5.5 | 4,700 | 7.875 | 380 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 →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Apr 10, 2007 | Nov 15, 2006 | Yes |
| 00 | Dec 27, 2006 | — | — |
Well logs
3 logs loaded from the RRC's log index, the latest received Jul 2, 2009. Density, Neutron, Resistivity, Sonic. 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 described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| ACOUSTIC POROSITYSpans Ramsey, Olds, Bell Canyon | TIFF | 3,200 to 4,696 | Jul 2, 2009run Jun 19, 2006 | 1.15 |
| NEUTRON/DENSITY POROSITYSpans Ramsey, Olds, Bell Canyon | TIFF | 250 to 4,696 | Jul 2, 2009run Jun 19, 2006 | 2.67 |
| RESISTIVITYSpans Ramsey, Olds, Bell Canyon | TIFF | 3,200 to 4,696 | Jul 2, 2009run Jun 19, 2006 | 1.23 |
"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.
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-301-31289 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-301-31289 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it. The University Lands library has no per-well link: then paste it into its 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/30131289, documented in the API reference.