MétaCan
Menu
Retour à la cohorte
Enregistrement W2115076463 · doi:10.2118/03-11-02

Proppant Flowback Control in Deviated Shallow Gas Wells

2003· article· en· W2115076463 sur OpenAlexaffabout
David J. Browne, Bradley Wilson

Notice bibliographique

RevueJournal of Canadian Petroleum Technology · 2003
Typearticle
Langueen
DomaineEngineering
ThématiqueGeotechnical Engineering and Underground Structures
Établissements canadiensARC Resources (Canada)
Organismes subventionnairesnon disponible
Mots-clésPetroleum engineeringWellboreWellheadGeologyHydraulic fracturingCompletion (oil and gas wells)Oil shale

Résumé

récupéré en direct d'OpenAlex

Abstract This case-history paper presents results from various proppant flowback prevention methods. The wells studied are part of a shallow gas development project near Brooks, Alberta, Canada. The wells were drilled from multi-well pads resulting in deviated wellbores that reach the gas targets. Each well penetrates two or three gas bearing geologic formations, 400 m to 800 m in depth. Each formation has multiple sand and shale layers that were typically completed by perforating six or seven 2.0 m pay intervals. Then each interval was hydraulically fractured with energized, viscosified water frac fluid that placed 12 tonne of proppant in the formation. The fracture treatments were pumped through coiled tubing and a straddle packer was used to isolate each pay interval. The occurrence of undesirable proppant flowback into the wellbore lengthened clean-out time and increased disposal cost. Three solutions to the flowback problem were tried:curable resin-coated proppant;proppant surface- modification agent; and,fibre elements. Each product was tailed into the end of the frac treatment and the amount of each product used had to stay within the economic limits of the project. This paper describes the proppant flowback control achieved by each technique. Other considerations that were required to successfully pump the flowback control products are also discussed. Introduction History The occurrence of proppant flowback from propped hydraulic fractures has long been an operational problem. Many solutions to try and prevent proppant flowback have been attempted with inconsistent results(1, 2). In most cases, the unwanted proppant is produced during cleanup operations, immediately following the fracture treatment, when the well is being flowed or is swabbed to recover frac fluid. During this time, operators can easily handle the produced proppant with the equipment that is present for well stimulation and completion operations. However, proppant disposal can be time consuming and costly as well as reducing the effectiveness of the stimulation treatment. In other situations, proppant is produced during hydrocarbon production and can be a problem for the production life of the well. Proppant flowback can cause valve and choke erosion, plugging of surface vessels, and proppant can build up in the wellbore covering perforations. During production of the well, proppant flowback increases operating costs, compromises safety and reduces hydrocarbon production. Substantial work has been conducted in the industry to explain, predict, and reduce proppant flowback(3). Uneven closure of the formation on the proppant coupled with proppant settling allows upper portions of the proppant pack to be free moving. Proppant flowback is more prevalent in soft, low closure-stress formations and in deviated wells, but can occur in almost any situation. The chance of proppant flowback from properly packed fractures is reduced but proper packing does not insure proppant free production(2). The literature does not provide a clear understanding of proppant flowback causes or flowback prevention techniques. Problem In the subject case history, proppant flowback is a problem in the field's deviated wells but is not a problem in the nearby vertical wells.

Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.

Comment cette classification a été obtenuedéplier

Prédiction distillée sur la base complète

Imitation des enseignants

Ni prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.

score de la tête « metaresearch » (Codex)0,000
score de la tête « metaresearch » (Gemma)0,000
Version: codex-gemma-dda1882f352aStatut de validation: machine_predicted_unvalidated
Catégories candidatesaucune
Catégories consensuellesaucune
DomaineSignal candidat: aucune · Signal consensuel: aucune
Devis d'étudeSignal candidat: Simulation ou modélisation · Signal consensuel: aucune
GenreSignal candidat: Empirique · Signal consensuel: Empirique
Score de désaccord entre enseignants0,891
Score d'incertitude au seuil0,987

Scores Codex et Gemma par catégorie

CatégorieCodexGemma
Métarecherche0,0000,000
Méta-épidémiologie (sens strict)0,0000,000
Méta-épidémiologie (sens large)0,0000,000
Bibliométrie0,0030,001
Études des sciences et des technologies0,0000,000
Communication savante0,0000,000
Science ouverte0,0000,000
Intégrité de la recherche0,0000,001
Charge utile insuffisante (le modèle a refusé de juger)0,0000,000

Scores machine (provisoires)

Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.

Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.

Tête enseignante Opus0,004
Tête enseignante GPT0,164
Écart entre enseignants0,161 · la distance entre les deux têtes enseignantes sur ce seul travail
Statut de validationscore_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découle

Classification

machine, non validée

Prédiction automatique; un appel candidat d’une seule tête enseignante, pas un consensus.

Les modèles n’ont appliqué aucune catégorie : rien dans la taxonomie ne correspondait à ce travail.
Devis d'étudeSimulation ou modélisation
Domainenon disponible
GenreEmpirique

Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».

En bref

Citations12
Publié2003
Routes d'admission2
Résumé présentoui

Explorer davantage

Même revueJournal of Canadian Petroleum TechnologyMême sujetGeotechnical Engineering and Underground StructuresTravaux en français237 207