Extended Lateral Solutions for an Extremely Difficult Well Trajectory
Bibliographic record
Abstract
Abstract An E&P operator was developing a reservoir and planned a horizontal well in an area where zones above the target cause drilling problems when trying to build angle and land the horizontal lateral. The operator suffered drilling difficulties on offset wells; therefore, it was decided to change the drilling plan for this prospect. The new plan required drilling through the target reservoir, into the formations below and then drill back up dip to the target. After reaching the base at a measured depth of 14,000 ft. the well plan required drilling up at maximum of 114° until reentering the target reservoir. Because of faulting in the area and required well direction, the target reservoir was dipping up at ∼10° laterally in the direction of the horizontal drilling target. To maintain position in the reservoir, the well had to drilled at ∼100° deviation to a measured depth of 21,100 ft. This wellbore trajectory made normal wireline plug and perforating completion operations extremely difficult. The wellbore trajectory meant high frictions on the wireline when coming off bottom. Also, due to the toe-up trajectory there was risk the wireline tools would slide down the inclined casing during and after plug setting and perforating. If the tool position could not be maintained there was risk the wireline cable could be entangled and a stuck tool could result. If the tools overrun the wireline cable the result could be wireline cable next to the perforating guns when detonated and wireline cable severed. The E&P operator needed to know if this challenge could be met. Alternatives to pump down plug and perforating could be very expensive (estimated $millions): Abandon acreage,Continue drilling attempts building angle above the target,Reposition surface location and drill down dip,Reduce angle and shorten lateral in target, orCoiled tubing conveyed plug and perforating completion. To meet the challenge several new methods and technologies developed for extended laterals were utilized. These products and methods included: advanced risk deployment modeling, jacketed wireline cable, addressable separation tool and downhole tension tool.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.003 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.024 | 0.003 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".